The Open Level Project

These are the guidelines again:

---------------------------------------------------------

WHAT IT IS ALL ABOUT:

1. The Open Level is a level which is made by different people. Everyone who participates makes edits to the level and adds to it, this includes:

• Adding rooms
• Adding scripts
• Editing rooms or room names if necessary
• Editing scripts if necessary

'if necessary' means only if there's a mistake, or if something can be done better/extended, like making challenges which are really too difficult/impossible a bit easier

2. Please put all changes you make in the changelog. It's a script called --CHANGELOG--, which we treat like a text document. Use the format that is used already, so leave one line empty before your entry, then put vXX - YY (with XX being the version number, and YY your username(s)). Use stars as bullets for list items. Be specific, but don't be too specific. Look at other entries to see how specific you should be. Please don't forget to update the changelog with your changes.

3. All flags which are used are listed in the script called --FLAGS--. Flags 90 - 99 can always be used for temporary things which are only needed in a few adjacent rooms, as long as they are off when you're done. When you use a flag (not 90-99), put it in the --FLAGS-- list with a small description or script name.

4. The level contains several debug terminals, to get direct access to a level or to unlock all teleporters to make playtesting specific parts of the level a lot easier. Don't remove these terminals before the level is about to be released, and everyone agrees. The scripts themselves should maybe be untouched, as they may be useful in the future.

5. Most communications about the Open Level are in the drawing room (room 'vvvvvv'). New versions are also released there to the participants. Sometimes there are also people in the drawing room who don't participate in the Open Level Project, so if that's the case, and you want to release your new version, send a PM with the link to all participants seperately (right click a name in the user list and select 'PM/Whisper', and put the version number and the link after the /pm name .

6. Also, we recently made a website with a small forum for the Open Level Project! The website is tolp.webs.com. If you register, you'll be changed to a member who can also access the OL board(s) in less than 24 hours. (can be much less, it depends on the time. It may also be a few minutes, for example.)

7. If you want to make a new version, wait until it's possible (between versions/when someone releases one is the best time) and tell participants on the tolp forum/in the drawing room, if they're not AFK. Tell them which version number you're going to work on, like for example "I'm going to make v23" so other people can tell you if you are working on an old version (when for example you start editing v22 when the most recent version is v25) or if somebody else is already working on it. If you know that somebody is already working on a new version, don't hesitate to say that you want to work on the version which comes after that one. If you do not tell other participants, you may have missed more recent versions and you may be making a new version from an old version, or you may make a new version while someone else is also doing that at the same time.

8. A good place to check what the latest version is, or to download any versions you may have missed, is [site]. If you have been away for some time, always check that site to see what the latest version is. However, [site] is not guaranteed to be always 100% up to date, so also check with active users in the drawing room if [site] is not up to date. You can also go to tolp.webs.com and check it there. (Also not guaranteed to be always 100% up to date)

DO:

 Use internal scripting. It's not something you're really required to use, but it is recommended. If you don't know how it works, and you want to make something which is not possible in simplified scripting, ask FIQ or Dav999. They're very good with internal scripting. You could also check out a tutorial of the basics here, and most commands can be found in the largest thread on the forum. 

 Make things nice and polished.

 Try to make original stuff, things no-one else has tried before. This includes not stealing design from other levels without permission.

 Follow the guidelines on 'How to get a level featured'. Although Terry hasn't featured any levels in a while, but they're still good guidelines on how to make a good level.

 Make things rather too easy than too hard. Making it too hard is WAY easier than making things balanced/too easy, and stuff you see as too easy might as well be just right for most other people.

DON'T:

 Remove work of others if not necessary.

 Start making a new version without other people knowing or without knowing for sure you're working on the most recent version. If there are no other participants in the drawing room, or if everyone is AFK (also after sending a chat message), and you're sure nobody is working on it, you can work on a new version without telling others, but at least be sure that you're working on the most recent one.

 Use direct mode. Not everyone has 2.1, and your direct mode work will get messed up if someone with 2.0 edits it. We agreed on using direct mode only in the final states of the level.

 Do things which do not work on both 2.0 and 2.1. This includes colored text boxes outside of internal scripting with say(n,color) or say/reply with more than 5 lines in 2.1, or the say(6) method of exploiting internal scripting in 2.0.

 Use bad level design, like floating spikes/checkpoints, or single tiles.

 Exploit bugs if it makes the level look bad (to exempt creative use of wallglitch -- see Dimension of Secrets -- or internal scripting, etc)

 Ruin it for others. So don't end the level unless everyone agrees, and don't make it less appealing for others to work on the level.

 Use flags without looking in the --FLAGS-- list if the flags have been used already, and don't use flags without putting it in the --FLAGS-- list. This does not apply to the temporary flags 90-99.

 Edit changelog entries of others or things in the --FLAGS-- list without a reason.

 Take too long with finishing your version. Please make the version withing 3 hours after you say you're working on the new version, otherwise other people are allowed to start working on it instead.

 Be afraid that you're doing something wrong, and that your version is going to be disliked. If you're afraid that you're doing something wrong, you can ask us for help. Also, it's not possible to permanently ruin it for others, all the versions are archived by several people, so we can always go back if necessary. 

Guidelines version 3, 23-02-2013 (02/23/2013)

---------------------------------------------------------