yes, i vaguely remember that it was what i trying to fix. sadly, i didn't had (and still don't have a habit of writing detailed descriptions for redesign reasons in commit messages, so i cannot remember it better. but the code looks like i tried to address some specific problem (hence it is so ugly).

the original code had two big problems, both related to "object hell". i don't remember the exact details now, but that was the reason i rewrote hell from the scratch. they mostly manifested themselves as duplicate entities and "zombie" entities. 't was currupting the saves beyound almost any repair. k8IVAN may crash mid-game, but it should not affect the saves. i believe the only way to corrupt saves in k8IVAN is to trick the game into generating a new level with missing entities/configs — this is fatal, because the game updated the save moving PC to the new level, and then failed to generate the level itself. so on loading such save it tries to load the level which doesn't exist, and considers the save broken.

i don't remember the details (and i really need to revisit that code), but i believe that the game wipes old level from memory, so it need to save it before generating a new one. it also saves current player state along with it — which actually should be done only after the new level is generated. it's quite hard to follow the code, though, and i yet to convince myself to dive into it.

SPOILER ALERT. Click here to see text.

i just got a great idea for a-bomb implementation: it should delete saves, and crash the game. i mean, it destroys the whole world, without any way to survive. so hard that even the game is broken, and need to be repaired by restarting.

that will happen automatically for such scrolls. yet i don't want to strip other scrolls of their type descriptions… or maybe i should? so "(L)ook" at the scroll will only tell "a scroll", and the player will learn what is that scroll only by picking it up? hm…

this will require special `GetLookDescription()` method, but should not be that hard: simply route it to the standard one for everything except the scroll… i'll prolly implement it.

i definitely like it! "fluff scrolls" should be easy to implement: they all could be one scroll type with different configs, each config with the specific text (or set of texts to choose by random).

SPOILER ALERT. Click here to see text.


and to skip making another post: activated bear trap thrown into somebody may trap the victim (if you won't miss, of course).

thank you! i'll PM you if/when i'll implement "history scrolls" then, ok?


also, quick bugfix build is upcoming. i managed to royally screw ESP (you can only see monsters when THEY have ESP activated, lol). and other small bugfixes.

i.e. do it never.

tbh, i don't have any defined roadmap. some todos are "definitely later", but most of them just pulled off the list randomly.

yes, as a separate item class. actually, all scrolls are separate item classes, due to different effects. it's not hard to add more scroll (or book) types, it's just somebody has to write a flavor text. definitely not me — not with my broken English. (or they will be broken history scrolls.

p.s.: shelves full of history books would be a nice touch in Attnam dungeon, i think…

and by reading, i realised that i want IVAN to have the ability for having more hands. djini with 4. artifact for player for more hands. that is at least 4 attacks per round. devastating.

the game is not really ready for this, though: bodypart indices are hardcoded everywhere, and 2 hands (or 2 legs) is maximum. strangely, maximum number for heads is 1.

sorry. while trying to get rid of all those tv tropes tabs, i accidenally found kill 6 billion demons. i know i won't like the end of it (somehow authors believe that we need MOAR DRAMA, and love to kill characters we like at the end; i bet this won't be an exception), but i need to read it first, so i could say that the author is asshole.

i mean, no updates for a week or so, i guess.