How RAMP works

RAMP is a project built by everyone who chooses to contribute! Everyone's submitted WADs will be compiled into a GZDoom game based around a hub level, and the player will be able to more or less choose to complete the maps in any order. In each map, the player will start with only the pistol, so don't rely on the player carrying weapons or ammunition from previous maps.

Mapping guidelines

• Maps can be of any theme or approach. I recommend taking a couple of weeks for a map and uploading it some time in mid-June. The last date for alterations is the end of June 30th, after which I'll help with any bugfixing caused by merging the project together.
• You're welcome to try more than one idea, but I need to limit it to three map submissions per person. If you'd like to do more, recruit a friend and help them make theirs!
• I recommend that maps take up to ten minutes to complete, but there is no strict size restriction. Remember that a player might get fatigued by a single map in a collection that's too long, and due to the high number of submissions I'll only be able to provide about ten minutes of feedback per map.
• While all comers are truly welcome to the project, I've got to reserve the right to kick maps that are excessively broken or unplayable on purpose, or people who don't treat other community members with respect. This isn't a quality control rule and maps won't be rejected for mistakes - we all make them!
• Please make something original for this, instead of something that's already been released elsewhere.
• However, after the project, I have no ownership of your map - I actively encourage you to take what you've made, build on it and release it independently as part of something bigger, like a whole custom episode!

Resources

RAMP will run on DOOM2.WAD in GZDoom. Textures from the resource packs 32in24 and OTEX_1.1.WAD are included in the project, so you don't need to do anything special if you want to use those - you can download a resource pack containing both of them in the starter pack (or here for just the resources PK3).

Custom content is also supported, as long as you don't overwrite any of the default DOOM2 lumps or make changes that affect the entire game (such as DEHACKED). If you'd like to include anything, see the Custom Content section below.

How to submit

Use the Upload page on this site! Submit a WAD containing a single map of any Doom format, and the site backend will incorporate the map into the complete project so far. You can download a snapshot version after uploading to compile the project including your latest changes - check the console icon next to your map in the Download page to see a report on what the compiler included.

You can submit changes to your map by going to the upload page and using the PIN that you'll be given the first time you upload. If you've lost it, the project owner can retrieve it.

Details on custom content

If you want to include custom Things (game objects), be aware of the DoomEd numbers you're using - each unique type of object in a Doom WAD needs to have a unique number, and this list is global across all maps. Check the Build Info page to have a look at the current list of DoomEd numbers that are occupied, and choose a range of numbers that won't interfere with others. The recommended formula is to use [(your map number) * 100] as a starting point, but this won't be possible for all maps due to the numbers of existing Doom objects.

When you upload your WAD through this site, the uploader will recognize and include:

• The first present Doom or UDMF map, including any ACS scripts and dialogue attached to it
• ZSCRIPT and DECORATE lumps (they will be rejected if they use the replaces keyword)
• The SNDINFO lump(s) and any sound lumps named in them
• Patches between P_START and P_END markers (alternatively PP_START or PPSTART, PP_END or PPEND)
• Textures between TX_START and TX_END markers
• Sprites between S_START and S_END markers (alternatively SS_START, SS_END)
• Flats between F_START and F_END markers (alternatively FF_START, FF_END)
• These lumps will be imported directly, with an extension matching your map's number:
  • TEXTURES to define textures made from patches
  • GLDEFS
  • ANIMDEFS
  • LOCKDEFS unless the clearlocks command is used (make sure you don't overwrite any previously defined locks)
  • SNDSEQ (make sure your defined sound sequence numbers don't collide with other maps)
  • README
  • MANUAL
• Music:
  • Name a lump D_RUNNIN to make it your map's background music.
  • If you need multiple music files, include them between MS_START and MS_END tags and refer to them directly in your MAPINFO or scripts.
• Certain allowed properties in MAPINFO:
  • activateowndeathspecials
  • aircontrol
  • airsupply
  • baronspecial
  • checkswitchrange
  • cyberdemonspecial
  • doublesky
  • evenlighting
  • eventhandlers
  • F1
  • gravity
  • lightblendmode
  • lightmode
  • lightning
  • map07special
  • music
  • sky1
  • sky2
  • spidermastermindspecial
  • specialaction_exitlevel
  • specialaction_opendoor
  • specialaction_lowerfloor
  • specialaction_killmonsters
  • useplayerstartz

If you need more custom content, contact DavidN on the Discord to get it into the project.