For a game idea I have in mind, I'm probably going to need my own type of lobbyserver. But I wanted to see an example of an existing one first to see if I had to program from scratch or not.
Well I just downloaded the sources and got them compiled in my eclipse. Except the fact that @Override is used on tons of methods with no fitting interface or inherrited parent method, but I can get around that.
Most of the code is pretty straight forward, although I never worked with OSGI in my life before, I think I would get the hang of it pretty quickly.
Now for what I'm trying to achieve. I like to make a collectable "warhammer esque" game in a persistant type of hex based map. Think shattered galaxy with a twist. After some research I believe that creating the lua for the game is going to be a breeze. Especially that I allready made that kind of gametype around last year. Some of you might remember.
I have a prove of concept running with spring MVC about how to construct squads from a collection. I made a REST service for that and a web client and it's all working. Now I need a new prove of concept.
I need a lobbyserver that is able to host battles, and when a battle is won or lost give the players a "currency". I also need it to keep track of a hexmap and be able to start battles on a specific hex, and when certain factions win a game, change faction on that hex. I believe the most though part is allready written in SpringLS when I skim the sourcecode. There are some parts I don't understand yet though.
Where is the link to SpringRTS ? What takes care of actually starting the game engine , keeping track of a battle, keeping track of disconnects etc ? Is this handled serverside ? Or is it that founder type of user that keeps track of that and a seperate lobby client ? If this is handled client side I believe I'm in a lot of trouble cause client side can be manipulated and open the door to massive cheating
Any insight would be appreciated, from what I gather the magic happens in all the commandimpl's
oh btw : your hibernate is massivly outdated and seperation of layers is not really adhered I believe, Personally I would put the entitymanager in a seperate abstractrepository class and pro entity type I would create a repository. But thats just my personal programming preference