Stonesense from Classic : Need this!!

[Kujila]

Stonesense is used to display a 3D isometric version of your fortress on Classic. It's really great for above-ground fortresses and castles so you can see your hard work in a "3D" format. It looks like Stonesense is an old project, and obviously the Steam version (premium) is not 1-to-1 to classic, but do you think there's EVER hope in the future of adapting Stonesense? It's open source on GitHub but I am not smart enough to know how it works, etc.

[Xcorps]

It needs DFHack.

[Hambone]

It will likely get updated once DFHack gets updated, since it relies on that. Its still an actively maintained project, so I don't see why it wouldn't eventually be updated to work on the new version.

[Kujila]

Originally posted by Xcorps:

It needs DFHack.

ahhh dang yeah, so likelihood of that is pretty low I would imagine.

maybe one day if the premium version takes off with community, I guess

Originally posted by Hambone:

It will likely get updated once DFHack gets updated, since it relies on that. Its still an actively maintained project, so I don't see why it wouldn't eventually be updated to work on the new version.

Nice, I hope so!

[Xcorps]

Originally posted by Kujila:

Originally posted by Xcorps:

It needs DFHack.

ahhh dang yeah, so likelihood of that is pretty low I would imagine.

maybe one day if the premium version takes off with community, I guess

Originally posted by Hambone:

It will likely get updated once DFHack gets updated, since it relies on that. Its still an actively maintained project, so I don't see why it wouldn't eventually be updated to work on the new version.

Nice, I hope so!

DFHack is currently under development for Premium. Based on comments in the Bay12 forums expect it to take a couple of months.

1. Ruby turndown
DFHack is looking at options for distribution via Steam. One of the blockers for this is DFHack's support for Ruby as a scripting language. It causes too many support issues. We need to rewrite existing Ruby scripts in Lua so we can remove ruby support without losing popular functionally.

2. Initless
As part of DFHack's ongoing usability overhaul, we're trying to make init scripts completely optional. This means that many tools need to be updated to persist their state so that init files don't need to be edited by the user to get the game back into a preferred configuration. Plugins can (and some already do) reload their state when the plugin is loaded, but we need to design and implement a similar mechanism for scripts, which have no analogous "load" hook. We have some thoughts about how this can be accomplished, but it needs more careful and thorough design.

3. GUI config for automation tools
Also part of the usability track. Many of DFHack's most popular automation tools lack in-game configuration UIs. Moreover, many of the existing UIs need to be rethought for the steam release. The DFHack UI widget library has matured significantly in recent releases, so there are many useful primatives for building UIs now.