Guild of Writers

I had a spawnpoint in each test I made so that is not the source of the problem.

Did you say you put the unencrypted age file into the Uru dat folder? I doubt Uru can read that, so you will end up with no page being loaded... which also means that there is no spawn point
Basically you need the same age file twice, unencrypted for the plugin and encrypted (or obfuscated ) for Uru.

Plaintext uncencrypted .age files actually works fine with Uru. (.age as well as .fni and all whatdoyousee files for that matter). And that's pretty useful.

I've found a few other serious bugs with Cyan's plugin: 1) If you create light maps, then remove them, it tries to keep them in the textures prp(it just updates it to save time), but the prp can become corrupted 2) Creating a second page makes it revert to using a SequencePrefix of 100 on that page. (This seems to be what GPNMilano experienced before.) Drizzle24 now automatically corrects this second bug. The first bug should be pretty rare, and can be corrected by simply deleting the prps, so that Plasma regenerates them from scratch.

Oh yes, and I should mention that I've added a Recipe for swimming regions to my Cookbook! (Though Drizzle23 won't correctly convert the swim regions, so you'll have to wait for Drizzle24 to make use of them.)

That first bug should be fixable by running one of the cleanup things included with Cyan plugin. I know the component manager has a "Clear unused" feature, and I believe on the Plasma menu there is something to clean up extraneous references.

I've updated the cookbook to show the method Wodan has discovered for getting footstep sounds working!

(I've also updated the tutorial to include using the conversion method from Drizzle24.)

Regarding the footsteps technique.

you can choose every sound in "Group" but the only sound what you can hear at the moment is "Dirt no matter what sound you choose.

Not true. You can choose any sound and it will be audible. The problem is to make different regions sound different. To make it work you need to add another action to the responder state, triggering the other detector (I consider the case of two detectors). So you have RegionSensor1 and RegionSensor2, and corresponding responders Responder1 and Responder2. Add EnableDetector action to the current (1 by default) state of each responder, in parameters select the opposite detector, ie RegionSensor2 for Responder1 and RegionSensor1 for Responder2, and that's it. Ah, and another thing - check the "Trigger on exiting volume" box for each of the detectors. You may also want to make the detector geometry high enough so jumping won't trigger it.