SCI1.1: Adding to the score and Btest

[Cloudee1]

In need of a little guidance here. The AddToScore  procedure in the main script takes a value to be passed through Btest before changing the score. What is this doing... and does that mean that each AddToScore call needs to have a unique Btest value to be passed, since it is setting it as part of the change score process?

Code: [Select]

(procedure public (AddToScore param1 param2)
    (if (not Btest(param1))
        = gScore (+ gScore param2)
        (sq5StatusLineCode:doit())
        Bset(param1)
        (rm0Sound:
            priority(15)
            number(1000)
            loop(1)
            flags(1)
            play()
        )
    )
)


[lskovlun]

In need of a little guidance here. The AddToScore  procedure in the main script takes a value to be passed through Btest before changing the score. What is this doing... and does that mean that each AddToScore call needs to have a unique Btest value to be passed, since it is setting it as part of the change score process?

Simple. It makes sure that you can only get points for a particular action once. And yes, it does mean you have to have a list of unique flag numbers.

[Kawa]

And #22 seems to be "in a closeup shot so use an exit icon instead of walk."

One to start off with.

[troflip]

It looks to me like #22 has to do with being a fly. I haven't played SQ5 all the way through, but it seems like at one point you become a fly?

Anyway, the next iteration of the template game that will come out with (crossing fingers) today's release of SCI Companion has flag 22 completely removed.


So, you can start by adding score flags to your game.sh, starting from 0. e.g.

Code: [Select]

(define FOUND_PLUNGER 0)
(define UNPLUGGED_TOILET 1)
...


[MusicallyInspired]

Yes, eventually you beam onto a Genetix research station which is a parody of both the Dynamix name and the movie Silent Runnings. When you beam over there's a fly in the transporter and you end up beaming over with your head on the fly and the fly's head on your body. There are a series of puzzles in this form. Quite a fun section actually!

[Kawa]

Okay, forget I said anything then

*proceeds to use it as such anyway*

[MusicallyInspired]

You're still right, of course. There's a closeup section where you have to fly into a room through a keycard lock slot. There's a puzzle here to figure out how to access the door when you're back in your own body again, but I believe there is a button to exit closeup view in this scene...

[Kawa]

I was referring to the thing in Larry 1/5 where the Walk icon turns into Exit. On further investigation, it's not global flag bit 22 that determines this but this unnamed procedure:

Code: [Select]

(procedure public (proc0_22 param1)
(if (param1)
(icon0: loop(15) cursor(6))
)(else
(icon0: loop(0) cursor(0))
)
(if (== (send gIconBar:curIcon) icon0)
(send global1:setCursor((icon0:cursor)))
)
)Taken from Larry 5 because 1 won't load. Loop 0 is of course walk and 15 is exit.

I'd think this is a little more interesting for a template game's functionality than "being a fly".

*proceeds to steal implement it right*