Bay 12 Games Forum

Question about the onReactionComplete eventful trigger. IIRC it only triggers when a product is actually created, is that still true? Also, if using both onReactionComplete and onJobCompleted will the always trigger in the same order, or will it be somewhat random which one triggers first?

Alright, I've got the basics of the Enhanced Reactions all up and running. I am still experimenting and testing a bit with how the various triggers are being handled together (onJobCompleted and onReactionComplete) along with my custom triggers, but they seem to all be cooperating together. The trick being making sure that the required information is available regardless of if a product from a reaction is created or not.

Currently script calling is enabled through the system, which lets you do anything you could want, but I am also working on getting shortcuts set up for some of the more obvious uses (miasma/smoke generation, long time reactions, variable reactions, power/water/magma consumption, etc...).

Some of my previous work on the Enhanced Reactions has been invalidated with the 0.47 release as well, which means I still want to go through and make sure I am not duplicating anything that is currently doable with the new reactions.

I've looked for bad items in the item list and haven't found them. The problem, from the outside, is that the corruption is seen by one or more equipment lists containing garbage entries, but those are generated on the fly (I've tried hacking them to remove a bad entry, and it's back the next time the list is generated). To me, it seems that the structure the data comes from isn't the regular item lists, but something else, unknown what (Toady would know, but I don't think anyone has asked him).

Yeah, military equipment (assuming that's what "equipment" is referring to) is likely stored separately from the items themselves.
Were you modifying the equipment list in a viewscreen? Those are indeed usually temporary copies. I'm not familiar with the exact structures at play here, but I could take a look at one of the corrupted saves.

I've looked in the past, but I've never been able to find the root location of the items. I'm thinking that somewhere there is a list of types, subtypes, mat_types, and mat_subtypes and that for one reason or another one of the four gets incorrectly filled in (or maybe not filled in) and then when the equipment lists get filled from those lists the corruption occurs.

My thought for why it is stored this way is because that is how the entity resources are stored, and I have had corrupted entity lists when I have accidentally removed a subtype entry and not the corresponding type entry.

You certainly could fairly easily combine a few things and create a script that allows you to extract blood, tears, pus, etc... You could even have it set up like the gui/create-item script where you select an extractor, an extractee, and the material to extract. You could also turn it into a more automated thing by creating reactions for extracting blood and such, and then tie the script into those reactions so that they functions similarly to how the milking reaction goes.

so I just got an adv mode idea given how stealth works and how it's invisible to the player but not to everyone else. is it possible to make Dfhack npcs that spawn in and hide out of site to do stuff you can't just force with dfhack yet.
like making an unit named Aimed Shot that hits like a space station and sets up aimed attacks that pierce and probably sticks into the person you told Aim to hit.
you could even set up how much force and damage the attacks are you could even assign the same historical figure to Aimed Shot so any kills they get would transfer over to the player.

this script idea would only work as long as the whole sneaking thing isn't fixed and probably break if someone uses any reveal any hidden units scripts.

Theoretically I think it would be possible, but spawning units with DFHack can be problematic, so I'm not sure you would want to do that too much. I also don't think there are too many things that a hidden npc could do that you couldn't do without it. For instance, in your example, you can already make an attack and add it to a unit and modify it's attack values

Quote from: Warmist on May 22, 2020, 12:06:55 pm

-snip- Also there would be mandatory maintenance and support part as anything that does not eat/sleep/bleed is boring and must have drawbacks

Feel like the big issue with golems is if you give them emotions or not, if you don't they probably work fine until one goes extremely distracted and crafting with them might get shoddy I heard, if you do give them emotions then they act like an immortal fort citizen that is affected by corpses and stress can cause them to go mad so you end up having to find a way to de-stress the golems.
which already feels like maintenance.

You could set up "pylon" buildings that periodically de-stress golems automatically when they walk by them. For even more flavor you could make them naturally super weak and slow, then have the pylons give them a massive strength and speed boost which lasts a certain amount of time, so you would need them to almost always be close to the building

yes but i still do not understand why you would want to do something that are applied to all castes after you have defined castes when that would mean writing one additional line of code in [SELECT_CASTE:ALL] and pressing tab one additional time per line of code you want to apply to all your castes, why not just leave defining castes to the end of the document and defining tissue colors and hair lengths and stuff a bit earlier? Why do they use this seemingly ineffective method? Is there some kind of reason why it is necessary to define all the tissue appearances last? Is it so that they can be found`and edited more easily? is it necessary to define tissue appearance at the very end of the creature for some technical reason? Sorry if i come of as a bit rude i just dont understand

As long as the appearance modifiers are defined after the tissues they modify, I'm fairly certain they don't need to be declared after the castes.

Also, the tabs are not necessary, there is no indentation requirements for the raws, so it really is just one extra line

Question about speed in lua, is there a notable difference between these two?

if Table.SubTable then
  for k,v in pairs(Table.SubTable) do
    ...
  end
end
vs

for k,v in pairs(Table.SubTable or {}) do
  ...
end