Opened 8 years ago
Last modified 4 years ago
#4004 new enhancement
Increase playerlimit — at Version 7
Reported by: | elexis | Owned by: | |
---|---|---|---|
Priority: | Nice to Have | Milestone: | Backlog |
Component: | Core engine | Keywords: | |
Cc: | Patch: | Phab:D1662 |
Description (last modified by )
Currently the engine has an 8 player limit, but it could be entertaining to play with even more.
This is a non-trivial change as probably many data structures in C++ components rely on that limit and maps being designed for at most 8 players.
The performance shouldn't be affected significantly if the mapsize stays the same and the population limit is reduced proportionally. As of r17881 the network code already supports up to 24 clients without a noticeable performance impact.
Change History (7)
comment:1 by , 8 years ago
Type: | defect → enhancement |
---|
comment:2 by , 8 years ago
comment:3 by , 8 years ago
Regarding random maps: Perhaps we can implement a lower and higher limit for the available map sizes and the supported number of players? So not all existing maps have to be tested and edited...
comment:7 by , 6 years ago
Description: | modified (diff) |
---|---|
Patch: | → Phab:D1662 |
Priority: | If Time Permits → Nice to Have |
Notice the feature would also be useful for 8 players + scripted enemies that aren't gaia (danubius, jebel barkal)
This is certainly not a trivial task. Next to the many data structures that depend on the number of players (they aren't all limited to 8 players, but most are limited to some number between 8 and 16), there's also the GUI (setup screen, statistics screen, diplo screen, ...).
Having to create scenario and skirmish maps for more than 8 players is to be expected, but player placement on random maps is currently also only tested for 8 players. So all random maps should be retested.
And for every extra two players added, you need to add an extra team possible.