🌟 ArenaPro Creator Incentive Program

To recognize and inspire every one of you who injects creativity into the ArenaPro ecosystem, we are officially launching the Creator Incentive Program. We believe that a thriving community is built on the selfless sharing, enthusiastic mutual support, and high-quality creations of its members.

This program aims to establish a fair and transparent honor system, ensuring that every contribution you make is seen and acknowledged.

✨ Our Honor Avatar Frames

We have prepared four beautifully designed exclusive avatar frames for you:

• [Glow of the Novice Contributor]: Awarded to new forces who actively embrace the ArenaPro workflow and take a solid first step in creation.

• [Git Collaboration Contributor]: Awarded to creators who are proficient in Git team collaboration and contribute to the standardization and efficiency of projects.

• [AP Code Event Winner]: Awarded to creators who are active or achieve outstanding results in official or recognized community-held code events.

• [Advanced Core Contributor]: Awarded to core members who have made outstanding and far-reaching contributions to the ArenaPro ecosystem. You are the cornerstone of the community.

🎯 How to Unlock Your Exclusive Avatar Frame?

[1] Glow of the Novice Contributor

This avatar frame is designed to encourage you to fully experience the ArenaPro development process and turn your creative ideas into reality.

• Basic Requirement: All applicants must first join the official ArenaPro AP Creator QQ Group: 492953731. This is the basis for our verification and communication.
• Achievement Method: Satisfy any of the following contributions to apply by contacting an administrator in the group.

Contribution Method	Goal and Requirements
Publish Original Work	Goal: Use ArenaPro to fully develop and publish an original expanded map work. Verification Criteria: ① Originality and Completeness: The work must be original to the individual or team, with clear gameplay and a complete experience. Plagiarism or simple porting is strictly prohibited. ② Technical Specifications: The core code of the project must be written in TypeScript and reflect its language features, not just be JS with a changed file extension. ③ Editor Usage: The applicant's account must have at least 14 cumulative effective active days in the ArenaPro editor. ④ Community Sharing: After publication, the work's link must be shared in the official AP QQ group.
Active Community Help	Goal: Actively and kindly answer others' questions in the community for an extended period (at least one month). Verification Criteria: ① Content Relevance: Answers must be highly relevant to ArenaPro editor usage, TypeScript programming, or related workflows, and genuinely help others solve technical problems. ② Official Recognition: Must be recognized by an official AP administrator.

💡 Your ArenaPro Learning Map

Here is a core knowledge map we've prepared for you, hoping it will help you successfully publish your first work:

1. Master TypeScript Core Basics
   • [ ] Understand and use basic TypeScript types like string, number, boolean, any[].
   • [ ] Be able to use interface or type to create type definitions for complex game objects (e.g., player attributes, items).
   • [ ] Master function type signatures (parameter types and return value types).
   • [ ] Be able to use import and export to organize and reuse code modules.
2. Familiarize Yourself with the ArenaPro Development Workflow
   • [ ] Successfully create an ArenaPro project and understand its basic directory structure (src, dist, package.json).
   • [ ] Be proficient in using VSCode to connect to the game and perform hot-reload debugging.
   • [ ] Understand the difference between the client and server directories and be able to write code in the correct entry point.

[2] Git Collaboration Contributor

This avatar frame recognizes your mastery of standardized, engineering-focused development processes, especially the excellent use of Git in team collaboration.

• Basic Requirement: All applicants must first join the official ArenaPro AP Creator QQ Group.
• Achievement Method: Satisfy any of the following contributions to apply by contacting an administrator in the group.

Contribution Method	Goal and Requirements
Standardized Personal Project Management	Goal: Demonstrate professional, standardized full-cycle Git management in a personal project, capable of independently maintaining a project with a clear structure and standard version iteration. Verification Criteria: ① Professional Git Flow: The project must follow the Git Flow specification, reflecting a clear branch management strategy.     - Merge Path: Each feature branch should be merged back into the dev branch upon completion; the phased results of dev are eventually merged into the main branch. ② Standardized Commit History:     - Commit Count: The entire project must have at least 20 meaningful commit records.     - Commit Format: It is highly recommended to follow the Conventional Commits specification (e.g., feat:, fix:, docs:), or maintain a consistent, clear custom style. ③ Rigorous Version Releasing:     - Release Tags: Every significant version on the main branch must be tagged with a semantic version number (e.g., v1.0.0, v1.1.0). The project must have at least 2 version tags. ④ Complete Project Documentation:     - The project root must contain a high-quality README.md that clearly explains the project's functionality, how to use it, and its development status.
Active Participation in Team Collaboration	Goal: As a core contributor, deeply participate in a public, two-person or more ArenaPro community project and make continuous, valuable contributions. Verification Criteria: ① Continuous Contribution: Successfully submitted and merged at least 10 valuable Pull Requests (PRs) to the same community project. ② High-Quality PRs: PRs must demonstrate diversity and depth, such as fixing core bugs, implementing independent feature modules, refactoring code, or improving important documentation. All PRs should adhere to high standards:     - Link to Issue: Any non-trivial change should first be discussed in an Issue, and the PR should link to it.     - Clear Description: Detail the background of the change, implementation ideas, and testing methods.     - Small and Focused: Each PR should focus on solving one problem, avoiding mixing multiple unrelated changes. ③ In-depth Collaborative Communication:     - Respond to Reviews: Be able to efficiently make multiple rounds of code modifications and discussions based on review feedback.

💡 Skill Checklist to Unlock "Git Collaboration Contributor"

This is a tailored skill checklist to help you master an industry-grade Git workflow and successfully unlock this honor.

1. Git Flow & Personal Project Management (Corresponds to the "Standardized Personal Project Management" path)
   • [ ] Master Git Flow: Be proficient in using the feature -> dev -> main branch development model.
   • [ ] Practice Conventional Commits: Learn and use standardized prefixes like feat:, fix:, docs:, refactor: to write commit messages, making the history clear and readable.
   • [ ] Implement Semantic Versioning: Be proficient in using git tag -a vX.Y.Z -m "Release notes" to create and mark important release versions for your main branch.
   • [ ] Write Professional Project Documentation: Be able to write a high-quality README.md that clearly introduces the project background, core features, installation, and usage methods.
2. Team Collaboration & Pull Requests (Corresponds to the "Active Participation in Team Collaboration" path)
   • [ ] Create High-Quality PRs: Practice breaking down large tasks into small, focused PRs and write clear titles and detailed descriptions for each PR, explaining the "why" and "how."
   • [ ] Link Issues & PRs: Learn to associate your PRs with relevant Issues on Gitee/GitHub using keywords (e.g., closes #123) to form a complete workflow loop.
   • [ ] Participate in Code Review: Be able to efficiently modify code locally based on others' review feedback and update the existing PR branch using git push --force-with-lease (recommended) or git push -f.
   • [ ] Keep Branches in Sync: Be proficient in using git fetch and git rebase (or git merge) to sync the latest changes from the target repository to your development branch and proactively resolve any potential merge conflicts.

[3] AP Code Event Winner

This avatar frame is an exclusive reward for periodically held official ArenaPro code events and is a symbol of honor and skill.

• How to Obtain: Participate in themed programming challenges, Game Jams, code sharing sessions, etc., initiated or co-organized by official AP, and meet the reward conditions specified for that event.
• Follow Channels: All event information will be announced first in the Official ArenaPro AP Creator QQ Group. Please pay attention to group announcements and notifications.

[4] Advanced Core Contributor

This honor is awarded to members who have made outstanding and far-reaching contributions to the ecosystem. Satisfying any two of the following different categories is required to apply.

• Basic Requirement: All applicants must first join the official ArenaPro AP Creator QQ Group.

Category	Contribution Method	Specific Requirements
A. High-Quality Content Creation	Boutique Game	A work developed with ArenaPro that has been officially rated as "Recommended," "Featured," or has received other official honors of the same level.
	Open Source Tool Library	Wrote and published a high-quality, reusable NPM package for other creators (published under the @dao3fun organization), which must be officially evaluated or proven to be adopted by multiple community projects.
B. In-depth Community Contribution	Quality Tutorial	Wrote an in-depth ArenaPro tutorial or technical practice article with rich text and images, and it has been included by AP officials in the official documentation, tutorial cases, or community highlights.
	Community Leadership	Served as an administrator of a core community or a long-term (three months or more) recognized technical leader, making outstanding contributions in maintaining community order, leading technical discussions, and organizing community events.
	Event Organization	Independently or leadingly initiated and successfully organized at least one influential community AP code-related event, such as an online Game Jam, themed sharing session, code challenge, etc.
C. Key Technical Breakthroughs	Code Contribution	Submitted a valuable Pull Request (PR) to the Box3 Lab Gitee/Github open source project which was successfully merged.
D. Collection of Honors	Honor Collection	Simultaneously possess [Glow of the Novice Contributor], [Git Collaboration Contributor], and [AP Code Event Winner].

🚀 Application and Review Process

1. Join the Group: Ensure you have joined the official ArenaPro AP Creator QQ Group.
2. Prepare Materials: Based on the conditions you have met, prepare the corresponding proof materials (e.g., work link, Git repository address, community chat screenshots, Issue/PR links, etc.).
3. Submit Application: Contact any official AP administrator in the QQ group and send your application reason and proof materials via private message.
4. Official Review: The official AP team will review your application within 7 working days.
5. Honor Granting: After approval, we will issue the corresponding avatar frame reward to you.

❓ Frequently Asked Questions (FAQ)

• Q: Can I apply for multiple avatar frames with the same project?

  • A: Of course! We fully support "double-dipping" and encourage continuous investment in your work. For example: ① You received the "Novice Contributor" for project A; ② You later introduced a standardized Git Flow and version management, you can then apply for the "Git Collaboration Contributor" with it; ③ If this project is later officially rated as a boutique, it can still be used as material to apply for the "Advanced Core Contributor."

• Q: How is the "cumulative effective active days in the editor" for the "Novice Contributor" calculated?

  • A: An "effective active day" refers to a day when you have performed actual operations in the ArenaPro editor (such as saving a script, editing a scene, debugging, etc.) and compiled code to the map. You do not need to be online all day; as long as there is a valid activity record for the day, it is counted as 1 active day.

• Q: When applying for the "Git Collaboration Contributor," do I need to meet both the "Personal Project Management" and "Team Collaboration" requirements?

  • A: No. These are parallel paths. You only need to choose one of them and fully meet all the verification criteria under that path to apply. We encourage you to choose the one that best suits your actual situation and project experience.

• Q: We are a team. How are the rewards distributed?

  • A: We do not accept group applications on behalf of a team; all honors are awarded to individuals only. For projects completed by a team, all members who made core contributions can apply independently. We primarily use the project's Git commit history to objectively evaluate each member's contribution amount and specific role. Therefore, a standardized Git commit record that reflects individual work is key to the application. When applying, please also briefly explain your main responsibilities in the team.

• Q: What if my application is rejected?

  • A: If your application is not approved, you can always ask the reviewing administrator for the specific reason. After making improvements based on the suggestions, you are always welcome to resubmit your application.

• Q: Do my contributions before this plan was announced count?

  • A: Of course! This incentive plan retroactively includes all historical contributions. As long as your contribution meets the above standards, you can apply.

---

Every line of code, every share, is a brick in the wall of our shared creative world. The ArenaPro team thanks you again for your support and love, and we look forward to seeing more avatars shining with the glow of contributors in every corner of the community!