[arty-fishL]

No, that's what Gloo does, this is completely different.

For a start "studentx" is just the name of any student, it was just an example for the given scenario, it could have been Tim or Bob.

In the case of a teacher having to cater for a lot of worlds being merged avoiding ambiguity is impossible, due to the sheer amount of things being added. Events and other things that cannot be manually named are automatically named "event0" and such. That means there will be a definite overlap of event names. Just renaming objects or events like you said is not an option. This wrecks the code by making object references invalid and summoning all sorts of potential errors.

In the case of VTOL lights this was not merging worlds, but adding children to objects, a situation where ambiguity can be controlled.

The idea here is that each student has their own package, like Java, so when they are bundled together who done what can be kept track of, therefore improving maintainability and readability, which are required to be of good standing order as things are sure to need refinement upon merging.