Sirius wrote:About having it in sync with the GZ - that's a good idea, but isn't the GZ always active online anyway ?
It's active when 'calibrated', which is server-specific. Admins can choose whether it's running or not. Cyan has left it running on MOULa since it was turned on initially.
Sirius wrote:Plus, there is the matter of fetching the state of the GZ across Ages, and uhmmm... let's say that's possible, but in most cases that's a real headache (might be possible, but this could require special instancing rules, which Shard admin may be reluctant to use).
From what I see at the moment, each city sub-Age which has the GZ beam just uses its own independent islmGZBeamVis SDL to activate the responder (why they're using a responder instead of a simple SDLBoolShowHide, I'm not sure yet, but it might be for the start-up and shut-down animations in the main GZ chamber). It's relatively simple to just flip them all on or off using the globalsdl command on dirtsand.
Sirius wrote:can PyPRP generate MarkerModifiers (or whatever they are...) so we can get KI coordinates in the Age ? I recall they are easy to setup but I'm not sure this has been implemented...
One has to be careful with these, though, since they actually give a precise location of the place, which could be lore breaking. That said, the same can be said of the projection light. And Cyan often did not bother with it themselves, so...
Doobes wrote:Yeah. It appears it's just a regular object (probably an Empty in Blender would work) with a Maintainer's Marker Modifier attached. No idea if there's AlcScript for that though.
Yeah, the coordinates for some of Cyan's locations are a bit... unlikely.
Looking at PyPRP, the way to make a fully-functional Maintainer's Marker is to add a dummy at the same location as your lamp with an alcscript property
calibration: calibrated.
Thanks Paradox for figuring out the value on that. Other possible values are
broken and
repaired.