whimxiqal / nope Goto Github PK

Requests to change data are distributed across some threads but are not synchronized, so the plugin is not yet thread safe. This must be remedied.

Everything in the sponge subdirectory needs to be fixed to sponge's API 8. The most complicated tasks will be converting the command structure and the event listeners.

The following must also be satisfied:

• The "common" subdirectory has no mention of sponge or Minecraft-related functionality for a complete split of behavior and purpose
• other requirements TBD

All work to be done in #1.

This is probably because SpongeForge does not implement LoadedGameEvent correctly, but the lifecycle handling can be done better in Nope anyway.

There really is no reason why a zone can only have one parent. When evaluating values for a point, every encapsulating zone will look up all its parents and add them to the priority queue by order of priority.

This will allow for more advanced inheritance.

Nope is becoming a project that is unwieldy to use directly in game because, although it is powerful and can perform for a wide variety of use cases, a firm understanding of its internal structure. So, it seems that it might become much more useful as an engine that runs external plugins like:

• Towns plugin ("Outpost")
• Prison plugin ("Stockade")

So, to support such endeavors, we need an API that basically does everything that the command structure does. So, we need to pull the behavior out from

command -> HostSystem

to

command -> host API -> HostSystem.

I'm a relatively new developer and certainly a novice when it comes to Gradle and publishing artifacts to Maven repositories. I would greatly appreciate anyone looking over my Gradle files and verifying that the processes I have set up are correct.

I'm going to forgo the GitHub template here because I think this is a pretty straightforward request:
I'd like to be able to see programmatically when someone enters or leaves a zone. My particular usecase is an administrative client mod that tells you which zones you're currently in on the F3 debug screen, though I admittedly have a hard time thinking of other uses that wouldn't be more appropriate as settings.

Right now, I can listen to the movement event myself and check if the zones are different (which is what Nope does for entry and exit checks already) but if Nope is already doing that, it'd be convenient to just fire the event at that time. I don't think it's necessary to make those events cancelable but maybe another developer will have a use for that?

Thanks!

New features coming out:

• Inheritance, achieved through Profiles. You may apply zero, one, or many Profiles to any Host.
• Much more developed API, including custom events and editors of Hosts
• Unit testing
• Nomenclature transition Zone -> Scene, Volume -> Zone
• Improved parallelism (not going to work on this)

Possibly more to come. PR and branch pending.