merge(core/layers): layers system into main#1
Merged
Conversation
…rId, Map::m_worldLayer
…d group join transfer
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Implements a layer system that allows multiple layers to spawn within the same map. By default, each layer supports up to 400 players, but the system is dynamic, meaning a map can handle additional layers depending on the number of active players.
Layers can only be changed while in a group, ensuring that all group members stay in the same layer and preventing abuse of the system.
The layer system has been tested with 2 layers without any issues, though testing was only done with 4 players, so more extensive testing is still needed. Layer switching is almost unnoticeable, and each layer runs on its own thread.
Additional configuration options have been added to worldserver.conf, allowing modification of:
Type of change
Testing
Checklist
YYYY_MM_DD_NN_database.sqlnaming scheme