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.

Sign up for GitHub

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

Jump to bottom

SubAges are not created properly #39

Open
NadnerbD opened this issue Feb 5, 2012 · 2 comments
Open

SubAges are not created properly #39

NadnerbD opened this issue Feb 5, 2012 · 2 comments

Comments

@NadnerbD
Copy link
Member

NadnerbD commented Feb 5, 2012

When a SubAge is created, the parent should be made a SubAge of the child. (Insert an AgeLink to the parent in the SubAges folder of the child) Currently SubAge functionality only works by virtue of the fact that the client will attempt to create the parent age using the correct GUID if it cannot find the appropriate SubAge.
@branan
Copy link
Member

branan commented Mar 9, 2012

Uhh... we fixed this, right?

@branan branan closed this as completed Mar 9, 2012
@branan branan reopened this Mar 9, 2012
@Hoikas
Copy link
Member

Hoikas commented May 17, 2014

This appears to be unfixable in the current protocol. The server knows nothing about what kind of link the client actually wants.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@branan @Hoikas @NadnerbD