TickEvent - why Phase over sub-event?

[Ernio]

Like the title. While I don't really mind, it's been bothering me for a while now.

 

What I can clearly see is that with Phase being in TickEvent, you don't have to write Pre and Post sub-events for every sub-event of TickEvent.

On the other hand TickEvents are being used with specific Phase in probably 90%+ of cases, so every time we have to do that phase check instead of doing e.g: PlayerTickEvent.Pre.

 

So, aside from people being used to doing it (or even worse - not knowing about phases at all) and the fact that code will have few more mini-inner-classes, why don't we make it more "polymorphic"?

[LexManos]

Because thats how cpw decided to write it back in the day.