Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proper linking framework #712

Open
diafero opened this issue Apr 18, 2011 · 0 comments
Open

Proper linking framework #712

diafero opened this issue Apr 18, 2011 · 0 comments
Labels
Client Enhancement Non-critical feature addition Python Issues stemming from the Python API files

Comments

@diafero
Copy link
Member

diafero commented Apr 18, 2011

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?

Hoikas referenced this issue in Hoikas/moul-scripts Jul 11, 2012
@dpogue dpogue transferred this issue from H-uru/moul-scripts Aug 29, 2020
@dpogue dpogue added Client Enhancement Non-critical feature addition Python Issues stemming from the Python API files labels Aug 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client Enhancement Non-critical feature addition Python Issues stemming from the Python API files
Projects
None yet
Development

No branches or pull requests

2 participants