UMDLARS / one_night_in_sf

A story game demonstrating why physical security is important and complex!
2 stars 2 forks source link

Biometric tower maybe TOO interesting #145

Closed Saturn-99 closed 9 months ago

Saturn-99 commented 1 year ago

Testers got stuck on biometric tower for a long time, maybe this red herring is a little too red

pahp commented 1 year ago

Haha, oops. Maybe we make some indication that the tower will only open for someone with John Titor's biometric signature, and maybe you should try to find some other way into the lab...

spacehobo commented 10 months ago

This seems like it's easily fixed with better descriptions and responses. It's not uncommon for even Infocom games to tell the player "You'll need to find another way, because this won't work."

pahp commented 10 months ago

April had a great idea to have the biometric tower give some error messages about how it will only open for John Titor.

Saturn-99 commented 10 months ago

April had a great idea to have the biometric tower give some error messages about how it will only open for John Titor.

Lol, I don't think I was the one that came up with the idea but I'll take credit if you want to give it to me!

spacehobo commented 10 months ago

Looks like #193 implemented that. I do notice that if I try to examine the eyepiece it doesn't know that word. Perhaps we should copy the rejection text if you do anything to the other components of the tower, through cheap_scenery?

pahp commented 10 months ago

Whatever you think is best for an MVP; we can always refine later if necessary. Thanks!

On Mon, Jan 22, 2024 at 4:39 PM Abolish ICE @.***> wrote:

Looks like #193 https://github.com/UMDLARS/one_night_in_sf/pull/193 implemented that. I do notice that if I try to examine the eyepiece it doesn't know that word. Perhaps we should copy the rejection text if you do anything to the other components of the tower, through cheap_scenery?

— Reply to this email directly, view it on GitHub https://github.com/UMDLARS/one_night_in_sf/issues/145#issuecomment-1904953892, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADUPIKKPDZXQE44YPXIGFWDYP3TBJAVCNFSM6AAAAAA3K5UI66VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBUHE2TGOBZGI . You are receiving this because you commented.Message ID: @.***>

-- Peter A. H. Peterson, Ph.D. (he/him) Associate Professor Department of Computer Science University of Minnesota Duluth (land acknowledgment https://about.d.umn.edu/campus-history/land)

Saturn-99 commented 10 months ago

Looks like #193 implemented that. I do notice that if I try to examine the eyepiece it doesn't know that word. Perhaps we should copy the rejection text if you do anything to the other components of the tower, through cheap_scenery?

Can cheap scenery only handle two possible names/aliases? Could we not added eyepiece to that list? (If not could we just create a second cheap scenery object that is identical in description except it has eyepiece as a name?)

pahp commented 10 months ago

I don't know the answer to this question. @spacehobo ?

spacehobo commented 10 months ago

Yeah, you usually handle this by defining the response (description string, handler function, whatever) externally, and then just having like

OUR_RESPONSE_VAR = "It wibbles like a thing possessed.";
object Wibble "Wibbling Room"
with
 description "You're in a wibble station, where you see a foo (with the bar extension) and a baz with a quux, all wibbling away furiously.",
 cheap_scenery
  'foo' 'bar' OUR_RESPONSE_VAR
  'baz' 'quux' OUR_RESPONSE_VAR,
! ...

(or you can define like [our_response_fn; ... ] and refer to that)

Saturn-99 commented 10 months ago

202 fixed eyepiece issue

pahp commented 9 months ago

April tried to make it less of a red herring (more obviously not the right path), so we will close for now and reopen if needed.