Go to file
an 11b4e635e5 whoops 2019-08-14 05:28:36 -04:00
api organize into folders (why didn't i think of this sooner?) 2019-08-14 05:27:32 -04:00
glossary organize into folders (why didn't i think of this sooner?) 2019-08-14 05:27:32 -04:00
language organize into folders (why didn't i think of this sooner?) 2019-08-14 05:27:32 -04:00
tools organize into folders (why didn't i think of this sooner?) 2019-08-14 05:27:32 -04:00
trees update for 4.1.0-4.2.0 2019-08-12 22:19:01 -04:00
.gitignore Move to a full repository 2018-11-24 01:50:55 -05:00
LICENSE.txt better license wording 2019-01-08 16:44:31 -05:00
README.md change header styles 2019-04-02 11:28:16 -04:00
api.md whoops 2019-08-14 05:28:36 -04:00
entry.md standardize documentation code style 2019-04-05 19:34:55 -04:00
glossary.md organize into folders (why didn't i think of this sooner?) 2019-08-14 05:27:32 -04:00
language.md organize into folders (why didn't i think of this sooner?) 2019-08-14 05:27:32 -04:00

README.md

ZScriptDoc

This is documentation for the ZScript language. CC0 public domain. See LICENSE for more information.

  • API - for information on the interfaces provided by GZDoom. This is itself a map of all of the API files.
  • Entry Points - for information on the ways you can tell the engine to add new things.
  • Glossary - for miscallaneous information and concepts you should learn. This is itself a map of all of the glossary files.
  • Language - for information on the language itself.

If you're wondering where to start, try starting with the language documentation and working your way from there. Also recommended is looking at existing mods using ZScript and modifying them. Try experimenting with features if you don't know what they do.