Skip to main content
Era accuracy modules are Lua and SQL modules that revert game mechanics, drop tables, or job abilities to how they behaved during a specific expansion. Rather than mixing these reverts in with general custom modules, the repository provides dedicated folders named after each expansion. This makes it easy to understand which changes belong to which era and to selectively enable or disable entire expansions’ worth of reverts.

Expansion folders

Placing a module in the correct folder is a convention, not a technical requirement. The server loads modules based on init.txt regardless of which folder they are in. The folder names communicate intent and help you and others reason about what the module is doing.
The rule of thumb: if a change occurred in December 2010, place the module that reverts it in the abyssea/ folder, since Abyssea is the expansion that introduced the change.

Existing era accuracy modules

cop/

toau/

wotg/

abyssea/

soa/

rov/

Loading era accuracy modules

Add the relevant folders to modules/init.txt. You can load an entire era at once or individual files:
init.txt

Writing your own era accuracy module

The process is the same as writing any Lua or SQL module. The only convention is the folder placement.

Example: reverting a pDIF cap (Lua)

This is based directly on modules/wotg/lua/pdif_caps_revert.lua. It sets pDIF caps back to { 2, 2 } across all weapon types, which was the value before the 2007-08-27 ToAU update:
modules/wotg/lua/pdif_caps_revert.lua

Example: reverting a status effect duration (Lua)

This pattern overrides an ability’s use function to restore an older duration. The source comment is important — it records which version update introduced the change.

Example: removing a drop from a specific era (SQL)

Place the file in the folder corresponding to when the item was added — reverting it means removing what was introduced.
modules/toau/sql/mob_droplist_removal.sql

Tips

  • Always include a source comment linking to the version update or patch notes that document the original change. This makes the module self-documenting and verifiable.
  • Use the expansion date ranges in the table above to decide which folder a module belongs in — not the date you wrote the module.
  • If you are not sure which expansion introduced a change, abyssea/ is a reasonable default for changes from 2010–2013, which is the most heavily modified era.
  • Era accuracy modules are disabled by default. They only take effect when you add them to init.txt.