V-1

Added: AOSL, New Terms, New bots Beta: Update:

V-1.01

Added: Beta: Update:

V-1.1

Added: Beta: Update:

V-1.5

Added: Beta: Update:

V-2

Added: Beta: Update:

V-2.5

Added: Beta: Update:

V-3

Added: Beta: Update:

V-3.1

Added: Beta: Update:

V-4

Added: Beta: Update:

V-4.5

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

Aidworks General License

1.1 | Terms and Conditions

The terms and conditions of the Aidworks Open Source License include:

1. The user may use the software free of charge and for non-commercial purposes.

2. You may modify the software for your own personal use, but you may not distribute or sell these modifications.

3. User may distribute the software free of charge, provided a copyright notice and disclaimer is included in the distributed software.

4. The user may not use the software in a commercial product.

5. The user may not represent themselves as the creator or owner of the AidWorks software.

6. The user understands and accepts that the software is provided as is, without warranties of any kind, express or implied.

7. The user agrees to use the software at the user's own risk.

1.2 | Credit attribution

The user must include proper credit attribution in any use or distribution of the software.

1.3 | Aidworks Removal

In the event Aidworks is removed, users are strongly encouraged to stop using the software and delete any copies or modifications of the software in their possession. The owner of Aidworks assumes no responsibility for removal of Aidworks or continued use of the software after removal. Additionally, users are strongly encouraged to back up and retain copies of any AidWorks software they may have downloaded, for future use if necessary.

2.1 | Applicable laws

The Aidworks Open Source License shall be governed by and construed in accordance with the laws of the place of jurisdiction of the owner of the software, without regard to its conflict of laws principles. Any legal dispute related to the Open Source License will be resolved in the courts of the place of jurisdiction of the owner of the software.

• This clause establishes that the Aidworks Open Source License is governed by and construed in accordance with the laws of the place of jurisdiction of the owner of the software, and that any legal disputes related to the Open Source License will be resolved in the courts of the place jurisdiction of the owner of the software.

2.2 | Divisibility

If any provision of the Open Source License is held invalid or unenforceable, that provision shall be construed to the minimum extent necessary to make it valid or enforceable. The validity and enforceability of the other provisions will not be affected by the invalidity or unenforceability of said provision.

• This clause establishes that if any provision of the Open Source License is considered invalid or unenforceable, it will be interpreted to the minimum extent necessary to make it valid or enforceable, and that the validity and enforceability of the other provisions will not be affected by the invalidity or unenforceability of said provision.

2.3 | Legal disputes

Any legal dispute related to the use of the Aidworks platform software will be governed by the laws of the place of jurisdiction of the owner of the software. If a dispute occurs, all parties agree to accept the exclusive jurisdiction of the court for the place of jurisdiction of the owner of the software.

3.1 | License Updates

The owner of Aidworks reserves the right to update and modify the Open Source License at any time and without prior notice. If the user continues to use the software after the License is modified, it is considered that the user accepts the new terms and conditions.

• This clause states that the owner of Aidworks reserves the right to update and modify the Open Source License at any time without prior notice, and that the user accepts the new terms and conditions by continuing to use the software after it is modified. the license.

3.2 | Security updates

The owner of Aidworks strives to ensure that the Aidworks platform software is secure and protected against external threats. However, the software is not guaranteed to be completely secure against all security threats. The platform owner reserves the right to update and modify the platform software for the purpose of improving the security of the platform.

• This clause states that the owner of Aidworks endeavors to ensure the security of the Aidworks Platform Software, but is not guaranteed to be completely secure. Furthermore, the owner reserves the right to update and modify the software of the platform in order to improve the security of the platform.

3.3 | Software updates and upgrades

The owner of Aidworks reserves the right to update and improve the platform software without prior notice. Such updates and improvements may include bug fixes, security fixes, and new features. By using the software, you agree to receive these updates and upgrades on your device.

• This clause establishes that the owner of the Aidworks platform reserves the right to update and improve the platform software without prior notice, and that the user agrees to receive these updates and improvements on their device. Updates may include bug fixes, security fixes, and new features that improve the quality and functionality of the software.

4.1 | Third Party Products

The Aidworks Platform Software may contain third-party software components that are subject to the licenses for those components. These components may be made available under a different Open Source License than the AidWorks Platform License. It is the user's responsibility to determine and comply with the terms and conditions applicable to such third party components.

• This clause states that the Aidworks Platform Software may contain third party software components. Users should review the terms and conditions of the licenses for such components and comply with them independently of the terms and conditions of the Aidworks Open Source License.

4.2 | Software Warranty

The owner of Aidworks does not guarantee the quality, security or functionality of the software. The software is provided as is, without warranties of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose, and non-infringement. Any use of the software is at the user's own risk.

• This clause is added to state that the owner of Aidworks does not warrant the quality, safety or functionality of the software and that use of the software is at the user's own risk. A user of Aidworks should be aware that the software is provided as is without warranties.

4.3 | Software Availability

The platform owner AidWorks strives to ensure that the platform software is available at all times. However, the platform software is not guaranteed to be always available and uninterrupted. The platform owner shall not be liable for any loss or damage arising from the use of or the inability.

• This clause states that the platform owner AidWorks endeavors to ensure the availability of the platform software, but does not guarantee uninterrupted availability. The Platform Owner shall not be liable for any loss or damage arising from the use or inability to use the Platform Software due to interruptions or unavailability.

4.4 | Software Modifications

You agree that the AidWorks Owner may modify or update the AidWorks Platform Software at any time without notice. The user acknowledges that any modification or update may affect the functionality of the software and agrees that the owner of AidWorks shall not be liable for any loss or damage arising from the use of the modified or updated software.

• This clause establishes that the owner of AidWorks may modify or update the platform software at any time and without prior notice, and that the user accepts that any modification or update may affect the functionality of the software. The user also agrees that the owner of AidWorks shall not be liable for any loss or damage arising from the use of modified or updated software.

4.5 | In-Software Advertising

You agree that the Aidworks Platform Software may include third-party advertising. The user acknowledges and agrees that the owner of AidWorks has no control over third party advertising and will not be liable for any damage or loss that may arise from the use of such advertising.

• This clause establishes that the platform software may include third-party advertising. In addition, the user acknowledges and agrees that the owner of Aidworks has no control over third party advertising and will not be responsible for any damage or loss that may arise from the use of such advertising.

4.6 | Termination of use of the software

The owner of Aidworks reserves the right to terminate access to and use of the Aidworks Platform Software at any time without notice. The user agrees that the owner of Aidworks shall not be liable for any loss or damage arising from termination of access to and use of the software.

• This clause states that the owner of Aidworks reserves the right to terminate access to and use of the platform software at any time and without prior notice, and the user agrees that the owner shall not be liable for any loss or damage that arising out of termination of access to and use of the Software.

4.7 | Software Export

User acknowledges that the Aidworks Platform Software may be subject to export control laws and regulations. It is the user's responsibility to comply with all applicable export control laws and regulations. You agree that you will not export, re-export, transfer, or use the Aidworks Platform Software in violation of any applicable export control laws and regulations.

• This provision states that the Aidworks Platform Software may be subject to export control laws and regulations. User must comply with all applicable export control laws and regulations and must not use the Aidworks Platform Software in a manner that violates applicable export control laws and regulations.

5.1 | Waiver of Rights

Aidworks's owner's waiver of any right or provision of this Open Source License shall not be deemed a further or continuing waiver of such right or provision, nor shall it revoke the owner's right to exercise such right or provision at any other time.

• This clause ensures that the waiver by the owner of Aidworks of any right or provision of the Open Source License shall not be deemed a further or continuing waiver of such right or provision, and shall not revoke the owner's right to exercise such right or provision. at another time.

5.2 | Disclaimer

The owner of Aidworks shall not be liable for any direct, indirect, incidental, special, consequential, or punitive damages resulting from the use or inability to use the software. The user understands and agrees that he uses the software at his own risk and responsibility.

5.3 | Disclaimer of Warranties

The owner of Aidworks disclaims all warranties, express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose in connection with the Aidworks Platform Software.

• This clause states that the owner of Aidworks disclaims all express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose in connection with the Aidworks Platform Software.

6.1 | Support for assistive technologies

The owner of Aidworks strives to ensure that the AidWorks platform software is compatible with assistive technologies, such as screen readers and alternate input devices, to enable people with disabilities to use the software. However, the software is not guaranteed to be fully compatible with all assistive technologies. The Platform Owner shall not be liable for any loss or damage arising from the use or inability to use the Software due to lack of compatibility with assistive technologies.

• This clause states that the owner of Aidworks endeavors to ensure the compatibility of the platform software with assistive technologies to enable people with disabilities to use the software, but does not guarantee its full compatibility. In this way, it seeks to protect the rights of users with disabilities and avoid any possible liability that may arise from the lack of adaptability of the software.

6.2 | Operating system compatibility

The owner of Aidworks strives to ensure that the Aidworks Platform Software is compatible with various operating systems and browsers. However, there is no guarantee that the AidWorks platform software will work on all operating systems and browsers.

• This clause states that the owner of Aidworks strives to ensure that the platform software is compatible with various operating systems and browsers, but it is not guaranteed to work on all operating systems and browsers. It is important for the user to take into account that there may be limitations in the compatibility of the software with certain operating systems and browsers.

6.3 | License Modifications

The owner of Aidworks reserves the right to modify the Open Source License at any time and without prior notice. If any provision of the License is held invalid or unenforceable, that provision shall be construed in accordance with applicable law to the minimum extent necessary to make it valid and enforceable. The validity and enforceability of the other provisions of the License will not be affected by the invalidity or unenforceability of such amended provision.

• This clause states that the owner of Aidworks reserves the right to modify the Open Source License at any time and without prior notice, and that the provisions of the License are interpreted in accordance with applicable law. If any provision is held invalid or unenforceable, such provision shall be construed to the minimum extent necessary to make it valid and enforceable. The validity and enforceability of the other provisions of the License will not be affected by the invalidity or unenforceability of such amended provision.

6.4 | Right to Modify or Terminate License

The owner of Aidworks reserves the right to modify or terminate this license at any time without notice. The user understands and agrees that the owner of Aidworks may terminate access to and use of the software if the user violates the license terms and conditions.

7.1 | Email Communications

The user accepts that communications with the owner of the Aidworks platform are carried out by email. The user must provide a valid email address and agrees that all notifications and communications related to the Open Source License will be sent to such email address. The user is responsible for keeping his email address updated in case of any changes.

• This clause establishes that communications with the owner of the Aidworks platform will be carried out by email, and that the user must provide a valid email address and keep it updated in case of any change. This would include any notification or communication related to the Open Source License.

7.2 | Data storage and processing

The user acknowledges and agrees that the owner of AidWorks may store and process their data in connection with the use of the AidWorks platform software. The user also agrees that the owner of AidWorks may share this data with third parties as necessary to provide the software and improve the user experience. The user agrees to comply with all applicable laws regarding privacy and the use of user data.

• This clause states that the owner of Aidwrks may store and process user data in connection with the use of the platform software, and that the user agrees that this data may be shared with third parties as necessary. It is also established that the user must comply with all applicable laws regarding privacy and the use of user data.

7.3 | Reverse Engineering Prohibition

You agree that you are prohibited from reverse engineering, decompiling, or disassembling the Aidworks Platform Software. Any unauthorized use of the software is a violation of the rights of the platform owner and may be subject to penalties under applicable law.

• This clause establishes that the user is prohibited from reverse engineering, decompiling or disassembling the Aidworks platform software without authorization. It seeks to prevent unauthorized reproduction or distribution of modified versions of the software, as well as protect the rights of the owner of the platform.

7.4 | Conflict of interests

The user acknowledges and accepts that it is prohibited to use the Aidworks platform software in situations that may present a conflict of interest. The purpose of this measure is to protect the rights of the owner of the platform and to avoid conflict situations that may result in inappropriate use of the software.

7.5 | Confidentiality

The user agrees to maintain the confidentiality of any confidential information related to the Aidworks platform software, including trade secrets and proprietary information of the owner of the platform. The user will not disclose, share or use such confidential information for any purpose other than the use of the Aidworks platform software.

• This clause states that the user must maintain the confidentiality of any confidential information related to the Aidworks platform software, including trade secrets and proprietary information of the owner of the platform. The user must not disclose, share or use such confidential information for any purpose other than the use of the Aidworks platform software.

7.6 | Compensation

The user agrees to indemnify and hold harmless the platform owner and its employees, contractors, licensors, distributors and partners from any and all losses, liabilities and expenses, including attorneys' fees, that may arise from the use of the Aidworks platform software or from any breach of the terms and conditions of the Open Source License.

• This clause establishes that the user must indemnify and hold harmless the owner of the platform and its employees, contractors, licensors, distributors and partners from any loss, liability and expense that may arise from the use of the Aidworks platform software. This would include any breach of the terms and conditions of the Open Source License.

8.1 | License Acceptance

Use of the Aidworks platform software implies full acceptance and agreement of the Open Source License. If the user does not accept the terms and conditions of the License, the user is not authorized to use the platform software.

• This clause establishes that the use of the Aidworks platform software implies the acceptance and full agreement of the Open Source License. If the user does not accept the terms and conditions of the License, the user is not authorized to use the platform software.

8.2 | Use of open source software

The Aidworks Platform Software may include the use of open source software under specific licenses. The user acknowledges and agrees that these specific licenses may include additional terms and conditions that govern the use of the open source software. The user agrees to comply with all specific licenses that apply to the use of the open source software on the Aidworks platform.

• This clause states that the Aidworks platform software may include the use of open source software under specific licenses, and that the user must comply with additional terms and conditions governing the use of this open source software. The objective is to ensure that the user is informed about the inclusion of open source software and adheres to the terms and conditions established by the corresponding specific licences.

8.3 | Use not allowed

The user may not use the software in any way that violates applicable laws and regulations. You may not use the Software to violate any third party's intellectual property rights, including copyrights, patents, trademarks, or trade secrets, or to post or transmit libelous, obscene, or illegal material.

• This clause states that the Aidworks Platform Software must not be used in any way that violates applicable laws and regulations or the intellectual property rights of third parties, including copyrights, patents, trademarks or trade secrets. The user must also refrain from posting or transmitting libelous, obscene or illegal material.

8.4 | Commercial use

The user may not use the Aidworks platform software for commercial purposes without the prior written permission of the platform owner. Commercial use includes any use of the Software that generates direct or indirect revenue, such as advertising, sponsorships, or sales.

• This clause establishes that the Aidworks platform software must not be used for commercial purposes without the prior written permission of the owner of the platform. This includes any use of the software that generates direct or indirect income, such as advertising, sponsorships, or sales.

8.5 | Use of personal data

The user acknowledges and agrees that the owner of Aidworks may collect and use the user's personal data in connection with the use of the AidWorks platform software. The user also agrees that the owner of Aidworks may share this personal data with third parties as necessary to provide the software and improve the user experience.

• This clause states that the owner of Aidworks may collect and use user personal data in connection with the use of the Aidworks platform software, and is necessary to provide the software and improve the user experience. Personal data may be shared with third parties as necessary.

8.6 | Use of the software outside the scope of the License

The user acknowledges and agrees that any use of the Aidworks platform software outside the scope of the Open Source License is strictly prohibited. Any unauthorized use of the software is a violation of the rights of the platform owner and may be subject to penalties under applicable law.

• This clause states that any use of the Aidworks platform software outside the scope of the Open Source License is strictly prohibited and that any unauthorized use of the software is a violation of the rights of the platform owner and may be subject to penalties under applicable law.

8.7 | Exclusive rights

The User agrees that the Aidworks Platform software and related intellectual property rights are the exclusive property of the Platform owner, including all related copyrights, patents, trademarks and trade secrets. The user does not acquire any ownership rights in the software or related intellectual property rights, except as expressly provided by the Open Source License.

• This clause establishes that the owner of Aidworks is the exclusive owner of the Aidworks platform software and related intellectual property rights, including all related copyrights, patents, trademarks and trade secrets. The user does not acquire any ownership rights in the software or related intellectual property rights, except as expressly provided by the Open Source License.

9.1 | Limitation of Liability for Software Defects

The owner of Aidworks shall not be liable for any defects or errors in the software resulting from misuse, modification, or misuse of the software. The owner of Aidworks shall not be liable for any direct, indirect, incidental, special, consequential, or punitive damages resulting from any defects or errors in the software.

• This clause ensures that the owner of AidWorks shall not be liable for any defects or errors in the software resulting from the misuse, modification, or misuse of the software, and that any liability of the owner is limited to the amount paid for the software (if any). paid at all).

9.2 | Responsibility for the use of the software

Use of the Aidworks Platform Software is at your own risk. Platform Owner shall not be liable for any loss or damage arising out of the use of, or inability to use, the Software, including but not limited to direct, indirect, incidental, punitive, and consequential damages.

• This clause states that the user uses the Aidworks platform software at their own risk, and that the owner of the platform shall not be liable for any loss or damage arising from the use or inability to use the software, including damages direct, indirect, incidental, punitive and consequential.

9.3 | User responsibility

You are responsible for any use you make of the Aidworks platform software. User agrees to indemnify and hold harmless Platform Owner and its employees, contractors, licensors, distributors, and partners from and against any and all losses, liabilities, and expenses, including attorneys' fees, that may arise from use of the Aidworks Platform Software in breach. of the Open Source License or any applicable law.

• This clause establishes that the user is responsible for any use of the Aidworks platform software and agrees to indemnify and hold the platform owner and others harmless from any loss, liability and expense that may arise from the use of the Aidworks platform software. the platform in breach of the Open Source License or any applicable law.

1. Be respectful and professional in all communication with other staff members and members of the server.

2. Use your powers responsibly and make sure to follow server rules at all times.

3. If you encounter a problem or issue, bring it up with another staff member or the server owner.

4. Stay active and engage with members of the community to keep the server running smoothly.

5. Remember that you are representing the server, so act accordingly.

6. Keep sensitive information confidential and do not share it with anyone who is not authorized to view it.

7. If you need to take a break or step away from your duties for any reason, make sure to communicate this with other staff members.

8. Do not abuse your powers or engage in any behavior that could be seen as favoritism or discrimination.

9. Make sure to familiarize yourself with the server rules and be prepared to enforce them if necessary.

10. Stay accountable for your actions and take responsibility for any mistakes or missteps.

11. Respond promptly to any messages or inquiries from members or other staff members.

12. Be open to feedback and suggestions and continually work to improve the server and your performance as a staff member.

13. Take note of any patterns or issues that arise in the server and work with other staff members to address them.

14. Remember that you are a rolemodel for the community, so act accordingly.

15. Do not engage in any behavior that goes against the Discord Community Guidelines or Terms of Service.

16. Maintain a positive attitude and create a welcoming environment for all members.

17. If you are unsure of how to handle a situation or are facing a difficult decision, reach out to other staff members for advice and support.

18. Stay organized and keep track of any tasks or responsibilities assigned to you.

19. Participate in staff meetings and discussions to stay updated on any changes or new developments in the server.

20. Make sure to communicate clearly and effectively with other staff members and members of the server.

21. Treat all members of the server fairly and without bias.

22. Make sure your actions are consistent with the server's mission and goals.

23. Encourage and support other staff members in their roles and responsibilities.

24. Be transparent with other staff members and members of the server with regards to your actions and decisions.

25. Take breaks and practice self-care to avoid burnout.

Go

Wait for a team to attend to you it usually takes a maximum of 24hours, if this is not the case, let us know by mentioning an assistant or moderator

No history of breaking & discord rules

No history of breaking AidWorks rules (NONE)

Terms of Partner & Alliances

1. Relevant content: All content shared by partners and allies must be relevant to the main theme of the server and must be posted in the appropriate channel.

2. Mutual benefits: Partners and allies must work together to create mutual benefits, with each party contributing to the success of the other.

3. Respectful behavior: All partners and allies must be respectful and professional towards each other and the server community as a whole.

4. No solicitation: Partners and allies should not solicit other members of the server for personal or business gain without prior approval.

5. Protection of data: Partners and allies must respect the privacy and rights of other members and should not share personal information without explicit consent.

6. Moderation: Moderators have the authority to enforce the rules and take appropriate disciplinary action in case of non-compliance.

Requirements

1. Relevant content: The partner or ally must have content that is relevant to the main theme of the server.

2. Established presence: The partner or ally must have an established presence on their respective platform (e.g. website, social media, etc.).

3. Professionalism: The partner or ally must act in a professional and respectful manner towards the server and its members.

4. Mutual benefit: The partnership or alliance must be beneficial for both parties, with each party contributing to the success of the other.

5. Approval: The partnership or alliance must be approved by the server administrators or moderators.

6. Activity level: The partner or ally must have a consistent level of activity on their respective platform, with regular updates and engagement with their audience.

1. Types of information collected: Clarify what types of information are collected from server users, such as registration information, contact information, and server usage information.

2. Use of information: Clarify how the collected information will be used, such as to improve the service, personalize the user experience, and offer relevant content.

3. Sharing information with third parties: Clarify whether information will be shared with third parties, such as advertisers or affiliates, and how user privacy will be protected.

4. Cookies and similar technologies: Clarify whether cookies or other similar technologies are used to collect user information, and whether that information will be used to personalize the user experience or offer personalized advertising.

5. Information security: Clarify what measures will be taken to protect user information from unauthorized access or misuse.

6. Access, modification, and deletion of information: Clarify how users can access, modify, or delete their personal information.

7. Changes to the privacy policy: Clarify how users will be notified of any changes to the privacy policy, and how their consent will be obtained.

8. Use of non-personal data: Clarify whether non-personal information, such as geographic location or type of browser, is collected and used, and how that information is used.

9. Advertising: Clarify whether advertising is displayed on the server, and how advertising is personalized based on user interests.

10. Minors: Clarify whether registration and use of the server is allowed by minors, and how the privacy and safety of those users is protected.

11. Data retention policy: Clarify how long user information is retained, and how that information is deleted once it is no longer necessary.

12. Data transfer to other countries: Clarify whether user information will be transferred to other countries, and how user information will be protected when doing so.

13. Consent: Clarify how user consent is obtained for the collection and use of personal information, and how users can withdraw that consent at any time.

14. Legal compliance policy: Clarify how applicable privacy and data protection laws and regulations will be followed, and how the server will cooperate with authorities in case of a legal request.

15. Contact: Clarify how users can contact the server if they have questions or concerns related to privacy and data protection.

16. User-generated content: Clarify whether user-generated content, such as messages or comments, is moderated, and how it is moderated to ensure the privacy and safety of users.

17. Analytics: Clarify whether analytics tools are used on the server to collect information about user behavior, and how that information is used to improve the user experience.

18. Social media integration: Clarify whether the server is integrated with social media platforms, and how user information is shared between the server and those platforms.

19. Payment and billing information: Clarify whether payment and billing information is collected and how it is protected to ensure the privacy and security of users.

20. Links to third-party websites: Clarify whether the server contains links to third-party websites, and whether user information is shared with those websites.

21. User rights: Clarify what rights users have with respect to their personal information, such as the right to access, modify, or delete that information.

22. Data breaches: Clarify what measures will be taken in case of a data breach, and how users will be notified of such a breach.

23. General Data Protection Regulation (GDPR): If your server is accessed by users in the European Union, clarifying how your server will comply with the GDPR.

24. User support: Clarify how user support is provided, and how user information is used to provide that support.

25. Opting out: Clarify how users can opt out of certain types of data collection or data sharing.

26. User consent for marketing: Clarify how user consent is obtained for marketing communications, and how users can opt out of those communications.

27. Data portability: If applicable, clarify how user data can be exported or transferred to another service or platform.

28. Changes to the policy: Clarify how users will be notified of any changes to the privacy policy, and how their consent will be obtained for those changes.

29. Contact: Provide contact information for users to ask privacy-related questions and concerns

Here we show you all the Phagons servers, some servers are private

Public Server

General Administrative Server

Administrative Pokemon Server

Administrative Systems Server

Partner Server

This server is in English because our Bot Hαkαiryu is English But we allow other languages because we are a Pokemon community

Open ticket in ‖🎟‖claims-ticket

Chief Officer of Phagons | COP

Creador de Phagons. Encargado de que todo vaya segun lo planeado

Chief Executive Official | CEO

Encargado de ejecutar las ideas de COP y que estas se cumplan

Chief Operating Officer | COO

Encargado de realizar todo lo que pida un CEO y solucionar problemas de CTO

Chief Marketing Officer | CMO

Encargado de realizar pactos economicos o sociales con otras comunidades

Chief Financial Officer | CFO (Actualmente no sirve)

Encargadod que la economia real del servidor se use correctamente

Chief Information Officer | CIO

Encargado de informarse e informar a otros, además de ayudar a otros miembros

Chief Technology Officer | CTO

Encargado de la configuración del servidor

Chief Communications Officer | CCO

Encargado de que la gente se entere de lo que va sucediendo a traves de anuncios

Chief Design Officer | CDO

Encargado de diseños, y recopilar datos generales del servidor

A place where you can imagine everything you want and share it with the rest. A place where everything could be possible

• Do not impersonate any member of the staff or moderation team.

• If you continue to do something that the staff have already told you not to do, your account will be suspended for 1 week.

• Do not spread false information about the bot.

• Do not incite hatred towards the bot.

• We do not tolerate the misuse of commands.

• Spaw DM with the bot will be strictly prohibited (staff can, if used correctly).

• Do not copy ideas, emojis, avatar or code (except the public). Before copying something, ask for permission from the account fluxairus@gmail.com

• You cannot exchange money, diamonds or pokemon (bot) with other bots or in a real life relationship (Unless the team has allowed you in that case you will get a special badge from your server ,to know that it has been allowed)

• Do not send mail or ask for help if it is a joke or false

• In case you want to delete your information, it must be done by the author who requested it in his own account, but not requested by another member.

The pokémon regulations are more for which pokémon you get I what you should do if it is illegal in Wolf Universe.

Which Pokémon are considered illegal in our Bots?

• In case of being shiny lock and not having one of these EO: Dragons.Support, T.Admin.Pokemon, T.Trust&Safety, Event_, Battle_, Global_

• That has a level higher than 100

• That it has an ability that does not exist or a movement (this is usually more due to failures or poorly created)

What should you do if you have an illegal?

In case it was given to you by a member:

• You must go to the administration server (w?support or /support) and communicate it

In case of an error:

• Communicate it too (fluxairus@gmail.com)

In case you created it:

• Release and create it right

Consequence of having an illegal and not reporting it?

It would be to suspend the account in the Bot until you justify why you have the Pokémon. In case you don't remember why, we'll let you release the pokémon and your account will be re-approved.

Discord, is like PEGI 13 years old generally, it may vary depending on where the user resides

Pokémon, is like PEGI 7 years old generally, it may vary depending on the game, movie/series or others

Our bot, like PEGI, is 12 years old, because it contains cheap systems, and fast capture, therefore, in order not to harm any user, for any reason, we recommend that the user be over 12 years old.

1. Use the command {prefix}support, and enter the support that indicates

2. Open a post

   1. In #issues-support: if it's a bug or question

   2. In #report: if you have any complaint

3. Put the tag that you think is most convenient for the topic

4. Wait for a team to attend to you it usually takes a maximum of 24hours, if this is not the case, let us know by mentioning an assistant or moderator.

1. Use the command {prefix}support, and enter the support that indicates

2. Open a ticket in #report

3. Select the Report Block tags and the terms tag you broke, in case you haven't broken any, just put the first tag

4. Explain why you think your account has been blocked. And why we should withdraw your suspension, in case you break the rule

Breaching server regulations can carry a Warn, isolation, kick or ban Breaching bot regulations can carry a Suspension. --> According to: Slight = temporary is serious = permanent suspension Breaching Pokémon regulations can carry a Suspension. suspension

--> According to:

You didn't know or you forgot for the first time = temporary suspension You already knew or you forgot but it happened before = permanent suspension

• = The version emoji, this is to the left of the number that indicates the version of the bot, the user or the command

• = This emoji indicates that the command has been added very recently.

• = Indicates that the command is in testing and therefore there are probably some errors.

V-1 [2023-03-17]

Added: roles, pings, partner, Beta: torney, battles Update: channels of bot

V-1.01

Added: Beta: Update:

V-1.1

Added: Beta: Update:

V-1.5

Added: Beta: Update:

V-2

Added: Beta: Update: catch, spawn

V-2.5

Added: Beta: Update:

V-3

Added: Beta: Update:

V-3.1

Added: Beta: Update:

V-4

Added: Beta: Update:

V-4.5

Added: {prefix} Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

Privacy Policy

User privacy

1. The Fluxairus system doesn't want your information at all, least of all the passwords and the token. This organization only obtains your username + tag (Discord # 0000), your user id to contact us for informational purposes or contact support through bot (having a certification that it is official by putting that it comes from a official server), as we contain information about where you used the command and on which server to send a response to their servers if they have a problem or to notify you of something important. THIS INFORMATION WILL NEVER BE SHARED TO ANYONE

Information we collect

1. We get your Discord NAME (ex: Discord) and your TAG (ex: #0000)

2. We get your ID to send you a private message (if you want), mention or to add support badges

3. We get the IDs and NAMES of the channels and the server to send an official message to the channel or a reply and issue or question.

4. We obtain the AVATAR to know on another occasion who it is or to facilitate contact

User Rights

In accordance with the Regulation, the user has:

1. the right of access to personal data;

2. the right to rectification of personal data;

3. the right to erase personal data;

4. the right to object to the processing of personal data;

5. the right to data portability;

6. the right to withdraw consent to the processing of personal data in writing or by email sent to: support;

7. the right to file a complaint with the supervisory authority in case of suspected non-compliance with the Regulations.

Personal Data Security

1. The DATA SECURITY team protects your information, if this information is shared without the consent of the author of the information, they will take action to keep the information in good hands

Here where we explain why we need the bot to have these permissions, Attention: any permission not mentioned here, we recomend to remove it

Important Permissions

• Read Messages/View Channels : so that the bot can know what command you are using

• Read Messages History

• Send Messages : to be able to respond to commands

• Attach files : so that there are no errors in the images

• Embed link :

• Use application commands : to be able to perform slash "/" commands

Additional Permissions

• Manage Messages : to be able to delete some commands that require their deletion

• Send Messages in Thread : so that if the user wants, the spawns also appear there

• Create invitation : so that if the staff needs to enter the server and solve a case, you can enter it

Other Permissions

• Add Reactions : Use external stickers and emojis: to make the bot look prettier

• Change nickname : to change the nickname of the bot, in case it is not the right one

The beginning of AidWorks life

• The AidWorks concept is created

• AidWorks open license is created

• The bot is modified

• The official contact bot is created

• Added to bots in AidWorks

• AidWorks servers will be created

• They put on the AidWorks gear

• They are put on the members who occupy it AidWorks

• General Terms are created

• The terms of each AidWorks are created

• Channels and roles are created

• Staff sought for each AidWorks

An event arrives on the server from Dragons, a server that has remained in prehistory and we enter a futuristic world. We hope you like what is coming in this event. Prize: Access to AidWorks Discord Partner. Requirement: invite a member here

Name: pokedex

Usage: pokedex <pokémon>

Parameters:

• <pokémon>

  • The name of the pokémon

Alias: d | dex | dx | pokédex

What should come out?: The information of the Pokémon

Example: dex mew | d DiaLga

Note: The pokemon name does not vary according to the size of the text. But it does vary according to its source and how it is put. When you go to look for a pokemon look for its normal form and already in the dex it is indicated how to look for information about its form. The Pokedex already indicates its shiny form and therefore does not need to indicate in the command what color form it wants.

spawn

Name: spawn

Usage: spawn

Alias: sp

What should come out?: Some

legend.spawn |

Name: l.spawn

Usage: l.spawn

Alias: legend.sp | l.sp | l.spawn

What should come out?: Some

g.spawn |

Name: g.spawn

Usage: l.spawn <pokémon> (| shiny?)

Parameters:

• <pokémon>

  • The name of the pokémon

• (| shiny?)

  • If you put shiny, the pokemon will appear shiny

  • If you don't put anything, the pokemon will appear normal

What should come out?: The Pokémon you want

Note: The pokemon that have come out in the and Pokemon that have not been sighted in the pokemon franchise cannot be spawned by users, on the other hand the official bot team can

giga-spawn |

Name: giga-spawn

Usage: giga-spawn

Alias: g-sp | giga-spawn | giga-sp

What should come out?: Some

totem-spawn |

Name: totem-spawn

Usage: totem-spawn

Alias: t-sp | totem-spawn | totem-sp

What should come out?: Some

mega-spawn |

Name: m-spawn

Usage: giga-spawn

Alias: m-sp | mega-sp | m-spawn

What should come out?: Some

w.spawn

h.spawn

p.spawn

Name: catch

Usage: catch <pokémon>

Parameters:

• <pokémon>

  • The name of the pokémon

Alias: c

What should come out?: That you need to put name pokemon or number pokemon, that there is no pokemon, that the pokemon is wrong or an error sent from the system (use /support or to report it)

Example: c mew | catch celebi

Note: The pokemon name does not vary according to the size of the text. But it does vary according to its source and how it is put. If you dont know the name. You can use hint (this command request premium if you want to know the full name, more info --> )

Name: hint

Usage: hint

Alias: h

What should come out?: of the pokemon's name or the

Example: hint

Some Words

Some letters appear. If symbols appear, those are from the word itself, for example Ho-oh

All Words

Note: if you want to know the full name you need )

Name: give-pokemon

Usage: give-pokemon <userID> <boxIn> <position>

Parameters:

• <userID>

  • The . The user that you want to give the pokemon

• <boxIn>

  • Put the number of the box where the pokemon is currently in

• <position>

  • The position of the pokemon. You can see , to get the position of the pokemon

What should come out?: That you give the pokemon to the other user

Example: give-pokemon 855390537702965258 1 40

I give to Wolf Universe the pokemon that its in the box 1 and the position is 40. For example a Mew Level 66, without shiny and special ability, and with EO, TheBestBot

Name: give-pokemon

Usage: give-pokemon <userID> <boxIn> <position>

Parameters:

• <userID>

  • The . The user that you want to give the pokemon

• <boxIn>

  • Put the number of the box where the pokemon is currently in

• <position>

  • The position of the pokemon. You can see , to get the position of the pokemon

What should come out?: That you give the pokemon to the other user

Example: give-pokemon 855390537702965258 1 40

I give to Wolf Universe the pokemon that its in the box 1 and the position is 40. For example a Mew Level 66, without shiny and special ability, and with EO, TheBestBot

Name: pok-info

Usage: pok-info <userID> <boxIn> <position>

Parameters:

• <userID>

  • The . The user that you want to give the pokemon

• <boxIn>

  • Put the number of the box where the pokemon is currently in

• <position>

  • The position of the pokemon. You can see , to get the position of the pokemon

What should come out?: That you give the pokemon to the other user

Example: give-pokemon 855390537702965258 1 40

I give to Wolf Universe the pokemon that its in the box 1 and the position is 40. For example a Mew Level 66, without shiny and special ability, and with EO, TheBestBot

Name: traslade

Usage: traslade <boxIn> <position> <boxTo> (serverID)

Parameters:

• <boxIn>

  • Put the number of the box where the pokemon is currently in

• <position>

  • The position of the pokemon. You can see , to get the position of the pokemon.

• <boxTo>

  • Put the box number where you want it to be now. If you dont put next a serverID, you can't put the same box that <boxIn>

• (serverID)

  • The . The serverthat you want to traslade the pokemon

What should come out?: That you give the pokemon to the other user

Example: give-pokemon

Name: give-pokemon

Usage: give-pokemon <userID> <boxIn> <position>

Parameters:

• <userID>

  • The . The user that you want to give the pokemon

• <boxIn>

  • Put the number of the box where the pokemon is currently in

• <position>

  • The position of the pokemon. You can see , to get the position of the pokemon

What should come out?: That you give the pokemon to the other user

Example: give-pokemon 855390537702965258 1 40

I give to Wolf Universe the pokemon that its in the box 1 and the position is 40. For example a Mew Level 66, without shiny and special ability, and with EO, TheBestBot

When you use the w?dex command, then in the same message you must put a Pokemon Number or a Pokemon Name.

The buttons of Pokedex

• The right arrow button is to go right

• The magnifying glass button is to search for any pokemon

• The left arrow button is to go left

Alias

• {prefix}d

• {prefix}dex

• {prefix}dx

• {prefix}pokedex

Version:

1

Note:

❌

Examples

• {prefix}dex 1

• {prefix}dex bulbasaur

• {prefix}dex

Name: daily

Usage: {prefix}daily

What should come out?:

For example

Name: omegan-landan

Usage: {prefix}omegan-landan

What should come out?: A obtion to change to omegan a landan or landan to omegan

Note: λ = Landan | Ω = Omegan | Ψ = Phagan

Conversions: 1499 λ = 1 Ω | 499 Ω = 1 Ψ (can't be passed Ψ to Ω)

Name: acquittance

Usage: {prefix}acquittance

What should come out?: To give to other user λ

Note: You can give only λ

1ºQuestion = userID 2ºQuestion = amount 3ºQuestion = confirm

When you use the w?dex command, then in the same message you must put a Pokemon Number or a Pokemon Name.

The buttons of Pokedex

• The right arrow button is to go right

• The magnifying glass button is to search for any pokemon

• The left arrow button is to go left

Alias

• {prefix}d

• {prefix}dex

• {prefix}dx

• {prefix}pokedex

Version:

1

Note:

❌

Examples

• {prefix}dex 1

• {prefix}dex bulbasaur

• {prefix}dex

Name: pokedex

Usage: pokedex <pokémon>

Parameters:

• <pokémon>

  • The name of the pokémon

Alias: d | dex | dx | pokédex

What should come out?: The information of the Pokémon

Example: dex mew | d DiaLga

Note: The pokemon name does not vary according to the size of the text. But it does vary according to its source and how it is put. When you go to look for a pokemon look for its normal form and already in the dex it is indicated how to look for information about its form. The Pokedex already indicates its shiny form and therefore does not need to indicate in the command what color form it wants.

spawn

Name: spawn

Usage: spawn

Alias: sp

What should come out?: Some

legend.spawn |

Name: l.spawn

Usage: l.spawn

Alias: legend.sp | l.sp | l.spawn

What should come out?: Some

g.spawn |

Name: g.spawn

Usage: l.spawn <pokémon> (| shiny?)

Parameters:

• <pokémon>

  • The name of the pokémon

• (| shiny?)

  • If you put shiny, the pokemon will appear shiny

  • If you don't put anything, the pokemon will appear normal

What should come out?: The Pokémon you want

Note: The pokemon that have come out in the and Pokemon that have not been sighted in the pokemon franchise cannot be spawned by users, on the other hand the official bot team can

giga-spawn |

Name: giga-spawn

Usage: giga-spawn

Alias: g-sp | giga-spawn | giga-sp

What should come out?: Some

totem-spawn |

Name: totem-spawn

Usage: totem-spawn

Alias: t-sp | totem-spawn | totem-sp

What should come out?: Some

mega-spawn |

Name: m-spawn

Usage: giga-spawn

Alias: m-sp | mega-sp | m-spawn

What should come out?: Some

w.spawn

h.spawn

p.spawn

Name: catch

Usage: catch <pokémon>

Parameters:

• <pokémon>

  • The name of the pokémon

Alias: c

What should come out?: That you need to put name pokemon or number pokemon, that there is no pokemon, that the pokemon is wrong or an error sent from the system (use /support or to report it)

Example: c mew | catch celebi

Note: The pokemon name does not vary according to the size of the text. But it does vary according to its source and how it is put. If you dont know the name. You can use hint (this command request premium if you want to know the full name, more info --> )

Name: hint

Usage: hint

Alias: h

What should come out?: of the pokemon's name or the

Example: hint

Some Words

Some letters appear. If symbols appear, those are from the word itself, for example Ho-oh

All Words

Note: if you want to know the full name you need )

Name: give-pokemon

Usage: give-pokemon <userID> <boxIn> <position>

Parameters:

• <userID>

  • The . The user that you want to give the pokemon

• <boxIn>

  • Put the number of the box where the pokemon is currently in

• <position>

  • The position of the pokemon. You can see , to get the position of the pokemon

What should come out?: That you give the pokemon to the other user

Example: give-pokemon 855390537702965258 1 40

I give to Wolf Universe the pokemon that its in the box 1 and the position is 40. For example a Mew Level 66, without shiny and special ability, and with EO, TheBestBot

Name: give-pokemon

Usage: give-pokemon <userID> <boxIn> <position>

Parameters:

• <userID>

  • The . The user that you want to give the pokemon

• <boxIn>

  • Put the number of the box where the pokemon is currently in

• <position>

  • The position of the pokemon. You can see , to get the position of the pokemon

What should come out?: That you give the pokemon to the other user

Example: give-pokemon 855390537702965258 1 40

I give to Wolf Universe the pokemon that its in the box 1 and the position is 40. For example a Mew Level 66, without shiny and special ability, and with EO, TheBestBot

Name: pok-info

Usage: pok-info <userID> <boxIn> <position>

Parameters:

• <userID>

  • The . The user that you want to give the pokemon

• <boxIn>

  • Put the number of the box where the pokemon is currently in

• <position>

  • The position of the pokemon. You can see , to get the position of the pokemon

What should come out?: That you give the pokemon to the other user

Example: give-pokemon 855390537702965258 1 40

I give to Wolf Universe the pokemon that its in the box 1 and the position is 40. For example a Mew Level 66, without shiny and special ability, and with EO, TheBestBot

Name: traslade

Usage: traslade <boxIn> <position> <boxTo> (serverID)

Parameters:

• <boxIn>

  • Put the number of the box where the pokemon is currently in

• <position>

  • The position of the pokemon. You can see , to get the position of the pokemon.

• <boxTo>

  • Put the box number where you want it to be now. If you dont put next a serverID, you can't put the same box that <boxIn>

• (serverID)

  • The . The serverthat you want to traslade the pokemon

What should come out?: That you give the pokemon to the other user

Example: give-pokemon

Name: give-pokemon

Usage: give-pokemon <userID> <boxIn> <position>

Parameters:

• <userID>

  • The . The user that you want to give the pokemon

• <boxIn>

  • Put the number of the box where the pokemon is currently in

• <position>

  • The position of the pokemon. You can see , to get the position of the pokemon

What should come out?: That you give the pokemon to the other user

Example: give-pokemon 855390537702965258 1 40

I give to Wolf Universe the pokemon that its in the box 1 and the position is 40. For example a Mew Level 66, without shiny and special ability, and with EO, TheBestBot

• = The version emoji, this is to the left of the number that indicates the version of the bot, the user or the command

• / = This emoji indicates that the command has been added very recently.

• = Indicates that the command is available

• = Indicates that the command is available.

  • In case that in that section there is a command that indicates that it is disabled, it is because it cannot be used on any Discord server.

  • In case it indicates that it is disabled in dragons, it is that this command cannot be used on any Discord server.

  • If it indicates that it is enabled or disabled on the server, use:

    • To enable a mode: set-mode enable <mode> .

    • To disable a mode: set-mode disable <mode> .

• = Indicates that the command is in testing and therefore there are probably some errors.

• = Indicates that the command requires a . It does not indicate that it has to be from the user or from the server, but when using the command it already specifies it.

WHAT ARE SLASH COMMANDS?

Slash Commands are the new, exciting way to build and interact with bots on Discord. With Slash Commands, all you have to do is type / and you're ready to use your favorite bot. You can easily see all the commands a bot has, and validation and error handling help you get the command right the first time.

Not every bot might be using Slash Commands right now. They're brand new, and it'll take some time for developers to start using them. So, be patient, but get excited!

DISCOVERY

We've all used a !help command and then received a wall of text in response. Now, instead of having to google a bot's commands or look through that long !help answer, you can see all the commands a bot has to offer just by typing /.

This command list will filter commands as you type, making it easy to browse commands or find exactly what you're looking for. You quick typers out there can also use TAB and ENTER to quickly choose and navigate through commands.

AUTOCOMPLETE

For certain values in Slash Commands, we'll help you out with a handy autocomplete! No more needing to remember ids. If you need to pick a user, a role, or a channel, you can use the autocomplete that you know and love to help.

VALIDATION AND ERROR HANDLING

Slash Commands help you learn how to use bots without the awkward mistakes of typing the wrong command into chat, or typing it the wrong way. If you accidentally pick an invalid option, we'll let you know before it sends:

NEW PERMISSIONS

Slash Commands are powerful, but with great power comes great responsibility. So, we've added a new "Use Slash Commands" permission to help keep your server organized. You can turn off Slash Commands for your entire server or for a specific channel by changing that permission.

The "Use Slash Commands" permission only affects commands created by bots. "Built-in" commands like /giphy, /nick, and /me will be unaffected.

HOW DO I MAKE SLASH COMMANDS?

If you want to try your hand at making custom Slash Commands, check out our Slash Commands can be integrated into your existing bot, or you can make something entirely new!

Both systems exit by themselves when you use any command. To update, you must click on the button that says Update and you will be updated. In case you don't get the update message, you can use the update command

To verify yourself

You must click on the Accept button. When you have given it, you are affirming that you are going to comply with the of the Service that we offer.

To update

You must click on the button that says Update and you will be updated. In case you don't get the update message, you can use the update command You can also see the

The command of the bot can be:

• w?

• /

The second it is a

In the , you can see that instead of putting the prefix, we have put {prefix}

What are BADGES and what benefits do they have?

• The badges are for people to recognize you and thus also know if you are trustworthy

• Badges are used to unlock commands or enter a system in general

How are they OBTAINED?

• To know how to obtain it, go to the section

In case it has not been verified use any command and then pykse to Approve to follow the

In case you are verified put start and pykse Adventure

Pykse ▶

Then put pick or get and in the same message the pokemon you want as a partner

Example:

And from here you can use more

The end of H𝛼k𝛼iryu is near...Don't worry, we don't mean to remove the bot, but it will change completely. While we are creating the new bot, it will be called the same and everything will be the same, except that it will go faster, the errors will be sent to ourselves and there will be new things.

• Good things about this.

  • The public bot will have all the functions of Partner, Early Support, Online, MemberShip and Premium completely FREE (without any requirement)

• Bad things about this.

Name: daily

Usage: daily

What should come out?:

For example

Name: omegan-landan

Usage: omegan-landan

What should come out?: A obtion to change to omegan a landan or landan to omegan

Note: λ = Landan | Ω = Omegan | Ψ = Phagan

Conversions: 1499 λ = 1 Ω | 499 Ω = 1 Ψ (can't be passed Ψ to Ω)

Name: acquittance

Usage: acquittance

What should come out?: To give to other user λ

Note: You can give only λ

1ºQuestion = 2ºQuestion = amount 3ºQuestion = confirm

V-1

Added: {prefix}lang, {prefix}spawn, {prefix}catch, {prefix}hint, {prefix}bot-info, {prefix}user-info, {prefix}server-info, {prefix}support, {prefix}say Beta: Update:

V-1.01

Added: {prefix}pings, {prefix}invite Beta: Update:

V-1.1

Added: {prefix}buy, {prefix}shop Beta: Update:

V-1.5

Added: {prefix}m-spawn, {prefix}legend.spawn, {prefix}giga-spawn Beta: Update:

V-2

Added: {prefix}dex, {prefix}redirect, {prefix}totem-spawn, {prefix}info, {prefix}start, {prefix}pick or {prefix}get, {prefix}daily, {prefix}leaderboard Beta: Update: catch, spawn

V-2.5

Added: {prefix}g.spawn, {prefix}reset Beta: Update:

V-3

Added: {prefix}select-partner, {prefix}evolve, {prefix}search Beta: Update:

V-3.1

Added: Button Box, {prefix}t.box, registre system Beta: Update:

V-4

Added: {prefix}hangman, {prefix}akinator, box 1, box 2, box 3, box 4 Beta: Update:

V-4.5

Added: {prefix}traslade, box 5, box 6 Beta: Update: catch: remove "]" and remove block singulars

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

V-

Added: Beta: Update:

• The Bot must have been in the server for 1 week

• Use the bot 1000 times in the server

• Don't break any ruler

• Be on the server AidWorks HelpDesk

Only if you have all, you can solicited the partner. The last request it will confirmed

1. You can use special commands, use {prefix}menu or {prefix}help and press the arrows, to see the commands that are partner

2. At some point, some codes can only be redeemed by partner servers or users

3. You can enter a partner-only server (Server Invite Paused)

4. You will be able to use the new commands before others (Beta)