Print

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

[Polemicist]

..With the past two versions of Masterwork.


It seems to nuke the existing dwarves, while sending a new seven dwarves in their place. Huge bummer! I've made several different worlds, re-downloaded / reinstalled, used 43.03 and 43.05, and reclaim seems to not be working across all of these.

Been having a crazy amount of crashes, too. Used LAA, fixed some crashes, didn't fix others. I turned off most of the additional creatures mods and this seems to have fixed the crashing (for now.) Currently using 43.03 until I see stability increases with 64 bit DFhack.

Anyway! Thanks for the amazing mod regardless, Meph and company. I'm sure I'll keep using it crashes and reclaim bugs aside. <3

[LMeire]

..With the past two versions of Masterwork.


It seems to nuke the existing dwarves, while sending a new seven dwarves in their place. Huge bummer! I've made several different worlds, re-downloaded / reinstalled, used 43.03 and 43.05, and reclaim seems to not be working across all of these.

Been having a crazy amount of crashes, too. Used LAA, fixed some crashes, didn't fix others. I turned off most of the additional creatures mods and this seems to have fixed the crashing (for now.) Currently using 43.03 until I see stability increases with 64 bit DFhack.

Anyway! Thanks for the amazing mod regardless, Meph and company. I'm sure I'll keep using it crashes and reclaim bugs aside. <3

Are you reclaiming with the same civ that you retired with? Because if not then the old population will register as "hostile" visitors in-game. They don't usually attack or anything, but they won't be yours.

[Polemicist]

Double checked, that's not the issue. Reclaiming with the same civ. The older dwarves are still present, however they're all listed as hostile as if they were a new civilization.

Double bummer.

[Amostubal]

did you makes sure you don't have 2 dwarf civs?  I've done that... I try not to bring back a fort that wasn't abandoned.  I've had too many weird things happen.... had a whole mountain side(30z) drop one z suddenly and without warning... no idea why.

[Polemicist]

Two dwarf civs? No no, the one I'm reclaiming with is the same civ that I built the fort with.


It isn't abandoned either, it was retired. ...I dunno! I suppose, let's see if we can replicate this issue with anyone else on 43.03 or 43.05? I've encountered this issue across both of those releases and I can still reclaim just fine on vanilla, so I'm sure it isn't an issue on my end.

Could be incompatibility with one of the submods?

[Amostubal]

well try it a few times and see what results you get.  try different races altogether (kobold civ unretiring a kobold civ).

also know you can verify that it was abandoned or retired or fell by tabbing over in the reclaim menu.

[Vozhban]

Last time i had the same problem with reclaim, it was solved by disabling some DFhack plugin, that gives some options while you choose a site to embark(it had its own menu on that screen). Don't really remember it's name, though, maybe it's "embark anywhere".

[Amostubal]

Oh?  If so than that's a bug for the Dfhack people, I think embark anywhere is one of there packed scripts, I can check and see if MWs is the most up to date version.

[Polemicist]

How do I disable Embark Anywhere? Just remove the script out of the Plugins folder in DFHack? I'll try that (and I'll try a few different civs, Amostubal) and I'll report back.


Also, Amostubal - good on you for filling Meph's shoes in his absence. Sure it's not easy! Thought I should tell you, while I can't speak for everyone, I certainly appreciate and I'm sure others appreciate the stuff that you do for this community, so thanks. <3

[Amostubal]

open onLoad.init it should be near the top embark anywhere, just put a # in front of it.