You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I seem to have found a new global, it's a one byte value immediately following ui_workshop_in_add and specifies the type of building being linked to a lever/pressure plate. Interesting thing is that it takes not values from building_type, but character code of a key you use to initiate linkage, e.g. b for bridge, ... , T for track stop. It's set to 0xff when not in the linkage mode.
EDIT: Also it's set to t when choosing a mechanism for the target, and to l when choosing a mechanism for the lever/pressure plate (with ui_building_assign_items holding the list of choices).
Since globals need to be updated manually for new DF versions, what's the procedure of adding a new one?
The text was updated successfully, but these errors were encountered:
This seems like it should be fairly easy to locate with find-offsets, once a scan is implemented for it.
(@quietust says he identified this in 0.23, by the way, so it could be using character codes because of its age.)
I seem to have found a new global, it's a one byte value immediately following
ui_workshop_in_add
and specifies the type of building being linked to a lever/pressure plate. Interesting thing is that it takes not values frombuilding_type
, but character code of a key you use to initiate linkage, e.g.b
for bridge, ... ,T
for track stop. It's set to0xff
when not in the linkage mode.EDIT: Also it's set to
t
when choosing a mechanism for the target, and tol
when choosing a mechanism for the lever/pressure plate (withui_building_assign_items
holding the list of choices).Since globals need to be updated manually for new DF versions, what's the procedure of adding a new one?
The text was updated successfully, but these errors were encountered: