General errors

❌ RM01.WAD does not exist in uploads folder, skipping it

The file that was uploaded for this map slot couldn't be found. The map slot is still there and can be reuploaded by using your PIN, but the upload might have been removed temporarily if it caused other errors in the project. Contact the project owner to check.

❌ No map lumps read after map marker, possible malformed WAD. Map will not be included

❌ Unexpected lump $1 in map definition, will not include this map

RAMPART can't find a valid map in your WAD. Maps consist of a map marker with a data length of 0, followed by a set of lumps that define the map. Your map lumps might be out of order, include lumps that aren't meant to be part of the map definition, or your map marker may have a non-zero length.

You can use SLADE3 to open your WAD and inspect it. Make sure the lump order is correct, and move any lumps that aren't part of the map definition. To replace a map marker with a length above zero, create a new marker, put it at the top of your map definition and delete the old marker.

Texture errors

❌ You don't need to define dummy texture s3dummy - skipping it

Your WAD defines one of the dummy textures used by Doom-engine games to fill out the 0th texture slot. This definition won't break anything but it isn't needed.

❌ TEXTURES attempts to redefine SKIN2 patchskin2,0,0 as patch"hell8_2",64,0patch"hell8_4",0,0. Already defined in IWAD as patch"hell8_2",0,0. Skipping this definition

❌ TEXTURES attempts to redefine SKIN2 patchskin2,0,0 as patch"hell8_2",64,0patch"hell8_4",0,0. Already defined in map 32 as patch"hell8_2",0,0. Skipping this definition

Your WAD has a definition in a TEXTURES lump with a name that's already been defined, either by another map or in the project's base resources. Your definition has been ignored and this texture is likely to look different in your map from what you expected. Rename the image lump or the definition in your TEXTURES lump and change references to it in your map.

⚠ TEXTURES redefines Texture MIDFENC1 as patch"midfenc1",0,0, already defined in map 33 with an identical definition. Skipping this definition

Your WAD has a definition in a TEXTURES lump with a name that's already been defined, either by another map or in the project's base resources. Your definition is identical to the existing one, so your definition has been skipped but there should be no difference in your map.

❌ [LUMP] lumps are unsupported - convert to [TEXTURES/ANIMDEFS] with SLADE3

Your WAD includes a lump that's unsupported by RAMPART because they replace the entire table of texture definitions or animation definitions project-wide. You can use SLADE3 to open your WAD and convert the lump automatically into a TEXTURES/ANIMDEFS lump, which will work with RAMPART - you only need to include the definitions for things you've added, not definitions from the project's base resources.

❌ Found conflicts while importing TEXTURES lump

A TEXTURES lump in your WAD couldn't be imported fully because of conflicts with other maps or in the project's base data. Check the errors above this one in the log for details.

Other resource errors

❌ Lump BCRATEL1 would overwrite existing lump of that name from the project's base resources. Please rename it

❌ Lump LILDV1 would overwrite existing lump of that name from map number 38. Please rename it to make sure both maps work correctly

A data lump in your WAD has the same name as a lump in the project's base resources, or another map. This could be a patch, texture, music, and so on. If it's already in the project's resources, you don't need to include this lump. If it's custom content, rename it and update your map's references to it to ensure it works as expected.

⚠ Lump METAL_C matches same name from map number 32, but the data is identical

A data lump in your WAD has the same name as a lump in another submission, but the data in each lump is identical. This could be a patch, texture, music, and so on. Your map will still work correctly. (Lumps with the same names as those in the base resources are never allowed, even if they're identical)

❌ Found colormap-related lump C_START, but colormaps are not supported

Your WAD contains markers indicating the use of colormaps, which are not supported by RAMPART. Effects that rely on these being there won't appear correctly.

❌ Found LOCKDEFS lump but refusing it as it performs CLEARLOCKS!

Your WAD contains a LOCKDEF that uses the clearlocks command, which would erase all other previously defined locks. Reupload your WAD without using this command.

Sound errors

❌ SNDINFO tries to define the sound growl2 as TMGROWL2, but it's already defined as GROWL2

Your WAD contains a SNDINFO lump that uses a logical name for a sound that's already taken by another map or the project's base resources. Rename the logical name (the left side of the SNDINFO definition) and update any references to it.

⚠ SNDINFO defines the sound cimpsit1, which is already defined but it matches the existing definition cimpcit1

Your WAD contains a SNDINFO lump that uses a logical name for a sound that's already taken by another map or the project's base resources. Your definition is identical to the existing one, so your definition has been skipped but there should be no difference in your map.

⚠ Not importing this SNDINFO

An SNDINFO lump in your WAD has been rejected due to errors, and won't be included in the project - check above this message in the log for more information.

❌ Music lump ECHOES is too large, skipping it. Replace it or re-encode at a lower bitrate

A lump identified as music in your map is over 10MB, so it's been skipped and will not play in your map. Try re-encoding the music at a lower bitrate.

Script errors

❌ DoomedNum conflict: 14304 for pyrodemon already refers to DECORATE class: PyroDemon from map 63, rejecting it

❌ DoomedNum conflict: 8 for Snake is in a reserved range, rejecting it

Your WAD defines a DoomEd number that has already been used by a Thing or class in another map, or that lands in a range reserved for game objects. This will make an unexpected object appear on your map in place of the object with the conflicted number. Check the Build Info page for a list of conflicts and the currently assigned DoomEd numbers across the project, and use one that hasn't been taken.

If you get this error pointing to your own map, make sure you haven't defined a class's DoomEd number in both the MAPINFO and DECORATE lumps.

❌ Found ZSCRIPT script lump but refusing it as it performs replacements!

Your WAD contains a script file that tries to automatically replace classes using the replaces keyword. This is unsupported by RAMPART because the replacement would take place across all maps. Define a new DoomEd number for your class instead and place it in your map directly.

The check for this is very crude, only searching for the word "replaces" in the text of the script - if this error is unexpected, check that "replaces" doesn't appear in strings or comments either.

❌ Found DECORATE lump but got a DoomEdNum conflict, not including this script

Your DECORATE lump defines a DoomEd number that has already been used by a Thing or class in another map. This will make an unexpected object appear on your map in place of the object with the conflicted number. Check the Build Info page for a list of conflicts and the currently assigned DoomEd numbers across the project, and use one that hasn't been taken.

If you get this error pointing to your own map, make sure you haven't defined a class's DoomEd number in both the MAPINFO and DECORATE lumps.

❌ Not importing identifiers because scripts for this map were rejected

DoomEd numbers and spawn numbers defined in this WAD won't be included because the WAD contained scripts that were rejected - this protects against the project being unstartable due to a DoomEd number pointing to a class that doesn't exist. Check for why the WAD's scripts were rejected to fix this error.