For now, there is only one UDP channel working on the server. That may be the reason causing an issue that in case of high load, a lot of UDP messages dropped. Therefore, implementing a new feature that allows setting up multiple channels UDP might resolve the issue.

Prerequisites

• [x] The number and ports number can be configured in the configuration file
• [x] Each client-side will automatically pick a UDP channel for communication. The algorithm might be the "round-robin"

… amount of UDP channel will be opened on the server

The UDP channel port will be chosen arbitrarily. The client should be received this value from the server when required.

There are some commands applied when running the server to purposely control it. To illustrate.

$ java -jar server.jar configuration=configuration.xml command=on scripts=/scripts

With the increasing of number of commands, they need to be managed better.

Prerequisites

• [ ] The configuration flag is must
• [ ] Command flags are only applied if present, unavailability means there is no effect as well
• [ ] Order does not matter

Creates new implementation for the web-socket implementation between client and server-side. The client-side handling is missing for the new server version. It needs to implement the serialize and deserialize methods based on the ticket: https://github.com/congcoi123/tenio-core/issues/12

It is necessary to be able to control the game server behaviors in a debug mode. The idea should like when running the following command.

$ java -jar server.jar configuration.xml command=on

Then a command console appears. It will listen input instructions from the user and execute them.

Prerequisites

• [ ] There are two modes: on and off. In off state or in case of no declaration for command, the command console will not be present
• [x] All commands should be implemented, declared by annotations for easy implementation and extension
• [x] Commands execution must use the ServerApi to interact with server, there should not have any exception

Prerequisites:

• Each client needs 2 UDP connections, one for sending data and the other one for receiving information from its interested area.
• The game server opens multiple UDP channels and does a mapping between grids of areas and their corresponding IP groups.

This is a missing feature and should be implemented. Reference: https://github.com/congcoi123/tenio-core/blob/master/src/main/java/com/tenio/core/schedule/ScheduleServiceImpl.java#L92 https://github.com/congcoi123/tenio-core/blob/master/src/main/java/com/tenio/core/schedule/task/AutoRemoveRoomTask.java

This is a missing feature and should be implemented. Reference: https://github.com/congcoi123/tenio-core/blob/master/src/main/java/com/tenio/core/schedule/ScheduleServiceImpl.java#L91 https://github.com/congcoi123/tenio-core/blob/master/src/main/java/com/tenio/core/schedule/task/AutoDisconnectPlayerTask.java

Allows a server to be able to extend its features by supporting the plugin mechanism. In short, there would be a folder (such as a plugin) in which the user puts their built .jar files. When the server starts, it will load all the plugins available and then run as expected.