Advertisement
Combinebobnt

fnf joining guidelines 2/1/2013 v1

Feb 1st, 2013
93
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.32 KB | None | 0 0
  1. Looking to perhaps join the team that keeps Friday Night Fragfest running? If so, read the information below.
  2.  
  3. Friday Night Fragfest (FNF for short) is a weekly event that hosts various Player Vs Player gamemodes every friday (although we have done a few cooperative-esque ones throughout history), with much diversity in wad choice and modifiers, if added.
  4.  
  5. In order to keep this event operational, the staff has to accomplish various tasks to make sure everything runs smoothly. This includes testing each wad for potential bugs, getting patches ready to fix the bugs that may potentially arise during testing, determining the proper server settings (dmflags, maplist, etc) for the event, and contributing to discussion on what to host and various topics that may arise, all on a weekly basis.
  6.  
  7. Criteria For Joining:
  8.  
  9. * Show up the actual FNF events (work and school schedules not withstanding), even if its just a few maps. A good showing at the beginning can, and will, entice more people to come play in the events.
  10.  
  11. * Have some know-how when it comes to modding (decorate, ACS, mapping). This isn't mandatory, but it is a big plus - especially for special FNF events or wads or mods that might need a patch. THIS INCLUDES KNOWING AND UNDERSTANDING THE PROPER RULES AND GUIDELINES TO MAKING A FIXWAD. READ THE SPOILER BELOW FOR MORE INFORMATION.
  12.  
  13. [spoiler="Proper Way to Make A Fix"]
  14. 1.) Make sure to try get permission from the author(s) of the wad if you are making a fix, ESPECIALLY if it is something more than a minor/trivial change.
  15.  
  16. 2.) When making a fix, *DO NOT* include the resources from the original wad! Just replace what is needed to be overridden.
  17.  
  18. 3.) You must name the file in a way that specifically differentiates that this wad is a fix wad. For the purposes of FNF, the original filename, appended with "-fnf" or "-fnffix", or related, will suffice.
  19.  
  20. 4.) The wad should include a text file designating all the changes that you have made in the fix.
  21.  
  22.  
  23. When writing a PM notification to the author(s), you should include your intentions to do the above things (make a text file, rename the file to something different than the original wad, not include the resources of the original wad, etc.), that way the author(s) know your good intentions and don't get the wrong impression about your fix.
  24.  
  25.  
  26. Generally, no authors have ever said no to making a fix in the past, but this is very good practice to notify the authors of your intentions. After all, these are the original creators of the wad and/or mod that you're making a fix for, and it shows that you mean no ill will.
  27. [/spoiler]
  28.  
  29. * Participate in discussions, both on IRC and on the forum in the proper discussion threads.
  30.  
  31. * Help think of ideas for each week's event. These should be ideas that can be easily backed up with reasons why it would be a good idea for FNF.
  32.  
  33. * Know that people will sometimes disagree with eachother, and that when this happens, be able to tolerate criticism appropriately and maturely.
  34.  
  35. * Let us know if you plan to be gone for a while.
  36.  
  37. * Take turns posting the weekly event threads and discussion threads, as well as contributing in the discussion threads.
  38.  
  39. If you meet most (again, ability to mod/map isn't mandatory) or all of these requirements, sign up now! Go [url="here"]http://zandronum.com/forum/usercp.php?action=usergroups[/url] to apply!
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement