The Duty of a Modder (sticky please)
Posted: Fri Jan 18, 2008 9:20 pm
It has become apparent that some have lost sight of the goal of modding, the point of what we do here, why we do it and what we strive to accomplish. I'm going to rectify that, by setting down these guidelines. May they lead you to a true path.
The Duty of a Modder
Article I: Duty to Game
The point of modding is to make an otherwise not-so-exciting game more fun and entertaining. This can be done through making new maps, modifying an existing map, adding a new element to a map, etc. It is the modder's duty to do this, to hack into the game and change the mechanics of a map or other piece of the game in order to change fundamental aspects and make it more fun for all. The true modder does not mod only for himself, but for the whole community of the game, for all those who play it and all others who mod it. A true modder releases his or her mods to the public in order to further the entertainment value of the game. In a sense, this way we are actually partly working for the game developer. But it's more than that, we work for all who enjoy the game.
Article II: Duty to the Community
For a true modder, the only glory sought is the glory of creating a mod that everyone can enjoy. It is not the duty of that modder to gloat about his glory, however. The modder does not hurt other modders through any such boasting, nor does the modder hurt others in any sort of strike against another modder's mod, or their game. A modder is entitled to their mod, and it is theirs with which to do with as they please. The community is to enjoy the mod, or, if they do not enjoy it, not to completely destroy the morale of the other modder either. A modder's duty to the community is to produce mods, to produce tutorials, and to aid others through modding. A modder has a duty to new members of the community, and that duty is to teach them the ropes and encourage them, but not to destroy them. A modder's duty to a new member should be that of someone to a friend who is lost and needs directions. New members should be helped, not beaten. Although a more experienced modder maybe incited into flaming by a spike in their emotional state, they should consider the position they are in and do their best to amend it and keep control. A newer member should also not attack or flame an older member unless given reason to. If the older member is doing something in objection to moral and social code against the new member, the new member should be able to defend himself/herself.
Article III: Duty to Self
The modder has a duty to himself, and that is called honor. A modder should be proud to know what he knows. However, as explained in Article II, a modder should be proud to a point, but not so proud that he or she encroaches upon their colleagues. A modder's honor should be defended as the honor of the game he or she mods. If the game is threatened, the modder has an obligation to defend it. It is unacceptable for a modder to do something that directly and adversely effects their honor. A modder does not flame. Modders do not involve themselves in pointless arguments or conflicts, unless necessary. A modder does not start an argument unless they are attacked directly, and even then the argument should be kept by both sides to the minimum to allow the community freedom from spam and flames.
Article IV: The Modder's Duty...
...Is to make modding and the game fun for all.
These are guidelines, and in no way does the creator of these guidelines state that a person absolutely must follow these guidelines. They are only here as a reminder to keep the peace, but are in no way forced upon a person.
The 002 clause:
It is up to the creator of a mod as to whether that mod is released or not. However, if a mod be not released, viable reasoning should be given as to why. This pertains only to mods that have been announced previously. For example: Little Jimmy talks a lot about his brand new mod which has flying scorpions, cows, a pickup truck, and a duel-wielding flamethrower laser beam. Then Little Jimmy decides not to release his mod. He does not say anything more on the subject.
Little Jimmy, therefore, is stupid for not saying, "Oh, I couldn't release my mod because the cows and the electric dishwasher lagged up the game."
If you've announced a mod, and it is finished, release it. If you don't want to or are unable to, say why.
If you have anything to add or change in this, post here.
The Duty of a Modder
Article I: Duty to Game
The point of modding is to make an otherwise not-so-exciting game more fun and entertaining. This can be done through making new maps, modifying an existing map, adding a new element to a map, etc. It is the modder's duty to do this, to hack into the game and change the mechanics of a map or other piece of the game in order to change fundamental aspects and make it more fun for all. The true modder does not mod only for himself, but for the whole community of the game, for all those who play it and all others who mod it. A true modder releases his or her mods to the public in order to further the entertainment value of the game. In a sense, this way we are actually partly working for the game developer. But it's more than that, we work for all who enjoy the game.
Article II: Duty to the Community
For a true modder, the only glory sought is the glory of creating a mod that everyone can enjoy. It is not the duty of that modder to gloat about his glory, however. The modder does not hurt other modders through any such boasting, nor does the modder hurt others in any sort of strike against another modder's mod, or their game. A modder is entitled to their mod, and it is theirs with which to do with as they please. The community is to enjoy the mod, or, if they do not enjoy it, not to completely destroy the morale of the other modder either. A modder's duty to the community is to produce mods, to produce tutorials, and to aid others through modding. A modder has a duty to new members of the community, and that duty is to teach them the ropes and encourage them, but not to destroy them. A modder's duty to a new member should be that of someone to a friend who is lost and needs directions. New members should be helped, not beaten. Although a more experienced modder maybe incited into flaming by a spike in their emotional state, they should consider the position they are in and do their best to amend it and keep control. A newer member should also not attack or flame an older member unless given reason to. If the older member is doing something in objection to moral and social code against the new member, the new member should be able to defend himself/herself.
Article III: Duty to Self
The modder has a duty to himself, and that is called honor. A modder should be proud to know what he knows. However, as explained in Article II, a modder should be proud to a point, but not so proud that he or she encroaches upon their colleagues. A modder's honor should be defended as the honor of the game he or she mods. If the game is threatened, the modder has an obligation to defend it. It is unacceptable for a modder to do something that directly and adversely effects their honor. A modder does not flame. Modders do not involve themselves in pointless arguments or conflicts, unless necessary. A modder does not start an argument unless they are attacked directly, and even then the argument should be kept by both sides to the minimum to allow the community freedom from spam and flames.
Article IV: The Modder's Duty...
...Is to make modding and the game fun for all.
These are guidelines, and in no way does the creator of these guidelines state that a person absolutely must follow these guidelines. They are only here as a reminder to keep the peace, but are in no way forced upon a person.
The 002 clause:
Releasing ModsTHOU SHALT SHARE YOUR MOD OR MEET A TERRIBLE FATE! MWAHAHAHAHAHAHA! SO SHARE OR DIE OR YOU WILL HAVE TO CLEAN THE GUNK BETWEEN MY TOES, CLEAN THE GUTTERS, AND BOW BEFORE ME.
It is up to the creator of a mod as to whether that mod is released or not. However, if a mod be not released, viable reasoning should be given as to why. This pertains only to mods that have been announced previously. For example: Little Jimmy talks a lot about his brand new mod which has flying scorpions, cows, a pickup truck, and a duel-wielding flamethrower laser beam. Then Little Jimmy decides not to release his mod. He does not say anything more on the subject.
Little Jimmy, therefore, is stupid for not saying, "Oh, I couldn't release my mod because the cows and the electric dishwasher lagged up the game."
If you've announced a mod, and it is finished, release it. If you don't want to or are unable to, say why.
If you have anything to add or change in this, post here.
* he/she must always remind themselves that is only a little emotion gotten out of control, and work to correct it"