MonsterDruide1

Your test does not cover some special cases yet, see these examples: ``` A: warning: Object Boss/GiantWanderBoss/GiantWanderBossStateOnGlass.o is placed before Boss/GKShip/GKShip.o, breaking the alphabetical ordering warning: Object Boss/Koopa/KoopaCappyEyes2D.o is placed...

I listed a few example in `A` above already, here are some more: ``` warning: Object MapObj/BreakablePole.o is placed before MapObj/BreakMapParts.o, breaking the alphabetical ordering warning: Object MapObj/CardboardBox.o is placed...

@LynxDev2 You mentioned Python warnings in #444 - what are those, and why can't those be fixed?

As far as I understand, it should just be some change like this: (also keep a backwards-compatibility-switch-thing like that) We'll want to use `filter='tar'`, to keep the executable flag on...

Is this fully finished then, or are there more ToDo's left before the transition?

If you want to revisit the discussion about the meaning of the tags, please do so in the appropriate Discord thread - I guess we're currently stuck in discussion here...

Also, this will probably conflict with the other, huge PR, so we'll probably get this one sorted out first, then rebase the other - but let's see.

No, as soon as something is `virtual` in a parent, all functions in subclasses should only be listed as `override`, not `virtual`.

Discord-Discussion about this: https://discord.com/channels/774687602996936747/1353271505273884692

Yes - fixed in #633, closing.