Model refactor to handle Instances #31
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently, we have a Game model. And a game can have a Server. Which was alright for situations say where you have a Game say Insurgency and then two Server models for that game say coop and pvp.
Without complicating into edge cases and talking game mods. We want 3 pvp servers, this model fails. port maps will need to change for the host. And the
name
field which is being used for the container name will collide although this is relatively simple.There are hacky ways around this. But instead we could imagine a game. Quake 3 Arena. And you have a Server for deathmatch. But there may be different rulesets that people like and hence we want more instances. THen what about spin offs such as Rocket Arena.
HEnce it’s better to consider the
Server
model as a template for a server for a game. We keep container_port/proto field from the template but can map it on the host to an inherited ServerInstance model.this is just me putting down the thoughts as they come. Should fully flesh it out. Changing the models isn’t a fun time.