Repository navigation
Overview
This release adds some new features, bug fixes, and official support for Minecraft 26.3.
Features were more focused on CreativeGates in this release, but a few changes for the other plugins were made.
IMPORTANT: For CreativeGates users - please take note of the changes to permissions detailed in the release notes below.
Changes/Features
MassiveCore
- Added support for the new Dialogs API (both Spigot and Paper). This can (and is!) now be used by the other MassiveCraft plugins to provide Dialog UI. See the CreativeGates release notes for the first implementation of Dialogs.
- Improved the built-in ChestGui API for displaying chest-based GUIs to users. We weren't using this anywhere (until now). See the CreativeGates release notes for the first implementation of chest-based GUIs.
- Removed a deprecated event registration (was not in use) - this prevents a warning from displaying at startup on 26.3 though since it was finally removed from the server API.
Factions
- Minecraft 26.3 support has been added.
- Protection for Cushions has been added (both placement/use) - there is a new perm for this. You can configure this with
/f permjust like other perms. - Additional new blocks added (mainly poplar blocks/items) also have had support added.
- Protection for Cushions has been added (both placement/use) - there is a new perm for this. You can configure this with
- The
/f flagand/f permcommands now list flags/perms in alphabetical order.
FactionsChat
- Implemented Unit Testing for better coverage and regression prevention
- [BUG]: Fixed an issue where URL parsing was not working in some scenarios (some URLs would not be displayed as clickable links even though they were valid URLs)
- [BUG]: Fixed an issue on Spigot where URLs were never clickable - they are now clickable/underlined based on the config.
- [BUG]: Fixed an issue on Paper where due to the upgraded version of the Adventure library, some errors would be encountered on 26.2 and 26.3. Adventure 5 (newest Adventure version) is now supported by FactionsChat.
- [BUG]: Fixed an issue with the DiscordSRV Integration where chat (in Minecraft) would not always be displayed in Discord (affected both Spigot and Paper, but different for each).
CreativeGates
- Added support for ALL blocks to be used as gate fill blocks. This can now be set on a per-gate basis. When a gate is being created, players will be prompted to select the gate fill block to use. The list of blocks that can be used can be configured on the server, then players can select one of those as their fill block.
- Players must have the new
creativgates.setgatefillpermission (granted by default withcreativegates.*). - The list is configured through the settings
allowedGateTypesandallowedHorizontalGateTypes - For new servers, the list of default blocks will be set to the following:
NETHER_PORTALEND_GATEWAYWATERLAVAPOWDER_SNOWICESCULK_VEINSCULK
- For existing servers, your list will only include
NETHER_PORTAL(orWATERif you had it set to use water previously). You can add the above blocks if you would like to, but you can also add any other blocks to the list. - This is configurable through
/cg configor by modifying the config file. - Horizontal Gates now support nether portal blocks! Note that there are some minor animation glitches with this that can occur (as Minecraft never intended to display nether portals in that orientation).
- The
useLavaInNethersetting has been renamed toreplaceWaterWithLavaInNether. This allows you to setWATERas a supported gate type, and have that be replaced withLAVAin the Nether only (in case you didn't wantLAVAto be selectable in the overworld but also don't wantWATERselectable in the Nether). - While highly unlikely this would occur, we now prevent drowning in
WATERgates. - CreativeGates now emit light (same light level as vanilla Nether Portals) - with one exception... if you use
WATER, it will not be lit, and if you useLAVA, it will be brighter than other block types.
- Players must have the new
- Added support for using Particles as the fill for gates instead of blocks. A large list of particles will be enabled by default, but you can modify that list (add/delete) using any valid Particle name.
- If the player has the new
creativegates.setfillparticlecountpermission (granted by default withcreativegates.*), players will also be able to set the amount of particles the gate spawns in the fill area (min/default/max are configurable at the server level). - The list of available particle types can be configured through the settings
allowedGateParticleTypesandallowedHorizontalGateParticleTypes. - The minimum, maximum, and default amount of particles can be configured through the settings
gateFillParticleAmountMin,gateFillParticleAmountMax,gateFillParticleAmountDefault
- If the player has the new
- Revamped the gate creation flow to now use Dialogs (on supported Minecraft versions) - on older versions, it will use a Chest-based GUI instead
- When creating a new gate, players will be prompted to select the gate fill block (or particle), using a dialog user interface (custom clickable menu system).
- Added a new command
/cg inspect- this does the same thing as the Inspect tool (Blaze Powder by default). This (and the tool) is now tied to the permissioncreativegates.cg.inspect. Granted by default withcreativegates.*.- To use this command, simply look at a gate/gate frame and run the command.
- On this note, the information displayed is now enhanced and will now be displayed in a paginated view similar to the
/f permor/f flagcommands for instance. Information included on inspect includes:- The gate owner
- The gate network name
- The number of gates in said network
- The various gate settings, such as secret status, entry/exit mode, types of entities that can use the gate (see below for more details)
- Added a new command
/cg manage- this does the same thing as the gate Manage tool (previously known as the "mode" tool - defaults to Blaze Rod). This (and the tool) is now tied to the permissioncreativegates.cg.manage. Granted by default withcreativegates.*.- To use this command, simply look at a gate/gate frame and run the command.
- This command (or tool) will now open a Dialog (on supported Minecraft versions) - on older versions it will use a chat-based interface instead (similar to the
/f flag manageor/f perm managecommands). - This didn't change but - users can only manage gates they own (unless in admin override mode - see below)
- The UI will present options for changing gate settings including:
- Secret status
- Entry/Exit Modes
- Types of entities that can use the gate
- If the player has permission, the gate fill blocks/particles
- Because the manage command/tool now can modify secret status and the inspect command/tool now displays the secret status, the separate tool for setting the secret status (which defaulted to Magma Cream) has been removed. We now have an inspect tool and a manage tool, that's it.
- Added support for enabling/disabling specific entities from using CreativeGates (controlled on a per-gate basis). The list of currently supported options includes:
- Players
- Mobs (yes, mobs can now go through CreativeGates!)
- Vehicles (boats, minecarts)
- Added a new command
/cg tool- this toggles the ability to use the manage/inspect tools on and off. If disabled, right clicking with these tools on gates would not work until re-enabled. This command is tied to the permissioncreativegates.cg.inspect. Granted by default withcreativegates.*. - Added a new command
/cg override- this toggles Admin Override mode, allowing administrators the ability to manage any other player's gates. This works very similar to Factions Override mode (same concept/idea). This command is tied to the permissioncreativegates.cg.override. Granted by default withcreativegates.admin.*(new admin-specific wildcard).- While in override mode, players will ignore most restrictions, including:
- They will be able to manage gates they do not own.
- They will be able to bypass frame restrictions (requiring specific blocks in the frame)
- They will be able to create gates in worlds that are currently disabled for regular users
- A permission
creativegates.cg.override.bypassallows players to manage any gate without enabling override mode. This permission must be explicitly granted and is not inherited by any wildcard permissions.
- While in override mode, players will ignore most restrictions, including:
- Some permissions that were previously granted with
creativegates.*have been moved tocreativegates.admin.*. The full list includes:creativegates.*(the admin permission grants all the "non-admin" permissions as well)creativegates.cg.overridecreativegates.cg.configcreativegates.cg.worldcreativegates.cg.world.listcreativegates.cg.world.delete
- Added a new permission
creativegates.create.bypassframewhich allows - [BUG]: Fixed an issue where the gate creation disabled worlds list was not be checked (so if you disabled gate creation in a world it would not be honored).
Check out the Wiki for updated documentation that includes all the new features!
Thanks to those who have reported issues and continue to support my plugins! Please continue to file issues or reach out to me if you experience problems!