Feh gamepedia manual#
Feh gamepedia plus#

This means example that whenever new story or paralogue maps are released, the wiki can display stats for Chain Challenges even before they are available in-game.

Feh gamepedia manual#

As can be seen in the source of this map, the unit stats for these game modes are no longer specified instead, as a result of supplementing the SQL database with extra fields, like skill promotion conditions and the internal IDs mentioned above, the Lua module is now capable of deriving those stats on the server, saving a lot of manual input. (Some new map articles already use this new format.) This is what the new table looks like compared to the old version, it runs approximately twice as fast, features a new AI settings table that can be generated from JSON dumps, displays the cooldown counts of all Special skills, and most importantly, supports unit promotion in derived game modes. The Lua-based replacement of the unit data table is finished, and it will start to roll out to map articles starting from August 3rd. (In reality, enemies are distinguished using a separate property list field, whereas the internal IDs are used for joins with other similarly merged tables storing other unit data.) By merging the two tables into one, both variants can be stored together and unambiguously identified using their internal IDs, which is important for derived game modes such as Chain Challenges and Squad Assaults where the different growth rates matter. However, when Book II finished, several of the units were made available in both playable and enemy-only variants which have slightly different properties, such as sort order and growth rates, causing a lot of trouble for maintainers templates and Lua modules had always been written to assume that a given name represents a Hero, so they query the Heroes table first and fall back to the enemies table only if a row cannot be found.

Feh gamepedia plus#

In the beginning, there was a table for Heroes plus the enemy bosses (Book I Bruno and Veronica), and a different, structurally incompatible table for generic enemy units. The major motivation is to merge those two types of units into the same SQL tables as much as possible, which simplifies certain SQL queries and permits further optimization. Internal IDs for Heroes (that start with PID_) and enemy-only units (that start with EID_) have been added to the database.