Skip to content
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

api/2.4.1 - Cloud for commands, ping command, more api #4862

Merged
merged 9 commits into from
Aug 1, 2024
Merged

Conversation

onebeastchris
Copy link
Member

@onebeastchris onebeastchris commented Jul 14, 2024

These are the changes to be released in version 2.4.1 of the Geyser API. Alongside them, the Geyser version will follow a new versioning scheme to properly reflect changes in the API, as well as indicate that a new Minecraft version is supported. More details on that soon!

API Changes included so far:

  • Cloud - features a full rework of the command system within Geyser, and adds permission checking to the Geyser API
  • Ping command - Adds a /geyser ping command to Geyser, and exposes a player's ping in the api
  • Hand switching api - Adds a simple method to request an offhand swap in the api, so extensions could replace the "emotes-and-offhand" workaround

Other PRs included:

  • Extension API version checking - Ensures that extensions properly specify the Geyser API version, instead of the Base API version. This will require extensions to update their api version in their extension.yml, however existing extensions will continue to work.
  • Base API changes to add an ApiVersion - Adds api version compatibility checking directly to the Base & Geyser API

Konicai and others added 3 commits July 11, 2024 23:56
Co-authored-by: onebeastchris <github@onechris.mozmail.com>
* Init: Add /geyser ping command

* Block just console execution, not everything but console senders

* Use RTT as that seems to vary less wildly compared to getPing()

* Cleanup, use lang strings

* Add ping() method to GeyserConnection in api

* Update to cloud changes
@onebeastchris onebeastchris added the API The issue/feature request relates to the Geyser API label Jul 14, 2024
@Konicai
Copy link
Member

Konicai commented Jul 14, 2024

To whoever merges this: remember to not squash

@onebeastchris onebeastchris added Work in Progress The issue is currently being worked on. PR: Feature When a PR implements a new feature labels Jul 14, 2024
@letsgoawaydev
Copy link
Contributor

is #4205 going to be in 2.4.1 or in a later api update?

@onebeastchris
Copy link
Member Author

Likely a later one; given that it adds a config value it likely makes more sense to wait until we move to configurate as that will update existing configs.

@onebeastchris
Copy link
Member Author

Once we merge this, GeyserMC/GeyserWiki#217 and GeyserMC/GeyserDiscordBot#299 should also be

onebeastchris and others added 4 commits July 23, 2024 14:29
* Update DeviceOs to latest protocol
* Revert enum name change and add deprecation annotations
)

* let extensions specify geyser api version instead of base api version

* fix spacing, @link formatting, properly check for compat

* Proper warning, update to API changes to also check patch version

* Bump base-api version

* adapt to new base api changes

* Actually bump to 2.4.1

* Update api/src/main/java/org/geysermc/geyser/api/extension/ExtensionDescription.java

* Address reviews

* Address reviews

* Update to latest base api changes; proper extension *human* version checking

* no need to apply a plugin, that's the default

---------

Co-authored-by: Konicai <71294714+Konicai@users.noreply.github.com>
@onebeastchris onebeastchris marked this pull request as ready for review July 31, 2024 22:12
@onebeastchris onebeastchris removed the Work in Progress The issue is currently being worked on. label Jul 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API The issue/feature request relates to the Geyser API PR: Feature When a PR implements a new feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants