Karkadann wrote:Instead of a linking book, I have a stone arch from my Relativity age (which by the way I really should start working on) would in be possible to create a stone arch that you can walk threw and end up in another age, or another sub world of the same age. if so How??
Yes, Huinexus does something like that. If you're talking about using UamVars to do that, it would require another another UamVar or two, but could certainly be done in a future version. The idea is to start with just these few items and increase them as things are needed.
diafero wrote:One bug is unfortunately still present: I installed the "enabled" version of the Network Access package, and now it's telling me I am risking my security and so on. It should definitely not do that on each Drizzle startup after I deliberately decided that I want the access to be enabled.
That's not a bug, especially not if people start saying things like "You need to install the enabled version of NetworkAccess to play this Age", because people might easily forget that they may be silently being spied on. This warning is an important part of reminding them that having NetworkAccess enabled puts them at that risk, and that there is no way for them to know. This warning makes sure they know.
diafero wrote:EDIT: I just noticed that the KI plugin is using private xLinkMgr functions and variables that might change in future versions (which is why I marked them with a "_" at the beginning). And it intersects the xULM by replacing a core function. I will try to remember that should I need to change them, but I can not guarantee such unforseen API usage to be stable. I had some ideas about how the custom Relto books could be done better, long before this was released - but I am not yet sure when I have time and will to realize them.
I also wonder why I was not notified that these obviously internal APIs are required by the plugin.
It doesn't replace the function; it appends to it. It's the cleanest way to do it without replacing components of the Offline-KI, which I don't want to do. I know that this API might change, but I would just update the Uam KI plugin to match in such a case (and release at the same time), but in practice, it shouldn't change often/ever (after all, the format the Offline-KI uses is still even the ULM one!). Ages obviously shouldn't use the Offline-KI API, as they should be future-proof, but this is another "(required!)" package that can just be updated.