Print

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

[Master]

Should be fixed now...

http://github.com/downloads/peterix/dfhack/dfhack-bin-0.4.0.3b.zip

5am...

Salute!

[smjjames]

Should be fixed now...

http://github.com/downloads/peterix/dfhack/dfhack-bin-0.4.0.3b.zip

Thanks, and you really should get some sleep man. Unless you have a wierd sleep schedule like Toady does.

[diriel]

Thank you Peterix you rock!

[Mechanoid]

Should be fixed now...

http://github.com/downloads/peterix/dfhack/dfhack-bin-0.4.0.3b.zip

jawsome

[HeliumFreak]

Should be fixed now...

http://github.com/downloads/peterix/dfhack/dfhack-bin-0.4.0.3b.zip

Thanks, much appreciated

[MaximumZero]

Since Runesmith is DFHack reliant, Runesmith is probably the one that needs to update the offsets, not DFHack. I, however, am a total noob when it comes to this stuff, and could very well be wrong, but that's what makes sense to me.

[Brandon816]

As long as DFhack keeps its current functionality intact, even if it changes in implementation, it shouldn't affect other programs like runesmith. DFhack is there so that you have a frontend for other programs to more easily access the memory, so only DFhack needs to have the offsets updated. The only problem is that, like mentioned already, if "certain software tries to access things that *aren't [in DFhack] anymore*".

[MaximumZero]

Huh. Nice to know.

[MaximumZero]

It looks to me like there are two files in the Runesmith folder:

QtCore4.dll
QtGui4.dll

that aren't in the DFHack folder. Perhaps they're looking for something that moved? (I don't know how to get them open, and even if I could, I wouldn't know what I was looking at. I'm just hypothesizing, here.)

Anyway, sizeak was looking for offsets of some sort. Not sure if he's seen this thread.

[Urist McFumbler]

Hmm...

What would it take for you guys to set it up so that future versions of dfhack.dll are compatible with previous versions of software such as Runesmith?

There might be bugs when certain software tries to access things that *aren't there anymore*, but if all that's changing is memory offsets, shouldn't that only need to be updated once?

As far as I can understand it

If Toady does not do any drastic changes in the raws, I believe this would be no problem.

Unfortunately, drastic changes will happen so everything has to be checked and rediscovered.

Hence the delay.

Runesmith relies on the same offsets as DFHack.

DFHack uses some of the same offsets as DT.

There is interdependency and reliance but they are all unique.

But then again I might be wrong again.

[Haelfix]

Is there any chance that in the flow utility, that there could be some sort of option for making permanent water or magma generators?  Eg i'd like to make a river or brook.  In 40d at least, there were 'generator' tiles that you could hack in with various utilities.

[jaked122]

EDIT: fixed itself, seems to only happen on one save

[Shaostoul]

I was wondering, can you stop all water in motion with one of that hacks? I know the fluids? one can place water that is static, but can it or one of the others freeze it... and can someone explain the 'flowbits' dealio?

[peterix]

I was wondering, can you stop all water in motion with one of that hacks? I know the fluids? one can place water that is static, but can it or one of the others freeze it... and can someone explain the 'flowbits' dealio?

Well, flowbits. There are some flowbits for each 16x16 block of tiles and also for each tile. In dfliquids, you can choose if you want to make the spawned liquid flow or not.
So 'f+' makes stuff flow.
'f-' makes stuff not flow.
'f.' doesn't change flow bits.

If you don't want to spawn liquids, but only change the flow state, use 'f'lowbits instead of 'w'ater or 'm'agma.

[peterix]

EDIT: fixed itself, seems to only happen on one save

Can I have the save?