Tsar Hoikas wrote:Don't do this. Korman will export the text note "<agename>.sdl" for you.
plLogicModifier requests an exclusive lock from the server via plNetMsgTestAndSet before triggering. The delay between acquiring this lock and the trigger is the cause of many "fall through the floor" subworld bugs.
Once again, I wasn't aware of those two points, so thanks for the clarifications ! Cool that Korman already supports exporting SDLs. As for the server lock with the LogicModifier... I'm both glad it exists, but also impressed/worried by all those edge-cases Plasma/Age authors may or may not handle correctly. Networking is never an easy matter, especially when you start messing with custom Python scripts.
ametist wrote:Ok, so what you are saying is that if I export to URUoffline, which is URU:CC in my case, and I see any differences in the .py files in MOUL(which I have downloaded from this wiki) and URUoffline, I should use the x...py of the latter?
I would say you use both. Look at the "advanced logic" modifier - you can specify which node tree to use for which target version. This does require making two versions of the same node tree though, which will be nearly identical except for the Python script they use. (A bit annoying to setup and maintain, but hopefully not required in most cases when scripts are either identical or compatible.)
Chacal wrote:Also, using SDL allows the shard admin to set states manually, triggering changes for story purposes.
IMHO SDL variables in general are a good standard, usually they are both limiting and powerful enough to railroad you in the "right" way of doing things.
I don't know how Cyan did at the time, but with the tools we have offline (Offline KI's SDL commands, deleting the SAV file, VaultShop etc) they are reasonably easy to work with.