CreativeGates3

This is the official release of version 3.4.3 of CreativeGates. Be sure to also download the new MassiveCore from the GitHub release! IMPORTANT: Pay special attention to the changes to permissions! Here is a list of updates included in this version: New Features: · 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.setgatefill permission (granted by default with creativegates.*). · The list is configured through the settings allowedGateTypes and allowedHorizontalGateTypes. · For new servers, the list of default blocks will be set to: · NETHER_PORTAL · END_GATEWAY · WATER · LAVA · POWDER_SNOW · ICE · SCULK_VEIN · SCULK · For existing servers, your list will only include NETHER_PORTAL (or WATER if previously configured). You may add any additional blocks. · This is configurable through /cg config or 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 useLavaInNether setting has been renamed to replaceWaterWithLavaInNether. This allows you to set WATER as a supported gate type, and have that be replaced with LAVA in the Nether only (in case you didn't want LAVA to be selectable in the overworld but also don't want WATER selectable in the Nether). · While highly unlikely this would occur, we now prevent drowning in WATER gates. · 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 use LAVA, it will be brighter than other block types. · 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.setfillparticlecount permission (granted by default with creativegates.*), 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 allowedGateParticleTypes and allowedHorizontalGateParticleTypes. · The minimum, maximum, and default amount of particles can be configured through the settings gateFillParticleAmountMin, gateFillParticleAmountMax, gateFillParticleAmountDefault. · 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 permission creativegates.cg.inspect. Granted by default with creativegates.*. · 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 perm or /f flag commands 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 permission creativegates.cg.manage. Granted by default with creativegates.*. · 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 manage or /f perm manage commands). · 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 permission creativegates.cg.inspect. Granted by default with creativegates.*. · 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 permission creativegates.cg.override. Granted by default with creativegates.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.bypass allows players to manage any gate without enabling override mode. This permission must be explicitly granted and is not inherited by any wildcard permissions. · Some permissions that were previously granted with creativegates. have been moved to creativegates.admin.. The full list includes: · creativegates.* (the admin permission grants all the "non-admin" permissions as well) · creativegates.cg.override · creativegates.cg.config · creativegates.cg.world · creativegates.cg.world.list · creativegates.cg.world.delete · Added a new permission creativegates.create.bypassframe which 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).