Odamex supports three MAPINFO format types listed below.

Hexen-style MAPINFO is merely the foundation of ZDoom-style MAPINFO (old format). All of the Hexen definitions are supported by ZDoom-style MAPINFO. More information is available in the Doom Wiki article.

The original ZDoom MAPINFO format (also referred to as "old format") was a ZDoom extension of the definitions possible in Hexen MAPINFO. The full list of definitions available with ZDoom-style MAPINFO (old format) is available on the ZDoom Wiki.

Note that while Odamex does support some features of new format MAPINFO, aka ZMAPINFO, which was introduced in ZDoom 2.3.0, it ignores lumps named "ZMAPINFO" due to internal conflicts. See this PR (pull request) for details.

It's important to note that Odamex doesn't yet support all of the MAPINFO (old format) definitions. Here will be listed the ones not supported with the hopes they will be marked off the list in future Odamex updates.

name <nice name>
lookup <keyword>

adddefaultmap
gamedefaults
cdid <CD identification number>
exitpic <picname>
• NOTE: exitpic (and enterpic) are supported. However, intermission scripts (defined by enterpic $LUMPNAME) aren't.

enterpic <picname>

• NOTE: See above.

intermusic <musicname>
bordertexture <picname>
specialaction <monstertype>, <action special>, <arg1>, ...
specialaction_killmonsters
lightning
vertwallshade <amount>
horizwallshade <amount>
clipmidtextures
forcenoskystretch
skystretch
autosquences
strictmonsteractivation
laxmonsteractivation
missileshootersactivateimpactlines
missilesactivateimpactlines
fallingdamage
monsterfallingdamage
oldfallingdamage
strifefallingdamage
forcefallingdamage
nofallingdamage
teamdamage <amount>
airsupply <amount>
filterstarts
allowrespawn
teamplayon
teamplayoff
noinventorybar
keepfullinventory
infiniteflightpowerup
allowcrouch
normalinfighting
totalinfighting
f1 <image>
checkswitchrange
nocheckswitchrange
translator <lumpname>
unfreezesingleplayerconversations
Compatibility options

hub

dropammofactor <decimal number>
name <name>
playerclassname <class> <name>
textcolor <color>

UMAPINFO is a standard map list format supported by several source ports. Odamex has supported it since version 10.0.0. More information, including a list of supported source ports, is in the Doom Wiki article.

When making new episodes in UMAPINFO, there is no separate Episode Definition, unlike MAPINFO. Rather, new episodes are defined by attaching them to the first map of an episode with the episode definition.

The clearepisodes MAPINFO definition is performed in UMAPINFO by first defining an episode as episode = clear, followed by another episode definition listing the actual desired episode properties. Here's an example that creates a new episode in the E1M# maps titled "Rescue on Bazoik". Subsequent maps (e.g., E1M2, E1M3, etc.) should not have episode definitions unless they are the first levels of other new episodes.

map E1M1
{
	levelname = "Landing Zone"
	levelpic = "WILV00"
	nextsecret = "E1M9"
	skytexture = "CQSKY1"
	partime = 110
	episode = clear
	episode = "M_EPI1", "Rescue on Bazoik", "r"
}

SPECIAL NOTE: The key MAPINFO property is defined in UMAPINFO by a single character given in quotation marks after the title. However, it is important to note that this character must be lower case or it will not work. This is in case you're trying to copy definitions from SIGIL or SIGIL II. The UMAPINFO lumps made in those two mods are buggy.

NOTE: If you include both a MAPINFO and UMAPINFO lump, Odamex will only load UMAPINFO regardless of the lump order.

The disadvantage of using UMAPINFO while modding for Odamex is that you'll be missing out on a number of ZDoom features present in its original MAPINFO format. The advantage is that you can make a mod compatible with a wider array of source ports.