SubAges are not created properly

Question

SubAges are not created properly

NadnerbD opened this issue 13 years ago · 2 comments

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.

Answer 1 · 2012-03-09T18:35:06.000Z

Uhh... we fixed this, right?

Answer 2 · 2014-05-17T01:47:56.000Z

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