Zooooooom (Level 10, v0.07)

Messages are moved here (should anyone ever want to see them again) once they are no longer applicable to the current version (e.g. suggestions that have been implemented or bugs that have been fixed).

Moderator: George Gilbert

Forum rules
Please read the Forum rules and policies before posting.
Post Reply
User avatar
Gambit37
Should eat more pies
Posts: 13715
Joined: Wed May 31, 2000 1:57 pm
Location: Location, Location
Contact:

Zooooooom (Level 10, v0.07)

Post by Gambit37 »

category: difference to dm

type: puzzle functionality/sound issue

Description:
The zoom puzzle is too slow - it's very easy to escape it. The timing was much harder on DM. Also, the sounds are not right. It should make a teleport buzz for every pad, but it seems to click for one pad, then teleport the next, click the next, teleport the next, etc...
User avatar
beowuuf
Archmastiff
Posts: 20687
Joined: Sat Sep 16, 2000 2:00 pm
Location: Basingstoke, UK

Re: Zooooooom (Level 10, v0.07)

Post by beowuuf »

comment on DM: something to do with the coding and running, but normal activating pressure pads had a slight delay in activating, while constant weight pads had an instantaneous effect. This was only noticable if the party was a 'boots of speed' party. Effects being triggered in the square/next square by a normal pad could actually be outran if the party was moving full speed along, while a constant weight effect could not be. Just something to concider when comparing as the zooom room in DM was a constant weight pad activated room, and therefore ran very fast compared to most other events.
Was unable to (permenantly) kill off ian_scho (Haynuus), Ameena, oh_brother (Westian), money (Falkor), raixel (Petal) and Lord_Bones (Aurek) in the DM D&D game Time's Champions!

CONGRATULATIONS TO THOSE WHO MADE THE GAME WHAT IT WAS - GREAT!
User avatar
George Gilbert
Dungeon Master
Posts: 3022
Joined: Mon Sep 25, 2000 11:04 am
Location: London, England
Contact:

Re: Zooooooom (Level 10, v0.07)

Post by George Gilbert »

Fixed for V0.08
Post Reply