Read detailed change logs in https://github.com/sakurawald/fuji/commits/dev/
Changelog
- [core] feature: add
--silentand--stdoutoptional arguments for all fuji commands. (#266)- feature: add
--silentoptional argument, tocancel the text sendingduring thiscommand execution. - feature: add
--stdoutoptional argument, tolog the text sending into the consoleduring thiscommand execution. - examples:
/fly --silent true/fly --silent true --stdout true/run as console --silent true fly others @r --silent false
- feature: add
Read detailed change logs in https://github.com/sakurawald/fuji/commits/dev/
Changelog
In this version, the command system undergoes a full code review, and many legacy bugs are fixed.
Besides that, a new permission.json file is introduced, to support the permission configuration, without the LuckPerms mod. (See below)
Core
- Feature: Improved property naming when inspecting argument types in the Inspector GUI.
- Feature: Added
permission.jsonfile to configure the default permission level for each Fuji command.- Before: Default permission levels were hard-coded.
- Now: Permission levels are stored in
permission.json, which can be edited and reloaded with/reload. - Especially useful in single-player worlds without the LuckPerms mod.
- Feature: Inspector now displays the documentation string for
config handlerobjects. - Fix: When installed client-side, the
CleanTTLMapJobis now correctly re-registered after rejoining a single-player world.
Back
- Fix:
/back {push|clear}command suggestions are no longer shown if the player lacks permission to use them.
Command Permission
- Fix:
/reloadnow immediately wraps newly registered commands in thecommand_permissionmodule, ensuring the client command tree updates properly.- Previously, lazy wrapping delayed this process until a command was used, causing potential client-side command tree desync. (After the
/reloadcommand, the users need to re-join the server, to re-fresh the client-side command tree)
- Previously, lazy wrapping delayed this process until a command was used, causing potential client-side command tree desync. (After the
Command Bundle
- Fix: User-defined variable values are now injected correctly even if other variables share a common name prefix.



