ToME: the Tales of Maj'Eyal

Hi,

well, i'm stuck in a far portal level and the loading time for generating level is never ending.

i have that "little" problem since the first level of that cursed farportal dungeon, but i somehow just have to relaod my save to make it work for now. don't work for the 4th level no matter how many time i try.

my problem is : i'm kind a lost in all that is technical stuff and i don't have any idea of what to add in order to make you understand what's the matter here. sooo if you need me to give you any other information just ask (but consider that if it's about log or stuff like that, i won't probably understand a thing about what you said if it's not cristal clear), i'll try to find this.

thanks.

What addons do you have running? That could really help someone figure out what to do.

As it is, I believe Stone Wardens, Item Vault, and Ashes tend to be the most common culprits. Try deactivating and reactivating those addons if you have them, and if that doesn't work, uninstalling and reinstalling.

well i try, i deactivate stone, item vault and arcanum class pack, didn't work, i re activate item vault only and it work. for now. but i'm a bit confuse, i thought stone warden and item vault were reliable so i didn't suspect them. well, not my problem it work, i'll try to interact with these if it come back.

thanks a lot, really, for once i had good hope for my character i'm glad i could save that game.

Oh sweet jesus no. The official addons are the most finicky, since they require some kind of authenticity. Still, glad to hear it's up and running.

They require connection to the server, which has been getting a lot of traffic due to the Ashes DLC bringing people back, plus ToME is on the current Steam sale.

I've been getting this problem upon trying to enter Angolwen for the first time (seems to be a crap shoot), and the only thing I can do is end the process, which ruins the save because now I'm stuck in a black void with LUA errors popping up if I move the mouse over the "terrain".

Every time this happens, a lua error has occurred and should be sitting in the log file, waiting for someone to read it.