xLinkingBookDefs.py & Linking Made Simpler

[Karkadann]

Been trying to get a linking book working using xLinkingBookGUIPopup.py. It works great for the ages listed in the xLinkingBookDefs.py but cant get it working for any of the fan ages so far.
Does any one know if their is a way to add my own linking panel to the xLinkingBookDefs.py python.


Linking Made simpler experiments starts from bottom of second page

[Tsar Hoikas]

Don't use this file for fan age linking books. We don't want a bunch of age writers modifying this file and having conflicts over which version is definitive... Use whatever diafero has provided with the offline KI.

[Karkadann]

Will do thanks

[Ehren]

It shouldn't be hard to use a linking panel with xLinkingBookDefs. You can see how Cyan refers to most of their linking books and linking images and just copy and edit that general form to refer to a new book. Paying attention to what "+ LinkEnd" means for the image's name...

Or are you saying you are trying to avoid editing xLinkingBookDefs?

[Tsar Hoikas]

DO NOT USE THIS FILE.

Don't even whisper the possibility of using it. Don't think about it. The only time you should ever, ever, ever do it is if you are the King of the Universe and have complete authority (ie you are Cyan). If you doubt any one of those things, don't do it. I don't do it. You shouldn't do it. Otherwise, you will cause pain, headaches, trials, and tribulations for all. Perhaps even the end of the world.

[GPNMilano]

But...don't both Gehn and TOC use this for their stuff?

Hoikas is right though. Sevkor's link will more than likely be provided through the Nexus, and from there a system can be written from scratch to deal with the linking out of Sevkor to the other fan ages.

[Tsar Hoikas]

In that case, Deledrius is "King of the Universe" and no one else touches the file...

[Deledrius]

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.

[Karkadann]

DO NOT USE THIS FILE.

Don't even whisper the possibility of using it. Don't think about it. The only time you should ever, ever, ever do it is if you are the King of the Universe and have complete authority (ie you are Cyan). If you doubt any one of those things, don't do it. I don't do it. You shouldn't do it. Otherwise, you will cause pain, headaches, trials, and tribulations for all. Perhaps even the end of the world.

GEE Thanks.....Now you got me curios. Are their any other components that cause Armageddon Cyan failed to tell us about?

[Deledrius]

GEE Thanks.....Now you got me curios. Are their any other components that cause Armageddon Cyan failed to tell us about?

Well, this is pretty easy, I hope: As a rule of thumb, if you find yourself editing scripts specifically to serve your Age in any files outside of the ones you've created for your Age, you're inviting a conflict down the road.