GPNMilano wrote:But...don't both Gehn and TOC use this for their stuff?
That's correct. However, I'll say that the logical distinction here is that the shard admins, not the Age-writers, edit their
locally-canonical version for that shard. It's an installation-specific implementation thing (and honestly it's a hack too, but we can't really fix it without
blah blah content license). Cyan wrote this thing with the expectation that the publisher, maintainer, and content-creator is all the same person (themselves) and that they'd have one set of that file to maintain.
In an ideal world this stuff would be data-driven correctly and not thrown in a script file like it is, so that Age writers could write their stuff without needing to interact with global scripts. Maybe we'll get there someday. I was looking into a better way to do this some time ago, but it's hard to juggle it when we have to preserve 100% backwards-compatibility and can't upgrade/fix the existing content to use an improved system. I did work out a much simplified journal script that does away with the hardcoded journal defs, and I hope to do something similar for the linking books that will put this directly in control of the Age writers, and in a way that isn't prone to causing an unworkable mess.