Print

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

[bartavelle]

Is there any specific reason why the combat reports don't work? I keep getting an invalid list index error when I try to use it.

I did not update it for a long time. I suppose that it will be completly broken when next release comes out, so I'm just waiting for it to update the code.

[Gertack]

I will add the unchampionize script in the next release. It is however true that it would be better that creatures be really unowned when butchered. It would require a bit more work.

Doesn't look like the dwarves will use the bones, skulls, or fat of formerly-owned pets, unfortunately.  At least with the fat I can dump it and let it rot...

[Earthquake Damage]

DC fails to work properly once I'm running a fort.  It loads fine in the main and embark menus, but once I embark it stops working properly.  When I try to restart it, I get this:

Code: [Select]

version generic version, pid 4412, player 1c8
2107 words loaded
race 0 loaded
race 1 loaded
race 2 loaded
race 3 loaded
4b3b23
d457f4 d73868 d73844
Traceback (most recent call last):
  File "dfcompanion_prototype.py", line 409, in <module>
  File "dfcompanion_prototype.py", line 403, in __init__
  File "dfcompanion_prototype.py", line 123, in initList
  File "dwarfdbg.pyc", line 897, in getCreatures
  File "dwarfdbg.pyc", line 439, in getCreature
  File "dwarfdbg.pyc", line 288, in getName
  File "dwarfdbg.pyc", line 189, in printName
IndexError: list index out of range
I have no idea what to do from here.

[bartavelle]

Could you upload your save file somewhere?

[martinuzz]

Posting to confirm the unconscious 'bug'.
When you heal an injured dwarf that was resting, he will keep the unconscious state (exhaustion 60 thousand something). It's not really a bug I suppose. DC does exactly what it says. It heals a dwarf. It just does not wake them up.
Doing that manually fixes that proper.
So whenever I heal a dwarf, I also set the exhaustion value to 0 and press apply.

Oh - and, Bartavelle and Valdemar, thank you and many compliments for your great tool.

[martinuzz]

As for Earthquake damage's post: I have always understood that you should embark / load BEFORE you start DC.
Isn't that the problem?

[Earthquake Damage]

Could you upload your save file somewhere?

If you think it's save-specific, then it could be anything given that my game is heavily modded.

So I tried it on vanilla.  It worked.

Then, seeing that the problem was related to getting and/or printing names, I tried adding a new language file (LATIN from Rome Fortress 2.0, which you should be able to get from the modding forum) and set dwarves to use it.  Crash.  The only differences from vanilla DF this time was the addition of a new language file and setting the MOUNTAIN entity to use the new language.

So apparently languages can cause DC to crash.  Hell if I know why.  It doesn't crash when I set a dwarf's custom nickname and/or profession to an arbitrarily long string, so it's probably not that the words are too long.

EDIT:  So, I tried generating a new world with my heavily modded raws, only I removed the new language files and set all entities to use the standard languages.  DC works like a charm.  It's clearly a language issue.

[Greiger]

I believe it crashes because companion is set to only find 4 languages (human, goblin, dwarf, and elf) but if it finds more it doesn't know what to do with the extras and fails.

Doesn't have to be a fort language either any extra languages anywhere will cause the error. 

I recall there being a way to fix it and I had used it successfully in the past, but I don't remember how it's done.  Maybe scan around a bit on all the companion threads and you should find what needs to be done to fix it.

P.S. Had something to do with messing with the code to tell it to just ignore any extras it finds or something.

[bartavelle]

Yes I hardcoded the use of 4 languages. The following line in dwarfdbg.py could be altered:

for race in range(4):

So that more languages are used. (I suppose)

[Earthquake Damage]

Given that I know little more about Python other than it's a snake, can someone explain how I might modify DC to not crash if it finds too many or too few (in case I crank the limit to "for race in range(100):" or something)?

[Eita]

Hey, uhh... Does Companion work at all with 40d?

[bartavelle]

Hey, uhh... Does Companion work at all with 40d?

It should.

[bartavelle]

Given that I know little more about Python other than it's a snake, can someone explain how I might modify DC to not crash if it finds too many or too few (in case I crank the limit to "for race in range(100):" or something)?

You would need to get the quantity of languages from somewhere. I have been toying with another method of getting data that would not have that kind of problems. For now it is easier to do it "by hand".

[Gertack]

Mine shaft (http://www.dwarffortresswiki.net/index.php/Exploratory_mining#Mine_shafts) helper:

Spoiler (click to show/hide)

Code: [Select]

import sys
import struct
from dwarfdbg import *

if len(sys.argv) == 1:
  print "Execute with one number to designate mine shafts for that many levels starting at the bottom."
  print "Execute with two numbers for a starting level number (bottom = 0) and number of levels to designate."
  sys.exit(1)
elif len(sys.argv) == 2:
  level_bot = 0
  level_top = int(sys.argv[1])
elif len(sys.argv) == 3:
  level_bot = int(sys.argv[1])
  level_top = int(sys.argv[1]) + int(sys.argv[2])

dbg = dwarfdbg(lang = False)

ptrg = dbg.getLong(dbg.off_map_data)
for x16 in range(dbg.x_width / 16):
  ptrx = dbg.getLong(ptrg + x16 * struct.calcsize('P'))
  if ptrx == 0:
    continue

  for y16 in range(dbg.y_width / 16):
    ptry = dbg.getLong(ptrx + y16 * struct.calcsize('P'))
    if ptry == 0:
      continue

    for z16 in range(level_bot, level_top): # range(dbg.z_width / 16):
      block = dbg.getLong(ptry + z16 * struct.calcsize('P'))
      if block == 0:
        continue

### These should be "!= 1" for proper spacing.

      for dx in range(16):
        if ((x16 * 16 + dx) % 3) != 1: continue
        for dy in range(16):
          if ((y16 * 16 + dy) % 3) != 1: continue
          for dz in range(1): # range(16):
#            print "=== x16:%2u y16:%2u z16:%2u dx:%2u dy:%2u dz:%2u | %x %x %x %x" % (x16, y16, z16, dx, dy, dz, dbg.getShort(block + 0x1164 + (dy + dx * 16) * 2), dbg.getShort(block + 0x1364 + (dy + dx * 16) * 2), dbg.getShort(block + 0x1964 + (dy + dx * 16) * 2), dbg.getShort(block + 0x1B64 + (dy + dx * 16) * 2),)

            # This seems to indicate the tile is already dug out.
            wag1 = dbg.getShort(block + 0x1164 + (dy + dx * 16) * 2)
            if wag1 & (1 << 0) != 0:
              continue

            # This seems to indicate "outside"
            wag2 = dbg.getShort(block + 0x1B64 + (dy + dx * 16) * 2)
            if wag2 & 0xfd != 0:
              continue

            od = desi = dbg.getLong(block + 0x264 + (dy + dx * 16) * 4)
#            print "=== x16:%2u y16:%2u z16:%2u dx:%2u dy:%2u dz:%2u | %x (%u/%u)" % (x16, y16, z16, dx, dy, dz, desi, (desi & (0xf << 4)) >> 4, desi & 0x200)

            # Clear designations
            desi &= ~(0xf << 4)

# 0 = nothing
# 1 = mining +?
# 2 = up/down stairs
# 3 = channeling
# 4 = up ramp
# 5 = down stairs
# 6 = upward stairs
# 7 = mining +?
#            desi |= (4 << 4)

            if z16 == 0:
              desi |= (6 << 4) # Bottom level ; 6 = up stairs
            elif z16 == level_top - 1 and z16 != level_bot:
              desi |= (5 << 4) # Top Level ; 5 = down stairs
            else:
              desi |= (2 << 4) # Middle level ; 2 = up/down stairs

            # Reveal square
#            if (desi & 0x200) != 0:
#              desi ^= 0x200

            # Hide square
#            if (desi & 0x200) == 0:
#              desi |= 0x200

            if od != desi:
#              print "writing!"
              dbg.setLong(block + 0x264 + (dy + dx * 16) * 4, desi)


MAKE A BACKUP.  NO, MAKE TWO.

Use "reveal" rules apply: only works on loaded tiles, so use designate for mining to load them.

Execute with one number to designate mine shafts for that many levels starting at the bottom. Execute with two numbers for a starting level number (bottom = 0) and number of levels to designate. Puts upward stairs on the lowest level of the map if you designate it.  All other levels are up/down stairs except for the highest level given if you specify more than one at a time.

NOT RECOMMENDED TO USE ON LEVELS WITH ANY SORT OF DIGGING ALREADY ON THEM.  It tries to avoid open air and already dug sections.  It happily tries to dig a staircase in water or inside trees.

If you've offset your mine shafts differently, change the lines that look like:

if ((x16 * 16 + dx) % 3) != 1

Where the "!= 1" part is the number to change to (0, 1, 2). Both X and Y could vary for you; I picked the number that reveals the most area on the map.

(Note that I use 40c and the offset 0x264 worked better than Dwarf Companion's 0x260. It couldn't change the last block with 0x260.  YMMV.)

[Gertack]

One fly in the ointment is that DF seems to keep track of whether anything in a tile has been designated, and if that flag isn't set it won't check the individual blocks ni the tile for designations. So if the entire map is designated, you'd have to manually redesignate one block per tile to get DF to search it.