Tester Program Rules & Authorization

1. Program Model

The beta may be live through a restricted Tester page on the ML website. Creating an account, applying, receiving a link, or possessing credentials does not authorize testing. Only the approved individual may use the approved account. No account or credential sharing and no allowing another person to use restricted access without express ML authorization.

2. Authorization Record

Populated by ML on approval — not editable by Tester.

ML may revoke or narrow authorization at any time.

3. Authorized Testing

Tester may access/play the approved beta, reproduce ordinary bugs inside the approved environment, submit private reports and authorized supporting evidence, and perform other testing expressly assigned by ML.

Ordinary QA does NOT authorize probing unrelated ML website areas, admin pages, other accounts, authentication, unrelated APIs, servers, infrastructure, networks, databases, client systems, third-party systems, or unrelated projects. Security testing requires separate express authorization.

4. Reporting

Report bugs, crashes, exploits and suspected vulnerabilities privately. Useful reports may include observed result, expected result, reproduction steps, frequency, environment/device, authorized screenshots/video, and logs where requested. If out-of-scope information is accidentally encountered: STOP exploring, preserve only what is reasonably needed to report it, report privately, and do not disclose it.

5. Conduct

Use only the approved personal account; protect credentials; report compromise; keep beta material confidential; follow scope; do not intentionally disrupt other testers; do not perform destructive testing unless specifically authorized; stop testing an area when ML revokes/narrows access.

6. Participation Rewards

The current program uses participation rewards rather than ordinary cash compensation. Rewards recognize sustained useful participation and good standing and remain subject to technical feasibility, development status, platform rules, content/rating requirements, production constraints, and ML approval. Unless separately agreed, the program does not promise wages, salary, royalties, revenue share, ownership in ML, or permanent availability of particular game content. Applicable law controls classification.

7. Base Tester Reward

A tester who completes applicable testing/release requirements in good standing is intended to receive: one free copy of the released game; and credit by legal name or ML-approved tester name as a Tester.

8. One-Month Reward

After at least one month of active participation in good standing, Tester becomes eligible for a MINOR INTERACTABLE NPC visually inspired by/designed with Tester. Use of submitted name/likeness/reference requires Tester's voluntary participation and is subject to ML adaptation, game-world fit, technical feasibility, content/rating requirements, and platform rules. Tester may request an approved fictional/alternate concept instead of personal likeness.

9. Two-Month-Plus Rewards

After at least two months active and in good standing, Tester becomes eligible for:

A. Tester-Designed Model Rocket — Tester may design/concept and name, with ML approval, a model rocket intended for inclusion as an unlockable in the game. ML may adapt it for gameplay, performance, art direction, technical requirements, and production.

B. NPC Role With Full Quest Line — Tester becomes eligible for a substantial NPC role with a full quest line, subject to ML final writing, design, technical, rating, and production control.

C. Tester-Only DLC Rocket Cosmetic Pack — Tester-only aesthetic variants of in-game model-rocket parts may include parachute textures, special motor-flare appearance, and other approved cosmetic treatments. These are intended as cosmetic rather than competitive gameplay advantages unless ML later deliberately changes the design.

D. Tester-Only Player-Character Cosmetics — Tester-only player cosmetics may include shirts, hats, and other supported tester-specific cosmetic items.

10. Good Standing

Good standing generally means Tester remains approved, follows the NDA and Rules, does not share the account or leak confidential material, respects testing boundaries, participates with reasonable continuity, and does not abuse Tester access. Temporary inability to test is not automatically misconduct; ML/UserSubmit may handle individual circumstances.

11. Reward Material / Consent

Tester should submit only reward material they have the right to provide. ML may modify/stylize concepts so they function in the game. The NDA contains the intended license for Feedback and voluntarily submitted Reward Material.

12. Development Reality

Rewards are intended as genuine recognition, but implementation may need reasonable adaptation, substitution, delay, or discontinuation because of technical limits, platform/legal/rating requirements, major design changes, system cancellation/redesign, or production feasibility. ML should not use this provision to casually erase earned tester recognition.

13. Access End / Closeout

When access ends, Tester stops using restricted access/builds; NDA obligations continue; required local restricted copies are deleted/returned; unresolved serious findings are privately reported; and ML preserves appropriate participation/reward records. Ending beta access does not automatically erase a formally granted reward, but final treatment can depend on termination reason, reward stage, development feasibility, and separate agreements.

14. Age

Draft launch default: TESTERS MUST BE 18+. If ML later admits minors, create a separately reviewed guardian/youth flow.

15. Website Flow

1. Application/invitation
2. Identity/contact recorded
3. Account created/linked
4. NDA electronically accepted
5. Current Rules accepted
6. ML approval
7. Tester access enabled
8. One approved human uses account
9. Beta testing/private reports
10. Participation/reward tracking
11. Access review/revocation/expiration
12. Closeout
13. Records preserved

Website should preserve where practical: NDA/rules versions, tester/account, acceptance timestamp, approval status/timestamp, project/build authorization, access status, reward milestones, and closeout/revocation state.