Editing ACS scripting
From Eternity Wiki
Jump to navigationJump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 11: | Line 11: | ||
This information does not apply for UDMF or Hexen format maps. | This information does not apply for UDMF or Hexen format maps. | ||
ACS scripts can be loaded with Doom-format maps through the help of [[MapInfo|EMAPINFO]]. The MapInfo entry for the map needs a specifier for | ACS scripts can be loaded with Doom-format maps through the help of [[MapInfo|EMAPINFO]] and [[ExtraData]]. The MapInfo entry for the map needs at least a specifier for its ExtraData lump and compiled ACS lump (setting the '''extradata''' and '''acsscript''' entries). | ||
The script can be written in a text editor and compiled using the '''acc''' tool (see https://devbuilds.drdteam.org/ACC/). After obtaining the behavior lump (usually with the .o extension), import it in a wad and place it between lumps '''A_START''' and '''A_END'''. The '''acsscript''' entry from EMAPINFO should then reference this compiled lump. | The script can be written in a text editor and compiled using the '''acc''' tool (see https://devbuilds.drdteam.org/ACC/). After obtaining the behavior lump (usually with the .o extension), import it in a wad and place it between lumps '''A_START''' and '''A_END'''. The '''acsscript''' entry from EMAPINFO should then reference this compiled lump. | ||
Line 35: | Line 35: | ||
ACS scripts can be tested from the [[console]] by using the '''puke''' command. | ACS scripts can be tested from the [[console]] by using the '''puke''' command. | ||
== ACS details == | == ACS details == | ||
*[[ACS spawn IDs]] | *[[ACS spawn IDs]] | ||
*[[ACS built-in functions]] | *[[ACS built-in functions]] | ||
*[[ACS directives]] | *[[ACS directives]] | ||
[[Category:Editing reference]] | [[Category:Editing reference]] |