MorePlayers is a multiplayer-mod record for a bundled BepInEx route, game-folder extraction, and a recorded configuration path. It only establishes how participants can align one known installation record, configuration location, test, and rollback plan. The player ceiling and any network or runtime outcome remain To be confirmed.
What this multiplayer-mod record establishes
The captured record identifies MorePlayers as related to a multiplayer lobby. This page keeps that role limited to the recorded installation and coordination workflow. It does not turn the mod name into a fixed player-capacity claim.
Treat the route as a shared change that needs a clearly recorded baseline. Keep the files and configuration under review identifiable before any test. That boundary makes it possible to compare a later result with the unmodified state.
Use the bundled BepInEx route
Use the bundled BepInEx route named by the captured record. Keep it separate from any other loader arrangement already present in the game folder. Whether another arrangement can coexist remains To be confirmed.
Record that this route is the one being tested before changing anything else. Do not infer a version requirement from the bundled route. Current loader details beyond the recorded route remain To be confirmed.
Extract to the game folder and record the config
Extract the recorded package to the game folder. The configuration path to record is BepInEx/config/MorePlayers.cfg. This page does not confirm a different extraction destination.
Preserve the pre-change game-folder state before editing a configuration. Keep the exact configuration path in the same change record as the extracted files. That record limits a rollback to the changes introduced for this setup.
Coordinate participants and test one shared setup
All participants should coordinate the same installation record, configuration, testing steps, and rollback plan. Start from a single agreed state so each observation refers to the same setup. Record what was checked without extending the result beyond that test.
If the test result is unclear, return every participant to the shared recorded baseline. Review the installation record and configuration path before choosing one next change. This is a staged testing method, not a promise about a multiplayer outcome.
Player-limit and network claims to confirm
The player ceiling, network behavior, and runtime outcomes remain To be confirmed. A single shared test does not establish compatibility for another setting or future session. Keep unverified results outside this page's conclusion.
Do not convert a local observation into a claim about performance, safety, servers, or long-term compatibility. Retain the shared rollback record until the tested change has been reviewed. Any result beyond the recorded installation workflow remains To be confirmed.