Going to quote Wizardry's post in parts, since there's too many bits I'd like to respond to, I deem this to be the most organized way to do so.
Link to the PK discussion. (Which is highly monitored by GMs)
Link to the GTB change topic/poll.
Might I remark that the new GTB effect (50% of magic damage reduction) was already done, tested and ready to go. However, people didn't want the change. Hence, it wasn't done. How are we exactly not doing what the players ask of us?
Was your "fix" of great importance to the server or just another of your pet-peeves? Referring back to the PK topic, you only pointed out that your main concern was getting killed when MvPing, whereas you gave no input to how this affected the community. Unless you specify what exactly was the "fix" you so complained about Genesis about, I'll believe it was nothing but a caprice.
Screenshot or didn't happen. You've also got to remember that RO communities are diminishing in General. The server is even listed as one of the top servers, our RMS reviews are almost impeccable and the daily player feedback we get is almost always perfect. People who play here often stay here.
The one bit made me grin. We already have moscovia's map as a city. NPCs and monsters are still not released simply because there is not stable eA version of them. Bug free, highly unlikely. You could go onto the forums of servers who say they're the first ones to offer "bugless" updates, what do you do? You log onto their forums and see miles of topics complaining about bugs. These server owners simply do not realize that, unless they run a debug on the entire game (or close to, something eA devs do). We simply have much more to offer than some half-worked updates of new cities/monsters. Updates on fRO come, more or less, monthly. Which, might I add, is a good pace considering GMing/Developing is not our job.
It's always nice to talk with someone who speaks for millions of players worldwide. I could state that players love to get hacked and abused by the GMs and that that's the reason they stay on a server, and, you know? It'd hold the same weight as the statement I'm quoting; none. Unless you've got charts and an investigation, don't come here and tell us what people look for in a server.
This statement right here sets the base as to what your coding experience is; none. Now since I know you'll just love to talk back at me on this one, I'll make it simple for you. Imagine, for the sake of the argument, that the whole RO program looks like this:
http://img67859.pictiger.com/images/15958279/
This is nothing alike RO nor the complex system it is, but for the sake of the argument, bear with me.
Now, let's assume your "number change" belonged to the B1 function. Good, that's done, but wait. Since the C1 and C2 functions are derived from the B1 function, then we need to check if that numerical change doesn't affect the variables inside C1 and C2 functions. It is highly probable that variables used in the B1 function are to be used in the derived functions, namely the C1 and C2 functions. Any numerical change that affects the gameplay are on variables. Which means that the C1 and C2 variables could very be changed without notice and thus, errors occur. Not only that but almost all functions in the RO program is made to return a value to the function they're derived of. Which means we've got to check to check all of the parent functions as well. The A function could very be the derived function of another function, which means we'd need to check that one too. Finally, there could be the instance that the C3 function also happens to use a variable in the B1 function, which means we'd have to check any derived and parent function of the C3 function as well. Finally, functions in the RO code are normally about this size in lines of code, there are also almost no comments.
All that just for a number change. Simple, isn't it? Now getting back to reality, RO's code is much more complex than this, you can only imagine the hassle we take to make even the smallest of changes. Even if you say you didn't understand what I previously wrote, it just proves my point further; any half-knowledgeable programmer can understand the latter paragraph.
So my final say is this: You're entitled to your opinion about how we work and, as biased as it can be, you're entitled to share it. However, when you want to throw in facts, be sure they are right because you'd best not look like an imbecile while throwing fake facts. Let me be the one who drops the line for you: You are not going to tell Genesis or I about updating, coding or pleasing players in general.
