Quote:
Originally Posted by Tigairius
Well, I agree, it would be nice; for example, for UN's hat system, I had to store peoples' hats in text files on the server and then load them into the person's string on login (due to the fact that some people had so many hats); but for most circumstances, it's inappropriate to have a string attached to the player that's > 255 characters in length.
|
Well my point is sometimes you're going to just have a lot of data. For example, if you used a simple switch/flag system that Classic used to use, where you set a flag when an event happened to make sure it didn't happen again, add up a lot of those and you're going to end up with a lot of event flags. What's the difference between having 20 strings or having one string with 20 values? Even if I save them in a file, they're going to have to be loaded and stored somewhere in memory anyways, no?
I just don't understand why such a simple change would be dismissed. As far as I know, Stefan can update the serveroptions and RC commands from the gserver and do an update that wouldn't require any updates to RC at all. I may be wrong, but that was my impression. I know even if it's not wise to use large strings, servers
do and it's stupid to lose important player data just because of an outdated RC tool.
I'm not saying we should all start using huge client strings and all, but when the occasion arises that a string does get long we shouldn't lose it to a bug. Especially when sometimes you might not even be aware!