At the moment the LevelManager which handles level loading, saving, updating and deletion on database level does not have any type of caching, this could potentially overload the database and should be high priority.
This hasen't been issue due to low player count not effecting it that much and due to small complexity it provided hasen't been worth enought for me to implement it
At the moment the LevelManager which handles level loading, saving, updating and deletion on database level does not have any type of caching, this could potentially overload the database and should be high priority.
This hasen't been issue due to low player count not effecting it that much and due to small complexity it provided hasen't been worth enought for me to implement it