Steele on 6/9/2016 at 02:11
Just wanted to say, that after a couple false-starts, I got this working! I actually found that I could do the Create Object function instead of Teleport Object (it's a default Thief object that doesn't have frob info, so that works out for my purposes), and so thanks again, all!
Yandros on 6/9/2016 at 03:04
Yep, I use the Create Object function on receptrons all the time. Glad you figured it out and are getting the hang of things.
Steele on 6/9/2016 at 13:45
Actually, I seem to have encountered an issue: My setup occasionally refuses to work o_O It usually works: Drop the item, it gets destroyed and replaced, door opens. Buuut I've encountered some oddness where the object won't disappear, or be re-created, or those things will happen but the door doesn't open (I'm wondering whether or not the switch is getting frobbed...). It bugs out roughly a quarter of the time. Is there something I should look for?
Here's the setup:
Object has "customstim" with an intensity of 1. It can be dropped or tool-dropped from inventory.
Table has a receptor for "custom stim" on Contact, no min or max intensity (as in, these options are checked off); It destroys the object, spawns a new version of that object (which doesn't have the customstim) into the correct place, and frobs a hidden lever (which is floating in solid space) which is linked as a CD to a "door".
Most of the time it works, but once in a while, nothing. I'd hate for several players to think they can't figure out a puzzle, or not have it reward them. Is it a timing thing? I've been ALT-G'ing in the same room as the puzzle and have been testing it over and over again right away, does it need a minute first or something? Should I put in a min or max intensity?
R Soul on 6/9/2016 at 14:22
It might be a timing issue. Make sure 'destroy object' is the last thing in the list. Thanks to NewDark, re-ordering receptrons is easy.
Steele on 6/9/2016 at 14:51
A few quick preliminary tests shows this working like a charm! I'll have to do more extensive testing when I get home from work, but I think it wouldn't be too premature to thank you at this point, so thank you!
Yandros on 6/9/2016 at 18:11
Good to hear. As R Soul mentioned, if a receptron destroys [this] then it should be last in the list, or else the ones after it may or may not get executed.
It is also generally a good idea to put bounds on the intensity. If the source's intensity is 1, then I usually put min=0.9 and max=1.1 to insure precision; for 2, I use 1.9-2.1 and so on. It also allows you to reuse the stim for a different setup (which might reasonably use the stim of the same name/type) and use a different intensity in the source and receptron(s) and thereby avoid any chance of cross-contamination, i.e. using an object intended to be used in A on B instead because B's receptrons are looking for the same stim across a wide open range. I hope that made sense.
