Future of this fork

[mdcfe]

It's probably worth rebranding this fork (vChat?) to reduce confusion with upstream gChat, especially considering the API breaks, as well as Velocity-specific features in #3.

Alternatively we could refactor the plugin into a cross-platform plugin for both Bungee and Velocity. @lucko would you be interested if I did this and PRed to gChat upstream, or would you prefer to keep gChat as-is?

edit: if not, I'll probably just rename this fork so people don't get confused.

[lucko]

Yep, sounds good to me!

I can make you a collaborator on that repo if you like?

[mdcfe]

Sure, sounds good. I won't be around for the next two weeks, but after that I'll be around to work on it. Just a couple of considerations:

• Do we want to implement plugin-specific hooks within gChat itself? (eg. Neutron integration for ignores and nicknames #3)
• Should we produce a single universal jar?

[lucko]

• Sure, why not
• I don't mind, but I guess a single jar is easier?