Print

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

[Dirst]

Have the actual limits being scienced yet?  I imagine that intermediate steps of some formulas could overflow if size or a stat was too high.  And that would all change when DF goes 64-bit.

1. Yes.

2. Yeah, 0.40.01 gave a sort of soft cap on strength dependent on unit size and carry weight; for example, having more than ~2,000,000 strength on a human-sized creature will make it so that that creature will immediately become as slow as possible upon picking anything up. Other than that, stuff just tends to work.

3. I don't think it will. DF going 64-bit doesn't mean all the uint_32s that make up attributes are going to magically become 64-bit. AFAIK even if he just uses "int" it still won't do that, "long" is the 64-bit integer type IIRC.

I didn't mean the stats' hard caps would change from 64-bit, but that the intermediate-result-overflow constraints might vanish.  But there's already a lot more science on this topic than I realized, so it might be trivial to test those chokepoints when a 64-bit build comes out.

[Bumber]

AFAIK even if he just uses "int" it still won't do that, "long" is the 64-bit integer type IIRC.

It's compiler and OS dependent. The only standard requirement is that short ≤ int ≤ long.

[expwnent]

No, he said somewhere he uses int32_t/etc everywhere.

[Roses]

I personally know of size and attribute values not translating directly from raws -> game (i.e. if you say strength should be 6000 it will just default to 5000). There may be other things as well that are raw capped but not game capped. I think I remember someone saying that materials may also be raw capped, but I'm not sure that can be changed since those values aren't stored in individual items but are just referenced directly from the raws.

Putnam brings up a good point though, there may be other soft caps which cause unintended behavior (I think the strength one might be from the tissue token [THICKENS_ON_STRENGTH] but maybe it's something else). Right now most of my scripts just check for the integer type and set the maximum according to that.

[Putnam]

Wait, I made the unbreakable katana in fortbent the maximum possible value for everything (trial and error). Yes, indeedy, the cap for strength values is 100,000,000. Adamantine's 5,000,000, so that's pretty good. Didn't check the cap on strain_at_yield, mostly because strain_at_yield is a really weird measurement to use. It's in percentage*1000, so TENSILE_STRAIN_AT_YIELD:100000 means that the material, once it reaches its TENSILE_YIELD point under tension, will have deformed elastically such that it's twice as long as it was before deformation began. This means, notably, that it's very difficult to define the stretchiness of an object as a function of the force applied to it; rather, it's a function of its strength divided by the force applied to it. Multiplying an item's strength by ten will divide its elasticity by ten unless STRAIN_AT_YIELD is changed to accompany it.

The cap of max_edge is 2147483647, or 2³¹-1.

[Roses]

That's good to know, and also fairly weird.

[Putnam]

class.lua:191: attempt to index field 'Physical' (a nil value)

EDIT: I have no idea why this is happening.

[Roses]

class.lua:191: attempt to index field 'Physical' (a nil value)

EDIT: I have no idea why this is happening.

I do, poor coding on my part, class.LevelBonus is always defined by default, but class.LevelBonus.Physical (or .Mental, .Skill, .Trait) is only defined if the class actually has those bonuses. To fix it for the version you have now replace (starting at line 191)

Code: [Select]

--Add/Subtract permanent level bonuses
 for _,attr in pairs(class.LevelBonus.Physical._children) do
  local amount = class.LevelBonus.Physical[attr]
  dfhack.script_environment('functions/unit').changeAttribute(unit,attr,amount,0,'track')
 end
 for _,attr in pairs(class.LevelBonus.Mental._children) do
  local amount = class.LevelBonus.Mental[attr]
  dfhack.script_environment('functions/unit').changeAttribute(unit,attr,amount,0,'track')
 end
 for _,skill in pairs(class.LevelBonus.Skill._children) do
  local amount = class.LevelBonus.Skill[skill]
  dfhack.script_environment('functions/unit').changeSkill(unit,skill,amount,0,'track')
 end
 for _,trait in pairs(class.LevelBonus.Trait._children) do
  local amount = class.LevelBonus.Trait[trait]
  dfhack.script_environment('functions/unit').changeTrait(unit,trait,amount,0,'track')
 end
with

Code: [Select]

--Add/Subtract permanent level bonuses
 if class.LevelBonus.Physical then
  for _,attr in pairs(class.LevelBonus.Physical._children) do
   local amount = class.LevelBonus.Physical[attr]
   dfhack.script_environment('functions/unit').changeAttribute(unit,attr,amount,0,'track')
  end
 end
 if class.LevelBonus.Mental then
  for _,attr in pairs(class.LevelBonus.Mental._children) do
   local amount = class.LevelBonus.Mental[attr]
   dfhack.script_environment('functions/unit').changeAttribute(unit,attr,amount,0,'track')
  end
 end
 if class.LevelBonus.Skill then
  for _,skill in pairs(class.LevelBonus.Skill._children) do
   local amount = class.LevelBonus.Skill[skill]
   dfhack.script_environment('functions/unit').changeSkill(unit,skill,amount,0,'track')
  end
 end
 if class.LevelBonus.Trait then
  for _,trait in pairs(class.LevelBonus.Trait._children) do
   local amount = class.LevelBonus.Trait[trait]
   dfhack.script_environment('functions/unit').changeTrait(unit,trait,amount,0,'track')
  end
 end
In the future release this will be fixed more elegantly.

[Putnam]

class.LevelBonus,Physical

[Roses]

thanks, edited original

[Roses]

So I really didn't feel this deserved another post anywhere, and I didn't want to clutter up anyone elses threads. Does anyone know of a utility that allows for easily taking sprites from multiple different sheets and creating a new sheet out of them? I have found tools that let combine entire sheets together, but I was hoping to be able to pick and choose individual sprites from a given sheet.

[Dirst]

So I really didn't feel this deserved another post anywhere, and I didn't want to clutter up anyone elses threads. Does anyone know of a utility that allows for easily taking sprites from multiple different sheets and creating a new sheet out of them? I have found tools that let combine entire sheets together, but I was hoping to be able to pick and choose individual sprites from a given sheet.

Not sure if Quiet-Sun's Tool does what you are looking for, but it's the only thing I know of that's close (other than straight-up image tools).

[Meph]

I think you are looking for this: http://www.bay12forums.com/smf/index.php?topic=77724

[Roses]

Well I got really annoyed with writing so I took a short break to brainstorm a road map for where I am planning on going with DF and DFHack. I have updated the first post with this information (removing my outdated todo list) so that you can see what my current plans are. Hopefully the first couple of releases will be quick and will happen in the beginning of June.

[Putnam]

I rewrote it to use json instead of persist-table. It's loads faster now. Main problem I can find is that I can't get it to save on quicksaves.