The bug that allows you to pass through monsers exists in arcade Pac-Man too, although there it mostly hits when the monsters aren't vulnerable.
rodneylives
Creator of
Recent community posts
I tried to post a screenshot, but I got an error saying "post: body: expected text between 1 and 20480 characters." The score in the screenshot was 52 points, lasting 32 seconds.
I had a game that went slightly longer, with a score of 57; I think the time was 37 seconds. I notice, when the game last that long, that the stars in the background scroll by in a repetitive manner, separating out into discrete lines.
This doesn't seem to me to be a very good score, but it seems like success is partly luck, in not getting a configuration of rocks that herds you inescapably into the corner.
I don't know if anyone's reading this, but I figured it's as good a place as any to mention it, a person ported a number of Videlectrix games to the awesome farflung futuretech of the Apple II: http://deater.net/weave/vmwprod/sb/
The Dungeon Maker has a couple of bugs. Most significantly, it doesn't work correctly in two-drive mode, which is how I've set up Dungeon for use for playing so you don't have to swap disks so much.
For storing items, Dungeon uses the Commodore-specific REL file format, which is difficult to simulate without also simulating a Commodore disk drive. If it weren't for that, I'd put the Dungeon files in a local directory in the distribution to play from there. It's weird how 34-year-old design decisions can affect emulation now.
There is at least one other significant Maker bug that I don't know what triggers it, that can once in a while cause the infuriating DISK ERROR when its time to save your work. I'm not sure if it also happened on normal hardware.
Ah, that co-author listed is Jon Mattson. I don't think he was a co-creator, he made two of the adventures LOADSTAR published for Dungeon. He was a prolific LOADSTAR contributor and made several other programs for it, including one game system of his own. But Dungeon predates his time with LOADSTAR, I think.
One point of difference with the arcade game is, it was very lenient with the knockback from doors. If you open a door with the knob on your side, and it knocks you into a cat, in the arcade the cat would be knocked out and you keep going. In this remake, if this happens, you lose a life.
It makes the microwave doors much harder to use effectively. I just had a game where every time I died it was due to this!
This is a pretty fun game! One thing I find it really needs, though, is a full screen mode. During the action, it's very easy for the mouse cursor to leave the bounds of the window, causing your skeletons to get lost. Or even worse, when trying to dodge, clicking outside of the window and causing the game to lose focus! It's also kind of hard to see in such a small window?
Hello! I have bug reports... some of these may not be bugs, but I figure I should report them just in case, all of them seem like a thing that may be awry.
* Shift-H conflicts between quick play move left and Help
* Game's ID game and food clock seems really easy: you begin with several extra scrolls of identify and a lot of extra food. I was tempted to leave a Ring of Regeneration on generally?
* You can move diagonally in corridors, and even through doors. This may be a design decision, but Rogue itself doesn't allow that.
* Maps have no loops, there's only ever one way to get anywhere.
* You can see parts of wall intersection tiles that shouldn't be visible.
* On normal levels, once seen, you can always see a tile's contents, even if you move far away from it. It makes the potion of Detect Monsters less useful (although it's never been really useful, even in Rogue).
* On dark levels, the reverse happens, which is even worse: you instantly forget the existence of walls when they leave your sight, making it difficult to get around.
* Quick play doesn't cut corners in corridors.
* Leprechauns don't teleport away when they steal money, Bats don't move randomly. These could just be design decisions though, they seem very obvious.
* Wands of Slow Monster don't have the expected effect? I'm not sure what they even do.
* There might be some confusion with ring hands when removing rings? Sometimes when I took a ring off, the wrong ring was taken off.
Sometimes the Zap command assumes the item you want to use? Not always though, it seems uncertain as to the circumstances. Maybe it's a keyboard interface issue.
* Monsters know where you are even if you're not in sight of them, and can pathfind directly to you. Rogue sometimes had monsters that magically just knew where you are too, though.
* Specifying an object on letter P at a prompt can result in inadvertent prayers. (For me, it happened after quaffing a potion on P.)
* Monsters seem to get a turn before magic effects aimed at them occur. This is what ended my first game, I was next to a Medusa, tried to teleport it, but the game gave it a parting shot.
* Cancellation doesn't seem to work on Medusa or Phantom? This is also connected with that game-ending occurrence. I zapped a Medusa, but she was still able to confuse me; it's possible that a nearby Phantom was in the way, but if it was it should have become visible?
Still, all in all, a good implementation generally! I'm sure bugs will get squashed over time. Thanks for making this!
I can understand that. It feels like the whole world is full of things, and so few of them are interesting, and the only way to tell what they are is to look at each of them individually.
It's something we're trying to combat at Set Side B, but we only have a limited amount of time and energy too. Sigh.
Interesting idea. My notes:
- Starting people on the middle difficulty by default, when they're not even sure how to play yet, seems like a bad idea.
- The high score screen forcing players to enter something is annoying.
- It wasn't obvious what color the next piece was going to be. After some examination I found where it was indicated, but the fact that the block wasn't that color seemed unintuitive.
A little bit of ambiguity in the rule description messed me up. When it says "Up to 2 cards can be placed sideways onto any other card," It doesn't mean up to two cards can be placed sideways onto a single other card as many times as the player likes, instead it means, up to two single cards can individually be played onto non-sideways cards over the whole board at once. I was wondering why sometimes the game wouldn't let me place a sideways card until I parsed it correctly.