You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Linking in Uru is a pure mess, and being able to do it via Python or using a responder doesn't make things better. In the end, everything needed to link to an age should be the age filename, the spawn point name, and optionally a GUID if a specific instance is desired. The rest should then be done automatically and safe (so invalid linking requests are aborted, no vault issues).
For Offline KI, I implemented a system that does this, except for the GUID - but since that essentially just disables some age finding automatisms, it should be easy to add. From all I learned, linking did not change very much for MOUL. This xLinkMgr relies on a configuration file (that could easily be embedded into the code though) to know which ages exist, what they are properly called, which linking rule they need (including sub-age relations), which spawn points exist (name and title) and what the default spawn point is. This information can then also be used to fill the Nexus, provide consistent age names in the KI and so on.
So, I suggest to include xLinkMgror an equivalent system into MOUL Python - and find some way to also sanitize links through plResponders. Is it possible to pass that through Python as well?
The text was updated successfully, but these errors were encountered:
Linking in Uru is a pure mess, and being able to do it via Python or using a responder doesn't make things better. In the end, everything needed to link to an age should be the age filename, the spawn point name, and optionally a GUID if a specific instance is desired. The rest should then be done automatically and safe (so invalid linking requests are aborted, no vault issues).
For Offline KI, I implemented a system that does this, except for the GUID - but since that essentially just disables some age finding automatisms, it should be easy to add. From all I learned, linking did not change very much for MOUL. This xLinkMgr relies on a configuration file (that could easily be embedded into the code though) to know which ages exist, what they are properly called, which linking rule they need (including sub-age relations), which spawn points exist (name and title) and what the default spawn point is. This information can then also be used to fill the Nexus, provide consistent age names in the KI and so on.
So, I suggest to include xLinkMgror an equivalent system into MOUL Python - and find some way to also sanitize links through plResponders. Is it possible to pass that through Python as well?
The text was updated successfully, but these errors were encountered: