ToME: the Tales of Maj'Eyal

That's good to know. Really wish I knew what was going on with char creation yesterday (It was basically failing 3 out of 4 times I went to character create).

Provided its working sanely tonight and I can get to the upload prompt, I'll try and upload it.

Tried again with similar luck. Either its broken or something really doesn't want me to get to upload it

because of invalid hash, using this addon means i can't play online and can't save chars to the vault

can this be fixed please?

Grawr. WIll be trying again this weekend. It just really would always explode these past tries when I went to upload.

Things are fixed. Wish I knew why it gave me trouble for so long but slowly putting it back together got something working minus a weird unused esp table.

Dracos wrote:Things are fixed. Wish I knew why it gave me trouble for so long but slowly putting it back together got something working minus a weird unused esp table.

Glad to hear it, thanks for your work!

There's still a bug with option changing Fixing it.

And that is now fixed.

Also added support for auto going into stealth (option controlled).

Blargh.

so, it is a valid addon now? the game sucks without this, i don't know why it isn't in the main code tbh.

Yeah, it is. Available off steam and te4.org as usual.

Question for other addon creators:
How do you safely reference talents in DLC? I'd like to add in support for the various healing and recovery inscriptions that are new in Embers, but I don't want to break the addon for folks who don't have embers.

Hide the references to their talents inside an 'if' statement that looks for DLC stuff.
For example, my adventurer plus addon only loads the tinker stuff:

class:bindHook("ToME:load",
function(self, data)
if ActorTalents.talents_types_def["steamtech/automation"] then
Birther:loadDefinition("/data-adventurerplusaura/birth/classes/tinkerhero.lua")
end
end
)

Unfortunately I have to report that I've traced a pretty serious bug to this add on

With the add on active sustain talents that drain steam (I didn't check for standard sustains, but most steam sustains are drains) do not deactivate when your steam hits zero. Now that I now what's causing it I will just avoid exploiting it until it can be fixed (although infinite rocket boots are very tempting...).

I think your superload of _M:act() in mod/class/actor is overwriting the one used by Embers to check for steam sustains:

Orcs wrote:local act = _M.act
function _M:act()
local ret = act(self)

-- If resources are too low, disable sustains
if self.steam < 1 then
for tid, _ in pairs(self.sustain_talents) do
local t = self:getTalentFromId(tid)
if (t.sustain_steam or t.drain_steam) then
self:forceUseTalent(tid, {ignore_energy=true})
end
end
end
return ret
end

Hope this is helpful, and I appreciate your work.

Well, that's no good, and thanks for tracking that down. I'll take a look tomorrow at it.

Edit: Oddly enough, I never noticed. I think it's because I never let steam come close to zero.

Fix published. Still doesn't support the new inscriptions though.