luceroweb / haunted-house-game

https://luceroweb.github.io/haunted-house-game/
1 stars 12 forks source link

Crystal orbs encounter poses no danger to the player #115

Open cgreen-bitwise opened 2 years ago

cgreen-bitwise commented 2 years ago

Devices

Device name: Custom Desktop PC Processor: Intel Core i5-6600K 3.5 GHz Quad-Core Processor System type: Windows 10 Pro 64-bit operating system, x64-based processor Resolution: 1920x1080 pixels, 16:9 ratio (~92 PPI density)

Device name: SM-G950U - Samsung Galaxy S21 5G (USA Unlocked) Processor: Octa-core (1x2.84 GHz Kryo 680 & 3x2.42 GHz Kryo 680 & 4x1.80 GHz Kryo 680) System type: Android 11, One UI 3.1 Resolution: 1080 x 2400 pixels, 20:9 ratio (~421 ppi density)

Brave Browser Version 1.31.87 Chromium: 95.0.4638.54 (Official Build) (64-bit)

Firefox Browser Version 93.0 (20210927210923) (Official Build) (64-bit)

Expected Behavior

Each encounter in the haunted mansion poses a danger to the player, but if they choose the correct action, they can find the silver key.

Actual Behavior

The orbs don't do anything if you ask them if they're hungry or if you ask the puppet. The only action that ends the encounter is if you select "Talk to the heads". The player has a chance of finding the silver key after this encounter as well, at no risk of losing the game.

Steps to Reproduce Issue

  1. Begin game
  2. Search the rooms until you get the crystal orbs encounter.
  3. Click on the "Ask if they're hungry" and "Ask the puppet" options.
  4. Observe that they don't progress the story.
  5. Click on the "Ask the heads" option and observe it passes the encounter, with a chance at finding the silver key at no risk.
luceroweb commented 2 years ago

@ProjectErostribe is our Haunted House story editor. Myles, should we consider adding a fail response to the Orbs event?

cc @cgreen-bitwise @lreyes-qae

SmiJa commented 2 years ago

@cgreen-bitwise we are reject the ticket. The reason for the rejection is we have decided to ultimately remove the Crystal orbs event. That decision came from a discussion of confusion that was found in the event.

cc: @lreyes-qae @luceroweb @ProjectErostribe