MetzNet
/
dfhack
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Moving the global job_types cache into the two functions that use it. 

It's mostly an artifact of a misunderstanding, anyway.
develop
Eric Wald 2014-08-03 14:57:20 -06:00
parent 1aafa206bc
commit 2db1c9d722
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
plugins/lua/stockflow.lua
Unescape Escape View File

@ -19,8 +19,6 @@ triggers = {
{name = "Never"},
}
local job_types = df.job_type
entry_ints = {
stockpile_id = 1,
order_number = 2,
@ -203,6 +201,7 @@ end
function clothing_reactions(reactions, mat_info, filter)
local resources = df.historical_entity.find(df.global.ui.civ_id).resources
local itemdefs = df.global.world.raws.itemdefs
local job_types = df.job_type
resource_reactions(reactions, job_types.MakeArmor, mat_info, resources.armor_type, itemdefs.armor, {permissible = filter})
resource_reactions(reactions, job_types.MakePants, mat_info, resources.pants_type, itemdefs.pants, {permissible = filter})
resource_reactions(reactions, job_types.MakeGloves, mat_info, resources.gloves_type, itemdefs.gloves, {permissible = filter})
@ -221,6 +220,9 @@ function collect_reactions()
-- A few task types are obsolete in newer DF versions.
local v34 = string.match(dfhack.getDFVersion(), "v0.34")
-- Caching the enumeration might not be important, but saves lookups.
local job_types = df.job_type
local materials = {
rock = {
adjective = "rock",