Skip to content
This repository has been archived by the owner on Aug 26, 2023. It is now read-only.

Packets instead of events for checking #2

Open
MyPictures opened this issue Sep 17, 2013 · 4 comments
Open

Packets instead of events for checking #2

MyPictures opened this issue Sep 17, 2013 · 4 comments
Labels

Comments

@MyPictures
Copy link
Member

I know this is an old subject and we probably will use events instead but maybe there are still some interests in this so fell free to comment and discuss :)

@asofold
Copy link
Member

asofold commented Sep 18, 2013

Likely not "instead", since our main context is Bukkit API, strongly tied to CraftBukkit. Future contexts also rather seem to be "use as plugin".

However it should be possible/interesting to:

  • add integration for packet APIs.
  • add our own thin/light-weight packet abstraction layer to allow packet checks that don't depend on a particular packet-API below (ProtocolLib, BKCommonLib, custom, ...) - read as data source providers / listener-registries.
  • add checks for some packets / things that only can be done with packet listening.

@MyPictures
Copy link
Member Author

Sounds good. Keep_Alive would be a really nice one to listen to.

@SuperSpyTX
Copy link
Member

We should check if ProtocolLib is loaded, then if so, be able to extend or add new checks via ProtocolLib's packet listeners.

@asofold
Copy link
Member

asofold commented Sep 20, 2013

Of course components only load if the dependencies are there ... question might be if to use some abstraction thing, to be able to use packets on different Systems.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants