Should the proposed CSLRP open beta go ahead, it would be treated as a temporary testing period rather than the beginning of permanent player progression.
Players would be encouraged to use the server normally, participate in roleplay, explore its systems and join departments.
The purpose would be to test the server under realistic conditions and identify problems that may not appear during smaller internal tests.
Reporting Bugs
Bugs and unexpected behaviour discovered during the beta would need to be reported through the official CSLRP support page.
Players should select the Bugs category when submitting a report.
A useful bug report should include:
- A description of what happened
- What the player was doing beforehand
- Whether the issue occurred more than once
- Screenshots or recordings where possible
- Any visible error messages
Using one central reporting system will prevent important information from becoming lost inside general Discord conversations.
Streaming and Content Creation
Streaming, recording and other forms of content creation would be fully welcomed during the beta.
Players would be allowed to create livestreams, videos, screenshots and other content while experiencing the server.
Creators should make clear that the server is still in a testing phase. Bugs, balancing problems and temporary changes may therefore still be present.
Content creation may also help the development team understand how players naturally interact with different systems.
Player Progress Will Be Reset
All normal player progression earned during the beta would be wiped before the official opening.
This would include:
- Characters
- Money and bank balances
- Inventory items
- Vehicles
- Property
- Business progression
- General economic progress
A full reset is necessary because undiscovered bugs or exploits could otherwise provide players with an unfair advantage.
Everyone should begin the official server on equal terms.
Department Training Will Remain
Department training would be handled differently.
Players would already be able to begin training during the beta, and completed department training is expected to remain valid after the reset.
This allows departments to prepare their members while simultaneously helping the team test equipment, procedures and internal systems.
Temporary Closure After the Beta
After the beta has ended, the server would temporarily close for approximately one to two weeks.
During this period, the team would:
- Review submitted bug reports
- Fix discovered exploits
- Improve server performance
- Adjust balancing
- Complete final configuration
- Prepare the server for official release
The exact duration would depend on the number and severity of the problems discovered during testing.