π§ͺ Kaimux Testers
Testers are part of the Kaimux administration, responsible for ensuring the quality of the servers. Their work involves playing on the servers, finding bugs, inconsistencies, or balance issues, and reporting them to the administration. This is not a creative or moderation role β Testers focus on the technical aspects of the game, helping to ensure stability and a good player experience.
π¬ Tester Responsibilities
Main Tester functions:
- Finding bugs on servers (technical, economic, map-related, etc.),
- Testing new or updated features,
- Checking player-reported issues,
- Participating in group tests (e.g., checking events or maps),
- Submitting clear and structured bug reports in designated Discord channels,
- Helping the administration understand how the bug occurs and what impact it has.
π Work Ethics
Testers must:
- Be thorough and precise when describing bugs,
- Provide information clearly and politely,
- Maintain confidentiality β using bugs for personal or friendsβ advantage is strictly forbidden,
- Collaborate with other Testers,
- Correctly classify bug severity (Minor / Bug / Major / Critical).
π
Tester Hierarchy
Testers are divided into levels according to experience and responsibilities:
1οΈβ£ Jr. Tester
- Entry-level, probation period,
- Plays on servers like a regular player,
- Reports found bugs in the Discord channel.
2οΈβ£ Tester
- Performs all Jr. Tester duties,
- Determines bug severity (Minor / Bug / Major / Critical),
- Helps Jr. Testers create proper bug reports,
- Checks player-reported bugs.
3οΈβ£ Sr. Tester
- Performs all Tester duties,
- Can test new features before they reach the Live server,*
- Helps coordinate group tests,
- Responsible for quality control before major updates.
π Recruitment Process
To become a Tester, applicants must pass several stages:
- Application β fill out the application form,
- Test β questions about testing, logic, and Kaimux project specifics,
- Practical task β perform a task on a Live server under admin supervision,
- Final decision β acceptance or rejection.
π Progression and Responsibility
Testers earn points for their activity. Reaching certain point thresholds promotes the Tester to a higher level. Points never reset β they accumulate over time.
π― Points System
- Minor bug β 1 point
- Bug β 2 points
- Major bug β 5 points
- Critical bug β 8 points
- Participation in group testing β 3 points
- Testing new features (with a report) β 5 points
- Special task β 10 points
πΌ Promotions
- Jr. Tester β Tester: from 50 points
- Tester β Sr. Tester: from 200 points
π° Rewards
Testers receive service balance for their work.
Rewards depend on:
- Number of bugs found,
- Bug severity,
- Participation in group tests,
- Contribution to testing new features or special tasks.
π§ͺ Tester Reward System
Jr. Tester
- Minor bug β β¬0.25
- Bug β β¬0.50
- Major β β¬1.50
- Critical β β¬2.50
- Group testing β β¬0.50
- New feature testing β β¬0.50β1.00 (depending on scope)
Tester
- Minor bug β β¬0.50
- Bug β β¬1.00
- Major β β¬3.00
- Critical β β¬5.00
- Group testing β β¬1.00
- New feature testing β β¬1.00β2.00 (depending on scope)
Sr. Tester
- Minor bug β β¬0.75
- Bug β β¬1.25
- Major β β¬3.75
- Critical β β¬6.25
- Group testing β β¬1.50
- New feature testing β β¬1.50β3.00 (depending on scope)
- Special tasks (assigned by Owner/Operator) β β¬1.00β5.00 (depending on difficulty)
π
Payment
- Rewards are distributed at the beginning of each month for the previous month.
- Only confirmed bugs count.
- Group testing and new feature testing rewards are only given for actual completed work.
π Bug Severity Categories
Testers classify bugs into four severity levels. This helps the administration determine the priority of the issue and the reward amount.
Minor
- Bugs with little impact on gameplay or player experience.
- Example: typos, minor visual inconsistencies, cosmetic details that do not interfere with gameplay.
Bug
- Bugs that can slightly hinder players or cause inaccurate game behavior, but do not break core mechanics.
- Example: buttons not working correctly, minor economic discrepancies (small differences in money).
Major
- Bugs that significantly affect gameplay, economy, or player experience.
- Example: players can exploit a bug to earn large amounts of resources easily, map issues that prevent completing tasks or events.
Critical
- Bugs that can completely disrupt the game, threaten server stability, or severely damage player experience.
- Example: server crashes, bugs that bypass protections, impossibility to complete main functions or events, economic bugs causing huge losses/gains.
π Tester Role β This is not a privilege, but a responsibility. It allows direct contribution to project quality, assisting the administration and ensuring the best possible player experience.
*If/when this feature is implemented.