-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Easier Event System #2
Comments
Maybe there's a way to translate events like this, but I can't see a way to do it in general unfortunately, since the Bukkit and Sponge events are so different best I can do I believe is implementing each one individually.. but maybe something better is possible? |
Also, Bukkit afaik won't call the event superclass handlers (including |
@Minecrell did dome cool stuff in https://github.com/LapisBlue/Pore that might help, related to events. |
@jamierocks They're doing the same thing that Bukkit2Sponge is doing (LapisBlue/Pore@687e7e2). |
Instead of implementing every Event in Sponge and transfering it to Bukkit (or vice versa), is there any way you could call the event based on the Bukkit event?
Obvisouly that doesn't work, but there's probably some way to add a
switch
for each Event. Plus I don't know if a normal Event will be called.Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: