Eventing: A legitimate specialty?
12-28-2008, 07:40 AM
Basically, it comes down to a matter of terminology. The term "eventer" has been diluted by the new game makers who want someone else to do the simple stuff for them. It's been suggested that titles like designer or system designer would be a better description, but I really don't think so because it's not specifying if you're using scripts or events. A person who makes a script-based battle system is a scripter, so why isn't someone who makes an event-based battle system an eventer?
For the qualification aspect, scripting and eventing can be seen as pretty equal. Scripting requires prerequisite knowledge and events are much more limiting because you can't change how they work. Scripting uses Ruby, eventing uses scripts.
Those are basically the arguments that I made for considering "eventer" a specialty. Some people would disagree with me on what I've said above, but no one really disputes that making your own battle system is a complicated thing to do, whether you think it's for design reasons or putting it together.
For the qualification aspect, scripting and eventing can be seen as pretty equal. Scripting requires prerequisite knowledge and events are much more limiting because you can't change how they work. Scripting uses Ruby, eventing uses scripts.
Those are basically the arguments that I made for considering "eventer" a specialty. Some people would disagree with me on what I've said above, but no one really disputes that making your own battle system is a complicated thing to do, whether you think it's for design reasons or putting it together.