dirtsand
dirtsand copied to clipboard
SubAges are not created properly
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.
Uhh... we fixed this, right?
This appears to be unfixable in the current protocol. The server knows nothing about what kind of link the client actually wants.