ToME: the Tales of Maj'Eyal

Yes, if you're a donator (eg. bought the game), one of the perks is Exploration mode which grants you infinite lives.

Usually downloading and using the standalone version from the homepage (https://te4.org/download) circumvents the crash

Tranquil Meadows is a Cursed-exclusive zone. It does not generate when playing any other class.

Lmao

Well at least it can only happen on 1 character

Just to make sure, you do have the Ashes of Urh'rok DLC active right?

If ya catch me either in the ingame chat (saying "mod" pings the mods, primarily me) or more reliably on the ToME discord (same name there as here), I can fix the save manually.

Did you have Paradox pool? If you don't have any talents that use Paradox, you might not have the Paradox resource in which case any talent which relies on your paradox modifier might not work as expected or be locked at low values

You can simple open the DLCs with a program like 7zip or winrar or whatever and rummage through them, they're in there somewhere. (.teaa/teac/team etc are just fancy names for a compressed file)

Usually if you're stuck in the "time void", as in time passes by at an extreme speed it means your character didn't load into the level for some reason. Most of the time this can be recovered from with a simple mod tp, so just call for a mod in the ingame chat or ping us on ToME discord an...

Thanks for the reports. This should be fixed now.

Stone Warden isn't a bonus class for donators anymore. It's now a normal unlock in the base game (Possessor tooks its place as the bonus donator class)

Update:

The issue is now fixed. However, addon authors need to manually re-add the description for the affected addons.

"Failed to complete the lich resurrection ritual" means that you died as a Lich, Neverending Unlife let you resurrect but you failed to meet it's requirement of killing a unique or higher rank enemy within X turns, and you died proper.

All clones of player break the ID quests currently

Hey.

Sorry I forgot to post in here. The issue is known and under investigation (there are couple other server/web service related issues as well currently, and the easiest guess would be it's due to complications from the recent server migration.)

I'll be back once the problem's bene solved