- Import `Commands.literal`
- Use more readable syntax for Brigadier command
- Use `DyeColor` directly instead of toString -> fromString everywhere
- Also updates `WoolTool` to use the new `HopperCounter` getter that supports it
- Split `resetCounter` in two, one for single and one for all
Also: HopperCounter now uses `.overworld()` and its `//OW` comments are removed
* Small cleanup to `/player` command
There should be no changes to users
* Use extracted `source` variable
* Inline another single-use small function
* Inline another trivial helper
* Import inner classes of the ActionPack
* Rename `literalargumentbuilder` variable
* Compact unnecessary three lines into one
* Inline `source.getServer` and pass `Vec3` to `createFake`
This gets outside of "just" the command, but it's fine
* Unpick name length constant
* Pass `Vec3` directly to `BlockPos.containing`
* shadow-single-player-owner-fix:
* Disallow shadowing a single player server owner. Fixes#1442
* shadow-single-player-owner-fix:
* Remove some redundant calls
* Settings rework and encapsulation
* Settings overhaul 3
Move everything in the new system to a new API package
Require rules using the new system to specify descriptions in their translation files
Implement temporary system on top of current translations to allow that to work properly
* Fix getRules fallback
* Final touches to settings refactor
* Mention that set shouldn't throw and remove comment
* Change translation keys to unify with translation PR
* Deprecate printAllRulesToLog to allow using any PrintStream
* Remove restriction of CarpetRules being Comparable
And fix overreaction in a deprecation message
* Bring back user input to rule observers
* Make Validator deprecation warning not spam on use
* Remove unneeded abstract methods in CarpetRule already inherited from CarpetRule
They literally do nothing, don't even force them to be implemented, and may be confusing as to why they're there or as if they are needed to be implemented
* Fix legacy SettingsManager field not being assigned correctly
* Finish fixing conflicts from future merge
* Actually fix remaining conflicts from future merge (missing imports)
* Import the newer rule in SettingsManager
* Refactor Validators
* Don't spam deprecation warnings on custom managers
* Get out the var
* Fix missing warning in old rule observers
* Update src/main/java/carpet/api/settings/Rule.java
* Remove `@ApiStatus.Experimental` annotations
* Fix incorrect `@deprecated` javadoc tags
By removing them given the class is deprecated anyway and else there's too much noise
* Add missing static import
* Remove TypedField and use a regular field
I liked that class tbh, but it's true that it wasn't really needed
* Move `field` assignment out of for removal
* Fix not following contract of `type()` returning boxed value
Previously handled by TypedField
* Fix few incorrect translation keys
* Remove resaving of comments when saving config files
Comments ignoring is still a thing when reading, so `locked` configs for example will keep comments
* Condense rule load messages in one
* Only print loaded settings message when at least one setting was changed
* Fix legacy validator detector
* Tweak and add more context to response to invalid values
* Fix strict validator not actually erroring on invalid input
* Fix more warnings and do some small optimizations
* Fix more warnings in ValueConversions
* Clean up some decompiler names and fix an unnecessary transformation around commands
* Use (way) more compact data structure for slot map
* Minor tweaks
Such as map directly in the collector
* I hate vanilla javac
Revert map changes in latest commit
* Remove no longer needed language packet mixin
* Make StringArgument properly return a StringArgument supplier, so `string` isn't `term`
Fixesgnembon/fabric-carpet#1044
* Complete removal of `/info entity` and it's correspondent carpet
Resolvesgnembon/fabric-carpet#1033
* Remove yet another no longer needed mixin
The current implementation only allows toggling tick freeze, so scripting is hard. This patch enables users to specifically freeze or unfreeze other than just toggling. It also provides '/tick freeze status' command to dynamically check whether the game is frozen or not.
This patch preserves compatibility to the existing '/tick freeze' toggle command.
This enables administrators to flexibly spawn players in game modes other than their current modes, and also allows administrators to spawn non-creative players from the console or rcon.
Usage: /player spawn bot in <gamemode>
Usage: /player spawn bot at ~ ~ ~ face 0 0 in minecraft:overworld in <gamemode>
Permissions required: OP Level 2 and above.
Note on flying: For spectator players, flying is always enabled. For other game modes, whether they are flying depends on the command caller. Therefore, it is possible to spawn a flying survival player when you are currently flying.
gnembon