Friday Night Fragfest Team - Criteria and Information About Joining the Team

Public FNF Discussion Area, does not show on Portal.

Moderator: Friday Night Fragfest Team

Locked
User avatar
Combinebobnt
Retired Staff / Community Team Member
Posts: 1893
Joined: Mon Jun 04, 2012 3:37 am
Location: Erth
Contact:

Friday Night Fragfest Team - Criteria and Information About Joining the Team

#1

Post by Combinebobnt » Sat Feb 02, 2013 5:51 am

Looking to perhaps join the team that keeps Friday Night Fragfest running? If so, read the information below.


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 in the past), with much diversity in wad choice and modifiers, if added.

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.


Criteria For Joining:

• 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.

• Have some more know-how on what makes a good wad for FNF, such as size, quality, quantity of maps, knowledge on the gamemode, etc. This will help in getting ideas for each week's fnf.

• Be active in discussion, both on IRC and on the forum in the proper discussion threads.

• Know that people will sometimes disagree with each other, and that when this happens, be able to tolerate criticism appropriately and maturely.

• Let us know if you plan to be gone for a while.

• Post things in the forums when asked.

[spoiler]Sometimes things are not optimal for fnf but they might have easy solutions. This could be some broken element of from 1996 made by John Doe, broken player spawns that ruin a dm pack, or maybe you want to improve a wad for fnf, etc.

1.) Make sure to 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.
- If the author denies you permission to make a fix, the wad will be run without the fix, unless the bug is too detrimental to gameplay.
- If you have tried every way possible to contact the author and have gotten no response throughout the week, then it is safe to make the fix (if they eventually do contact you, comply to what they say).

2.) When making a fix, *DO NOT* include the resources from the original wad! Just replace what is needed to be overridden.

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.

4.) The wad should include a text file designating all the changes that you have made in the fix.


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.


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 mod that you're making a fix for, and it shows that you mean no ill will.[/spoiler]


If you meet most these requirements or are willing to quickly learn, sign up now! Go here or PM a staff member to apply!
Last edited by Combinebobnt on Thu Sep 17, 2015 3:27 am, edited 1 time in total.

Locked