Temporary patch to 'Unsupported event'

[diamondburned]

Unsupported events are now silenced. Fixes #421.

When #319 is merged, all events will be logged fully again.

[a-urth]

@diamondburned thats not exactly what i meant, sorry for misunderstanding.
So commenting handling unknown events is definitely not what we need.
I'm not sure whether we need those 2 events at all or they can be just log messages. First can be clarified with @iwasaki-kenta and @claudiucelfilip

But how do you think much time it will take to add ws support (parsing mainly) for those two events? Thats in case we actually need them to be send over ws. Otherwise i guess it can be changed to logging pretty fast, right?

[diamondburned]

@diamondburned thats not exactly what i meant, sorry for misunderstanding.
So commenting handling unknown events is definitely not what we need.
I'm not sure whether we need those 2 events at all or they can be just log messages. First can be clarified with @iwasaki-kenta and @claudiucelfilip

But how do you think much time it will take to add ws support (parsing mainly) for those two events? Thats in case we actually need them to be send over ws. Otherwise i guess it can be changed to logging pretty fast, right?

Changing to logging is simple, it's just changing log.Event() to log.Node(). However, the current logging structure is ideally done over WS, so it should either be an actual event, or it should be a debugging event (which doesn't go over WS afaik).

That said, if these 2 events are needed over WS, I could do that.

[a-urth]

@diamondburned so those events are both used in frontend, so we need to support them.

[diamondburned]

@diamondburned so those events are both used in frontend, so we need to support them.

It's added now.

[a-urth]

remove this new line please

[a-urth]

@diamondburned and merge master to this branch