beware 1642

[Atarlost]

Why not look at the ToME dungeon generation code. It can construct dungeon levels one room without difficulty. It must either have some failsafe code to avoid endless loops on small levels or use a different algorith that produces superficialy similar dungeons at least for some room settings.

[d_m]

Originally Posted by Atarlost

Why not look at the ToME dungeon generation code. It can construct dungeon levels one room without difficulty. It must either have some failsafe code to avoid endless loops on small levels or use a different algorith that produces superficialy similar dungeons at least for some room settings.

I think the concern isn't that the current code can't produce one room dungeons, but rather that the rest of the Angband code assumes that there will be N rooms (where N is probably at least 4). It's easy to make the generation code create only one room if that's what is desired.

[Atarlost]

I thought the problem was the corridor generation looping when there was only one room. I guess I misread something.

[PowerDiver]

Originally Posted by Atarlost

I thought the problem was the corridor generation looping when there was only one room. I guess I misread something.

That's the infinite loop problem for generation. There are other infinite loops for things like Portal [failed my test after I fixed the rubble bug] and who knows what else.

What if all open space is inside vaults, because the level is just 1 vault? Aren't you guaranteed not to start in a vault? Isn't phase guaranteed to take you out? Who knows what would happen.

Also, tiny levels make telSelf and telOther not be escapes. That's a fundamental change to how the game is played. IMO this deserves more discussion than symmetric LOS or item generation.

I continue my 1642 game, and have survived a couple small levels just through luck. I guess I should post a dump.

[takkaria]

The dungeon used to be variably-sized; Ben took it out when he refactored the code. I don't think it's a massive fundamental game change.

[Magnate]

Originally Posted by PowerDiver

Also, tiny levels make telSelf and telOther not be escapes. That's a fundamental change to how the game is played. IMO this deserves more discussion than symmetric LOS or item generation.

Naughty - you are on record several times as saying that tSelf is not an escape. The effect on tOther is IMO connected to a long overdue revisiting of monster detection ranges, which should be considered along with other changes following from variable-sized dungeons.

I'm now going to start a new thread about the caveats of playing dev versions.

[PowerDiver]

Originally Posted by Magnate

Naughty - you are on record several times as saying that tSelf is not an escape.

Well, it's a chance at an escape? It's an attempt to escape?

I wouldn't use it when hurt, but at full hp I do use it, especially early on a new level. Sometimes. Hmm. I wonder if we need different terms.

[Magnate]

Originally Posted by PowerDiver

Well, it's a chance at an escape? It's an attempt to escape?

I wouldn't use it when hurt, but at full hp I do use it, especially early on a new level. Sometimes. Hmm. I wonder if we need different terms.

Just teasing really - I know what you mean, in that the variable levels do make a difference to it. Perhaps "escape" and "guaranteed escape" would do - currently only new levels (stairs, tLev, DD and Alter Reality) are guaranteed escapes, I think.

[Marble Dice]

I'd consider ?*Destruction* and similar effects as true escapes, too.

[Pete Mack]

Originally Posted by PowerDiver

Well, it's a chance at an escape? It's an attempt to escape?

I wouldn't use it when hurt, but at full hp I do use it, especially early on a new level. Sometimes. Hmm. I wonder if we need different terms.

I usually use "evasion" for (successfully) declining a fight, and "escape" for an impending instakill situation.