07-09-2016, 07:39 PM
(This post was last modified: 07-09-2016, 08:48 PM by Grimm_Wolfe.
Edit Reason: Additional Argument
)
(07-09-2016, 10:01 AM)Thorsassin Wrote: I agreed it's a dire issue yes, that happens in discussions, but not a reason for a reset in my opinion. the server is worth keeping as is with its band aids with only a few regulars affected so far and for the most part recompensated. Basically while its serious, it's not game breaking for every player on the server where the server needs to be reset.
So you're okay with the severely broken economy, the server glitching to the point people lost resources/homes/warps, all CoreProtect logs being purged because of said glitch, world-guard regions taking up too much data-space, x amount of inactive players with active redstone clocks causing lag, horses are now broken on the server, overcrowding, an outdated OverWorld, and you're saying we don't have enough issues to warrant a server restart? What about when the inactive players come back and find themselves affected by a glitch, do they not matter then? It may not be game-breaking for 100% of the players, but there are enough to warrant a reset.
You're also–again–contradicting yourself. You cannot agree with me saying we're dealing with a dire issue and then go on to effectively say, "yes, it's serious, but not serious enough to warrant a reset". When I say "dire issue", I mean it's an issue that demands an immediate, effective solution to be fixed; an issue whose solution is non-negotiable for the sake of the server's future. When you try mitigating my statements' nature, you're ignoring what I've said.
In my opinion, it seems to me that you will never draw a line for when we should reset as long you have yours. At the very least, that's how your argument makes you sound.