Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Hesperid]

1 based indexing is an obvious example of massive brain damage... Hmmm... Maybe I should brush up my C skills some and write a language that takes all the best parts of Lua, but use C-like syntax, 0 based indexing, etc. The problem is, I already have too many projects.

I think we've all had that idea once or twice whenever we stumble on Lua's many oddities. Lua's strengths are very impressive, and the clumsy and verbose syntax is the price you must pay for it. The real problem in writing your own Lualike language, because it applies even to people that don't have too many projects, is this: see you in 20 years when your single-developer language is mature and doesn't randomly glitch out/segfault. Oh you're finished? Well Lua's dead and now we're all using MontyPython, because all the VR devices have an integrated bytecode VM for it. There's your next homemade language dupe project.

[heydude6]

Just a quick question about the exterminate him command, but is there a way to make it select a target by receiving map coordinates rather than having to move my cursor over it? I kind of want to create a syndrome that automatically exterminates a unit after it gets infected with it and I can't have players willingly initiating the process.

[Putnam]

Exterminate just removes all blood from the creature's system and makes them disappear in two ticks. Make a CE_BLEEDING syndrome with extremely high severity on all parts, that should be enough.

[Williham]

1 based indexing is an obvious example of massive brain damage... Hmmm... Maybe I should brush up my C skills some and write a language that takes all the best parts of Lua, but use C-like syntax, 0 based indexing, etc. The problem is, I already have too many projects.

I think we've all had that idea once or twice whenever we stumble on Lua's many oddities. Lua's strengths are very impressive, and the clumsy and verbose syntax is the price you must pay for it. The real problem in writing your own Lualike language, because it applies even to people that don't have too many projects, is this: see you in 20 years when your single-developer language is mature and doesn't randomly glitch out/segfault. Oh you're finished? Well Lua's dead and now we're all using MontyPython, because all the VR devices have an integrated bytecode VM for it. There's your next homemade language dupe project.

Also, the language already exists:

They call it Squrrel.

[expwnent]

That looks great but in terms of how much good we can do for the project per hour of free time it's probably not worth it.

[gchristopher]

I'm investigating writing a script that calculates a artificial running "score" of a game as it progresses. I'd like it to display periodic updates on the current score, and persist a cumulative total for an in-game year across save/loads. So far I've got:

- I can start a script from onMapLoad*.init and do any needed cleanup from onMapUnload*.init. (That's the safest place to put something that should only run in Fortress mode?)
- I can use repeat to schedule a command to examine the site map/logs and calculate/report a score daily.

So far, so good. Is there any convenient way to save a value (like "current total score") that will persist across save/loads of a game?

I imagine that writing a value to an arbitrary file would be a gigantic security hole, but maybe it's possible anyway? I see there's a stockpiles plugin that (I think) delivers a .dll to deliver the file access functionality. I'd rather not get that fancy.

Failing that, I guess there's a lot of places in a saved game where you could stash a value somewhere it wouldn't hurt a running game. Maybe in some stat for a historical figure, or somewhere in the game raws as a non []-enclosed value that would be interpreted as a comment?

Does anyone have any advice on how to best save arbitrary data across game saves so the script can retrieve it on the next onMapLoad?

[lethosor]

onMapLoad*.init will run whenever any map is loaded, including in adventure mode. If you want your script to only work in fortress mode, you have to handle that in your script (e.g. check "dfhack.world.isFortressMode()").

The stockpiles plugin is self-contained. It doesn't distribute any other libraries. Perhaps you're thinking of protobuf, but that's included in DFHack, and DFHack uses it for most remote communication. Lua has decent enough file support for the kind of data you want to save, and there's also a Lua JSON library if you want that.

There's also the persistent storage API. I'm not too familiar with it, but it should be documented in the Lua API docs: http://dfhack.readthedocs.io/en/latest/docs/Lua%20API.html

[Putnam]

I would personally just use the JSON API and use the site index as a key. There are some minor problems with saving (autosaves won't work), but that can be handled by just storing the scores by dates, saving the file whenever they're stored, then deleting any that happen after the current date. Make sure to store any keys as strings rather than integers, storing as integers will make the JSON API store it as an array even where that makes no sense (e.g. you're tracking units 2703 and 2704, so your JSON table has 2702 empty indices listed out before 2703).

[TheKaspa]

Is there a pre-alpha for 43.05?

[Dirst]

Is there a pre-alpha for 43.05?

We've tried doubling the volunteers' pay ($0x2=$0), but it turns out that no one is slacking and it's just taking a long time.

[lethosor]

I've also been busier than normal and haven't had as much time to work on DFHack as I would've liked.

Part of the issue is that some offsets still aren't located (partly because there are 6 builds now instead of 3, although the real issue is that finding 64-bit offsets is harder since we have to update some tools we were using). That would definitely block a stable release, but I guess it's not too bad for an alpha release. We've released early builds without some offsets before, anyway.

[Quietust]

finding 64-bit offsets is harder since we have to update some tools we were using

In some cases, that isn't even possible - for example, I've been using IDA demo/free versions on Windows for 32-bit DF, but the only versions of IDA that support 64-bit binaries cost over $1000 for a single license, and most other tools don't even come anywhere close in terms of functionality and usability.

[SalmonGod]

This is super sad, and I would donate money to the cause if I could.  It's very difficult to go back to playing DF without the basic set of DFHack and Therapist tools.

[zeves]

yes it wouldnt be so bad if we only had 50 dwarves, but with new hardware in place and the map bigger than ever, 200 dwarves seem quite difficult  to manage manually.

[nuker22110]

when using catsplosion list, the command shows animals that have already been slaughtered. When does the count reset? Also, I penned my falcons into a room with nestboxes and ran the catsplosion bird_falcon_peregrine and it just says pregnancies accelerated or something, but nothing happens? they dont immediately lay more eggs