Took me forever to get around to writing this one up... after a 53 floor amulet win dive and breaking the save file system, I've got some notes...
Agree on the never more than one per floor. They should be rare before floor 26 (you want an average player on a winning run seeing at least one, just so they know about them), but more common deeper than that, to the point that they become a one every 5 floors around... floor 100?Zaxxon wrote:
- Dragon hordes are a neat idea but they are far too common, creating massive GP inflation. I propose that there should never be more than one dragon horde per floor and that floors with dragon hordes on them should be both semi-random and exceedingly rare -- perhaps once every 50-100 floors (or more) and never occurring within the first 26.
Agree - hard-coded party rooms = BAD; don't like difficulty selector, though. Should be handled by better implementation of gameplay system. Hard-code allows for floor 25-26 level-dancing. IF you're locked in on keeping hard-coded party rooms, make it so that once you've cleared a floor with them, you can't level-dance to abuse them; they disappear when going back down. (So if you descend to floor 26, go up to floor 1, when you come back down there should be NO party rooms in floors 1-26.)Zaxxon wrote:
- The hard coded party rooms really switch the game into easy mode due to the increased equipment drops that accompany them. Although you are much less likely to find an "unwinnable" dungeon in 2.0, it's such a big change that I think it warrants the implementation of a difficulty selector (with only harder RT 1.0 style dungeons making it to the leaderboard). Regardless: While a case might be made for hard coded party rooms within the first 26 floors, I do not think they should occur after that. I also do not view reducing, eliminating or otherwise tampering with drops in these rooms as a "solution" because that would just push the difficulty in the opposite direction (and de-incentivize entering these rooms, making them almost as unappealing to explore as mazes).
Like the horde rooms, party rooms should be very rare between 1-25 (as rare as "you sense powerful magic on this floor" or rarer - only one other guaranteed party room before floor 26 for same reason as horde room - teach the player they exist), and then after that increase in appearance (but still random!) to say, 1 every 15 floors by floor 100 and deeper.
I'm personally unaware that any such mechanic exists in any version of RT (although I think there may have been one in Rogue). Maybe I'm just not paying enough attention on ascensions?Zaxxon wrote:
- Was the amulet's impact on your food consumption rate lowered/eliminated? If so, I'm not sure if this is a good change or not. A better way to handle it might be making food slightly more common on that first ascent from 26 to 0.
This should occur whether you're inside OR OUTSIDE the room in question, UNLESS it's obvious from outside the room that a door MUST be located in front of you... that situation should be exempt (there's no reason to punish the player for knowing the door must be there by kicking the wall).CommanderData wrote:3) Force find/open a secret door wakes all monsters within, even if you're stealthy.
I'm pretty sure that wearing two rings of slow digestion in normal Rogue effectively turned off the hunger clock / made it 0; in RT it seems to take many thousands of turns to become hungry, but it's not completely eliminated.CommanderData wrote:3) Yep, two rings of slow digestion would allow you to make thousands of moves before. I don't know the exact count off the top of my head but depending on how recently you ate before wearing them both it could seem like forever!
With that said, it is also possible the 64-bit update has things rounding a bit differently and causing the fractional food usage to drop to 0 per turn. Not sure if this is the case yet. If it is, I'm not sure that I will try to change it either... it could be an interesting "feature" for those lucky enough to find two rings of slow digestion!
I'd be very interested to know if you ever got hungry or weak after wandering with 2 of them on
Yetis seem to be the main culprit, and yes, they are generating with the level, but also seem to be a larger percentage of the wandering monster system than they should be on floors where Yetis hang out. Aquators have always spawned in great and annoying numbers; seeing no difference there.CommanderData wrote:Since this room full of Yetis was a party room, they should have all been generated at the start of the level and were residing there... and not generated by the wandering monster system as I was speculating before.
This doesn't eliminate the possibility of very odd random number generation, but it definitely tilts things towards some sort of strange monster creation bug (where it is duplicating a previously made monster instead of creating a new random one). Possibly something with the 64-bit code changing data types/sizes, but I would have expected it to be very common in that case- as in all monsters on each floor would be the same. Of course that type of problem would have been noticed immediately in testing! Darn obscure intermittent issues
__________________________________________
RT 2.0 Bug List:
- Wraith abuse to make HP levels ridiculously high
- Falling through a pit trap on to a floor that's supposed to have a level hint (party room et al) makes level hint appear on the next floor accessed via the stairs
- Unless a game makes it on to the Hall of Fame list on a user's device it isn't reported to the Bestrogues high score server. (Game Center should fix this in the future?)
- Monsters picking up items in rooms you've explored but aren't currently in causes a graphics glitch and gives away a monster's location and actions.
- Items that don't self-identify when used: scroll of mapping, wand of teleport away. There's probably others.
- Knock back (Str 24 and above) should only occur with blunt weapons. Knocking back a monster while hallucinating should not give the type of monster away in the message log. Xerocs should not switch graphics and appear as Xerocs but become fairies or unicorns.
- Speaking of Xerocs (ugh...): Xerocs should always spawn as "sleeping" and camouflaged, ESPECIALLY if spawned via the wandering monster routine (ideally, they shouldn't be spawning from that routine at all - they're effectively traps). Scrolls or rings of aggravate monster should not affect Xerocs (or if they do, de-camo first). Xerocs should always appear as items or stairs on mini-map unless the player has used a potion of clairvoyance or discovered they are Xerocs through direct interaction. (opinion) Xerocs camouflaged as stairs should use the regular stairs graphic.
RT 2.0 Possible Bug List / Gameplay Questions:
- Is there any particular reason why monsters (in general) won't follow a player into a maze? I know this is a holdover from Rogue, but I've never understood why this is the case.
- Threw the Amulet at a jabberwock, and then killed it on a later turn. Jabberwock didn't drop the Amulet on death. Ummm.....
- New trap graphics clash with green hallucination tiles making trap types unreadable.
RT Wish List:
- Amulet in inventory negates pit traps (in original Rogue this "floating" effect is what is supposed to allow you to go up the steps instead of being forced to only go down)
- Step and kill counters accessible in-game, instead of only being able to see them at the end on Hall of Fame list (or not at all, if your game isn't good enough to make your HoF page).
- Conducts - previous allows for player-invented conducts for additional challenge, but some built-in ones wouldn't hurt. Perhaps this can be melded into the secret character system somehow?
- Call out armor that is rustproof in inventory screen (either made rustproof by the player or naturally rustproof - leather, shozoku, elven).
- End-game item ID option
- Faster "death screen" scrolling or ability to just tap through it
- A way to scroll back / read the message log beyond the few lines at the top of the screen
- Monsters avoid traps instead of walking right over them unaffected. Gives player clue re: trap location. Or monsters could occasionally trigger a trap and be affected.
- List of scrolls / potions / staves / wands / rings types already identified during that run (a la Brogue) - should start empty and fill in as player discovers item types (presumably across multiple games).
- Daily seed competition (I know this one has been on your radar for forever as well)