The styling and readability bit is quite lackluster. Sure, nobody wants to inspect a server with hundreds of nearly illegible forms of print, but the fact that both, NC and the Graal Editor, allow for styling should completely dismiss such a rule to most degrees.
You gave such a horid example, Skyld. If anything, I would hold the rule to those that code in single lines, something along the lines of:
NPC Code:
function onCreated() {if (this.foo == this.bar) {this.something = this.somethingelse;}}
or even
NPC Code:
function onCreated() {
if (this.foo == this.bar) { this.something = this.somethingelse; }
}
Because with your example, I could easily copy that code, and paste it in an empty npc on Graal Editor, and press the Style button, and viola.
But for the most part, code can be easily styled via the Graal Editor, or even NC, but I believe NC misplaces brackets when styling or it misplaces triggers (not sure exactly which).
I don't believe that lack-of-styled scripts should give a server an automatic failiure. I believe the GST should aid them in the proper forms of styling code, or even, helping them have it styled via Graal Editor. Some coders choose to style code in a specific way, and sometimes that way makes it harder for others to read, but is natural to them. It would be rather unfair for one to dismiss the content of a server just because the GST has a hard time reading the code. If the code is to the point where even styling it would do no good, then chances are, it possibly has tons of inefficiency and loop holes, and therefore, this rule could apply, but other then that, I would have some discrepancies with how it is carried out and enforced.
The GST should be around to aid the players, not ignore them because their method of styling, if any, is un-ordinary. Help the players, do not discourage them. If all of their npcs are horribly styled, then show them methods of styling. Maybe you could even style one of their currently un-styled npcs, as an example. After that, have them style another npc, and you judge how well they styled the npc. If they have done a good job, tell them you'd come back later that day or on another day, and even tell them that you would help them if any help is needed. The more global-to-staff interaction there is, the more safe and secure a playerworld team would feel, in case of an emergency; in which case they would need to contact globals (if needed). The current problem is that current playerworld staff dislike globals, mostly, because they just hop from server to server and act like they run the place. Globals should learn to interact with the fellow players, not act superior to them, unless of course, you need to handle a situation that is, or is getting, out of control. In this case, you would not exactly act superior, but you would act in a more foreman sort of way. Show the players that you are to be respected and listened to by treating the players as you would like them to treat you in return.
03-25-2006, 10:03 PM
.
Linear Mode
