Crow Game Server (crow.game)

crow.game.codec.api - [95%]

We designed a PacketReader interface that helps us further decouple the netty code from our API. We still need to do PacketWriter.

crow.game.codec.netty - [95%]

Not a bunch of changes. We have attempted to add ‘size’ as a packet detail for dynamically sized packets but we are still not reading it property. AccountReg2StoreRequestHandler is an example where we have size but still have to read it again at the start of fromPacket.

(NEW) crow.game.login.api, proto, and server [???]

These 3 modules constitute the required business logic objects, the protocol details, and the tcp server and business logic-tcp bridge code. I had originally wanted to keep it to two modules, proto and server, which would act as sort of an API and Impl. However, the login API constitutes shared objects between multiple servers, such as ha0… which we will get to.

(NEW) crow.game.ha0.proto and server [???]

In order to best code and test this server, I wanted to have it interact with existing rathena servers. (See note1). This ha0 proto and server act as the protocol objects and netty server, respectively, in order to provide a dedicated port for the rathena char-server to connect to.

As mentioned in the login module notes, the ha0.server requires objects from the login.api module. This constitutes shared state that these two servers need to share in order to function.

Here is a sequence diagram showing the flow of messages.

Uppercase messages are TCP messages encoded and decoded via the module crow.game.codec.netty. The red boxes are TCP servers listening on dedicated ports. The Blue boxes are in-memory singletons shared between all the other components. Everything encaspulated in the black line is part of this codebase so far.

(NEW) The OMNISRV!!!

This module will eventually be a single jar file that just contains everything you need. For now, since we need our login server to connect to the existing rathena servers then the omnisrv does the following:

• import ha0 tcp server
• import login tcp server
• implement the interfaces needed for both of those servers.
  • The UserAuthenticator, the UserLoader.
• Inject these implementations int the tcp servers and start them.

For now, the omnisrv connects to mysql but eventually, if and when we get a char-server and a map-server done, then the omnisrv should be able to run on it's own. No MySQL (unless you want it), no other servers, etc.

Here is the psuedocode for this, showing off how we can build our own implementation details (in the dot-dot-dots) and how we can toggle components on and off via environment variables or flags:

public class Main {
    public static void main(String[] args) {
        UserLoader userLoader = new ...;

        ActiveUserCollection activeUserCollection = ...;
        UserAuthenticator userAuthenticator = ...;

        PendingAuthCollection authCollection = ...;
        ServerCollection servers = ...;

        LoginServerMain loginServerMain =
                new LoginServerMain(
                        activeUserCollection, userAuthenticator, userLoader, servers, authCollection);
        Thread thr1 = new Thread(loginServerMain);
        thr1.start();

        if(System.getenv("USE_HA0")) {
            HA0ServerMain ha0ServerMain =
                    new HA0ServerMain(activeUserCollection, servers, userLoader, authCollection);
            Thread thr2 = new Thread(ha0ServerMain);
            thr2.start();
        }
    }
}