- This topic has 1 reply, 2 voices, and was last updated 8 years, 8 months ago by
.
-
Posts
-
Don’t hate me, but we don’t refund here (please see Disclaimer off of the home page). If you are a donator, I go out of my way to help you out, but that is it. Otherwise, you are a player that is playing on my public server, which is provided without warranty.
That said, this is a bug in ExileMod code that was introduced a few months ago and is plaguing the community. Every time I search exilemod.com for answers, I find random suggestions and try them out. It’s not only annoying for you (the players), but it’s annoying for me (the admin) to constantly having to hunt for fixes where the database did not store a player’s stuff. It’s like a fundamental use case of ExileMod and frankly I am surprised the development team has not figured it out, or done longevity studies on their code to find these database save issues ahead of time. To their defence, there are so many types of server hardware and database implementations out there, I am sure it is hard to get this right (even though they had it right and broke it and other mods have not had these issues in the past).
I have run all of these types of Arma mod public servers in the past and never had issues with database saving: Arma 2 DayZMod, Arma 2 DayZMod + EpochMod, Arma 2 Overwatch, Arma 3 Wasteland (all kinds of different implementations), and Arma 3 EpochMod. All of them ran perfectly with no database saving issues… This current problem is exclusive to: ExileMod
– terd
- You must be logged in to reply to this topic.
