Utility:DFusion

DFusion info page

Thread for discussions: Thread

Usage

Dfusion plugin offers two DFhack commands: 'dfusion' and 'lua'.

lua

Runs an interactive lua console. For more on lua commands see Lua reference manual or google "lua". Also this command could be ran with filepath as an argument. Then it runs that file as a lua script file. E.g. lua dfusion/temp.lua runs a file <your df path>/dfusion/temp.lua.

dfusion

First this command runs all plugins' init.lua part then show a menu. Type number to run specified plugin.

Exported functions and objects

Objects differ from functions by calling convention ( using : instead of '.'). Also most of the functions are grouped.

Dfhack/DF interface

Console.

name	description	example
print	prints a message to dfhack console	Console.print("Hello world!")
printerr	prints an error message to dfhack console	Console.printerr("Error world!")
clear	clears console	Console.clear()
color	sets text color	Console.color(2)
reset_color	resets text color to defaults	Console.reset_color()
cursor	sets if the cursor should be visible	Console.cursor(true)
msleep	waits for x milliseconds	Console.msleep(200)
get_columns	returns number of columns in the console	Console.get_columns()
get_rows	returns number of rows in the console	Console.get_rows()
lineedit	asks user for input	Console.lineedit("Type in your name:")

From scripts

These commands are exported from script files. Most of them are in "common.lua" file.

Patterns

See patterns.lua and itempatters.lua. This will be refactored in the future to use Memory.xml (thus be version and Os independent).

How to

This section explains in detail some of more complex things that could be done with dfusion.

OnFunction

There are two parts to OnFunction: adding new triggers and using already existing triggers. To add new trigger you must know exact location of function call (and what it does) also it would help a lot if you know what registers correspond to what data. Usually this could be worked out by analysing call stack after setting a data breakpoint (watch in GDB) and then guessing what does what. Using already existing triggers is way simpler. Adding a callback (a function to be called when a trigger is encountered) is done by onfunction.SetCallback(name,function). For possible names see locations.lua (at the time of writing there is "Move" and "Die" both in Linux and Windows). Possible use of it:

function DeathMsg(values)
	local name
	name=engine.peek(values[onfunction.hints["Die"].creature],ptt_dfstring)
	print(name:getval().." died")
end
onfunction.SetCallback("Die",DeathMsg)

In this example we bind 'DeathMsg' function to "Die" trigger. Values argument has all the registers and a return address. So we lookup from witch register do we need to read the creature pointer ( values[onfunction.hints["Die"].creature ) and read a string just from the beginning (usually the creature starts with his name). Then print it to the console.

Note: there can be only one callback per trigger. Also if you know any more trigger locations please share :)

Tips and Tricks

• To use dfusion's functionality in lua first run dfusion (exit it with 'q') and then use run lua