multiplayer

Required skills: Python

Difficulty: Easy

For the initial asset conversion, openage provides textual output to signal which stage of conversion has been reached. The output usually looks like this:

INFO [py] converting metadata
INFO [py] [0] palette
INFO [py] [1] empires.dat
INFO [py] Starting conversion...
INFO [py] Extracting Genie data...
INFO [py] Creating API-like ob

OpenRCT2/OpenRCT2#15489 showed that the * and / operators of ZoomLevel cause some confusion. Instead of the operators, member functions could be used to increase or decrease a given value. Something along these lines:

int32_t zoomedIn = zoomLevel.ApplyTo(unzoomedValue);
int32_t zoomedOut = zoomLevel.ApplyInversedTo(unzoomedValue);

Currently we expose some controls in the debug panel to allow for quick state resets as well as state save/restore:

These make use of the local client reducer to manipulate the cl

Is your feature request related to a problem? Please describe.

I would like the Game Server de-scheduling logic to be more accurate based on GS states or tune-able in the context of a single node.

Given the following scenario:
1 hot game server exists and 0 sessions exist. A session is requested via the Matchmaker.
The matchmaker creates a GameServerAllocationRequest to set GS1 to `All

If there are repeated matches, how does the evaluator expand horizontally？thanks

Describe the feature you'd like
We should limit the miss angle to effectively be around 15 degrees.

Describe why do you think it is needed
Missing a target by 90 degrees just look stupid - a miss is a miss. Doesn't have to be that off 😁

https://www.reddit.com/r/warzone2100/comments/gy87wg/rookie_units_are_as_helpful_as_ever/

Is your feature request related to a problem? Please describe.

Killing one script at a time is a complete and absolute pain when doing testing. Especially if the code is already in disarray and generating a plethora of identical scripts.

Describe the solution you'd like

Please add support for killing a range or sequence

Describe the bug
If you spawn a Player Object explicitly like this:
newPlayer.SpawnAsPlayerObject(clientId, null, true);

It will clean up if the player disconnects. But if the server force-ends the client connection via DisconnectClient, the object is left hanging around.

![image](https://user-images.githubusercontent.com/27827009/117048953-90afee00-ace1-11eb-9217-e94ba2331e41.pn

Describe the bug

• Objects set to breakable="false" in map remain breakable (hay boxes, object ID 996, object ID 3280 and many more)

To Reproduce

• Set any of the objects I mentioned above to breakable="false"

Expected behavior

• Objects become unbreakable and do not fall apart after a heavy weight passes on them

Screenshots

This is a feature proposal issue
It would be nice to be able to bind Quilkin's sender socket to a given address and port pair. When Quilkin proxies the packets to an upstream host server, it chooses a random socket to use. This feature would remove the randomness and allow us to control which address and port pair to use.

Why do we need this?

• The first reason behind this feature request

The CMakeLists files of this project is kinda messy, mostly due to my limited understanding of the topic.

So they definitely need to be cleaned up at some point