More info about various object types

[devinacker]

I've recently been digging around in the SS1 source release, partly in order to update/correct some info about unused object types in this tcrf.net article that I was working on a while back, and I've found some additional info about various stuff. (Relevant issues: #39, #40, #41, #43)

• The "area" triggers (12/0/5 and 12/0/6) are implemented and use a radius-based condition (TRIGGER.C:2293-2312)
• The unused vending machine objects (9/4/x) work the same as normal receptacles (9/1/x) (OBJUSE.C:955)
• The condition field for normal receptacles (9/1/x) includes an optional trap message if the player tries to use the wrong item (OBJUSE.C:987-993)
• The condition field for the retinal scanner is based on the "current frame" value of severed head items, not the MFD image index (OBJUSE.C:961-964)
• The unused "control panel" object (7/5/5) works the same as the control pedestal (7/5/6) (OBJUSE.C:1164)
• The first byte of human corpses' SmallStuff struct is the treasure type index for random loot (AI.C:590-591)

I may be adding some other small things after more investigation/experimenting.

[devinacker]

Added:

• Cyberspace decoys (8/5/10) can be made to destroy another object when destroyed by the player (OBJSIM.C:2269-2271)

[devinacker]

Actually, about the bigstuff "control panel"/"control pedestal" types, I think the actual behavior is still a bit different than what I have... I need to experiment with these some more.

• Most(?) bigstuff objects with the UseType set to "use", except for screen-like objects, have two trigger object indexes. For example, "scope" (7/5/1), possibly also "control pedestal" (7/4/0) (see OBJUSE.C#1192-1198)
• For the "control panel" w/ screen (7/5/6), if the first trigger object index is not zero, the next int16 might be a second trigger object index? (need to test)
• For the unused "control panel" (7/5/5), it won't actually display a screen, but if you assign it one of the camera views it will work the same as 7/5/6, including triggering an object (or two objects?) instead, if specified

[dertseha]

Hello @devinacker ! I know of the TCRF article - great job on that one!
Thank you for the contribution - these are all the gritty details that the code now exposes.

The retina scanner for example was one that irked me quite some time :)

[devinacker]

Thanks for the merge :) I'm still experimenting with some stuff so I may have another PR with some more information sometime after the holidays.