v3.4.0 ALPHA-11

Overview

This alpha release adds official support for Minecraft 1.21.11. Some small bug fixes and quality of life features have also been added.
This release also now includes builds of MassiveBooks and MassiveHat, updated to support the latest versions of Minecraft! Tested on versions 1.21.4 - 1.21.11.

Changes/Features

General

• All plugins have been tested on Minecraft 1.21.11.
• Additional work has been done on the wiki website. I will continue to update this and work on it with time. You can check it out here: https://factions.wiki

MassiveCore

• There were some breaking changes with the latest version of Paper to Gson, one of the libraries used throughout the MassiveCraft plugins. Some refactoring was done to resolve this. This has increased the size of the MassiveCore file. You will need this new version of MassiveCore! Please be sure to install it with the new versions of Factions and any other MassiveCraft plugins you are using. (As a rule of thumb, it is best to always use the latest version of MassiveCore with the latest versions of the MassiveCraft plugins.)
• Updates were made to support MassiveBooks and MassiveHat.
• Some changes have been made to the internals of MassiveCore. Nothing that should affect players, but please continue to report any issues or bugs found on the Issues page.
  • For anyone interested in technical details, I have been working on removing unnecessary NMS usage from MassiveCore. I will continue to work on this as time permits.

Factions

• Added support for new MC 1.21.11 mobs
• Some changes have been made to the internals of Factions. Nothing that should affect players, but please continue to report any issues or bugs found on the Issues page.
  • For anyone interested in technical details, I have been working on removing unnecessary NMS usage from Factions. I will continue to work on this as time permits.

MassiveBooks

• This marks the official release of MassiveBooks, ported to modern Minecraft. This is a plugin that aims to add features to books, including better displaynames, copying books, unlocking locked books for more editing, and more!
• I have not yet added documentation for this plugin to the wiki, but I will try to get that added ASAP. In the meantime, check out the legacy docs on archive.org:
  • Player Docs
  • Server Owner Docs
• As this is the first official modern release of MassiveBooks and we don't have any servers using it yet, there may be bugs. If you would like to be an alpha tester for us, please reach out! Please also continue to report any issues or bugs found on the Issues page.

MassiveHat

• This marks the official release of MassiveHat, ported to modern Minecraft. This is a very simple plugin for using any item as a hat.
• I have not yet added documentation for this plugin to the wiki, but I will try to get that added ASAP. In the meantime, check out the legacy docs on archive.org:
  • Player Docs
  • Server Owner Docs
• As this is the first official modern release of MassiveHat and we don't have any servers using it yet, there may be bugs. If you would like to be an alpha tester for us, please reach out! Please also continue to report any issues or bugs found on the Issues page.

Known Issues

MassiveCore

• Starting with Paper 1.21.7, a warning will be displayed in the console upon player login about usage of PlayerLoginEvent. Paper has decided to deprecate this in favor of a new protocol. We are aware of this and will be implementing the new protocol into MassiveCore in a future build. Note that this does not apply to servers running Spigot.

MassiveBooks

• There is an issue with Paper where stacked books can in some cases be stacked to the incorrect stack size. This is a Paper bug and is not a bug with MassiveBooks. As such, this issue does not occur on Spigot servers. We will keep you updated on when a fix has been released for Paper. Check back on these release notes (I will update the notes when we see a fix has been made).

---

IMPORTANT DISCLAIMER

This is an alpha release. We recommend exercising caution if considering running this in a production environment. Please test this in a test server before even considering deploying to your main production server! Also remember that bugs may exist - please file them in the Issues tab if you find them!

Thanks to those who have reported issues and continue to test these alpha builds!

---

v3.4.0 ALPHA-10

Overview

This alpha release adds official support for Minecraft 1.21.10. Some small bug fixes and quality of life features have also been added.
No changes were made to CreativeGates in this version from the previous alpha build, however, a build is still provided.

Changes/Features

General

• All plugins have been tested on Minecraft 1.21.10. There were no actual changes needed to support this version from 1.21.9, but it has now been tested.
• Logos in the repo have been updated with new logos used in the Wiki.
• Additional work has been done on the wiki website. I will continue to update this and work on it with time. You can check it out here: https://factions.wiki

Factions

• Additional placeholders have been added to the PlaceholderAPI integration. The list of supported placeholders is now quite extensive. Check out the complete list on the wiki
• A new config option foundedDateFormat has been added - this sets the date format that displays when displaying the founded date of a faction. It defaults to yyyy-MM-dd. This is currently used only with the new founded date placeholder. This follows the Java SimpleDateFormat standards, which you can find here: https://docs.oracle.com/en/java/javase/21/docs/api/java.base/java/text/SimpleDateFormat.html
• It was discovered that Factions was hard-coded so that neutral players could not be damaged in their own territory. This was being exploited to give neutral factions an unfair advantage (treating them more like friendly factions). A new enablePVPAgainstNeutralInTheirTerritory config setting has been added. It defaults to true, to treat neutral players more like enemies (they will be able to be hurt in their own territory). This is a change to default functionality. Admins can set this new setting to false if the old functionality is preferred, and neutral players will no longer be able to be hurt like before.
• A bug with faction enemy/ally relationships has been fixed. This was an issue where in certain cases, an enemy faction could become allies with a faction without said faction's approval. This could happen infinitely, which allowed for faction relationship exploits (enemy the faction, raid their land, ally them), and the other faction would not know how it occurred as they are not notified of the relationship status changes. It looks like this bug has existed for a long time but required a specific setup to replicate. This exploit is no longer possible so now when enemying a faction, both factions must approve to become allies.
• Enderpearl exploit prevention has been further improved. Specifically, the handleExploitEnderPearlClipping setting was not handling doors, trapdoors, or fence gates. There were several ways discovered that you could clip through any type of "door" with enderpearls. This update accounts for these scenarios and further improves this exploit prevention.
• The Compatibility Layer with legacy factions plugins has been updated to account for recent changes to other Factions plugins. Please remember that this compatibility layer is not officially supported and is largely untested. Please encourage plugin developers to implement true MCore Factions support.

FactionsChat

Several new commands and features have been added, as well as a few bug fixes. The wiki has been updated with these new features, so check it out if you want to see full details about any of these:

• A new /f c help command has been added to allow players to get help with the various FactionsChat commands/features they can access.
• A new /f c toggle command has been added to allow players to toggle (enable/disable) specific chat modes (channels). A corresponding permission node has also been added (factions.chat.toggle), as well as an admin permission node (factions.chat.toggle.admin).
• A new /f c ignore command has been added to allow players to ignore other players. A corresponding permission node has also been added (factions.chat.ignore), as well as an admin permission node (factions.chat.ignore.admin).
  • It should be noted that the new permission node added for this command also provides access to the unignore command, and the ignorelist command. See below.
• A new /f c unignore command has been added to allow players to unignore other players. The permission node added for the ignore command also gives access to the unignore command.
• A new /f c ignorelist command has been added to allow players to see what other players they are currently ignoring. The permission node added for the ignore command also gives access to the ignorelist command.
• A new permission factions.chat.ignore.bypass has been added which allows a player to bypass the ignore list of other players (if you want admins to never be able to be ignored for instance - granting this permission to said admins will prevent regular players from ignoring those admin players).
• Some changes were made to the internals of FactionsChat to improve the /f c reload command. This is not user-facing, but is just being noted in case you see any issues with that command to reload config changes.
• Some changes were made to the internals of FactionsChat to improve updates to the config.yml file. Anytime updates are made upon new version upgrades, we will make a backup of the old file before updating to the new file. Old settings will also be retained upon update. There should be no issues with this change, but this is being noted in case you do see any issues with the config file.
• Fixing a file access race condition bug that can occur when loading the plugin for the first time.

MassiveCore

• A small update to MassiveCore was made that updates the website link on the /massivecore version command.

Known Issues

MassiveCore

• Starting with Paper 1.21.7, a warning will be displayed in the console upon player login about usage of PlayerLoginEvent. Paper has decided to deprecate this in favor of a new protocol. We are aware of this and will be implementing the new protocol into MassiveCore in a future build. Note that this does not apply to servers running Spigot.

---

IMPORTANT DISCLAIMER

This is an alpha release. We recommend exercising caution if considering running this in a production environment. Please test this in a test server before even considering deploying to your main production server! Also remember that bugs may exist - please file them in the Issues tab if you find them!

Thanks to those who have reported issues and continue to test these alpha builds!

---

v3.4.0 ALPHA-9

Overview

This alpha release adds official support for Minecraft 1.21.9. Some small bugs and quality of life features have also been added.
No changes were made to CreativeGates or FactionsChat in this version from the previous alpha build, however, a build is still provided.

Changes/Features

General

All plugins have been tested on Minecraft 1.21.9. Some updates were made to Factions to support the new Minecraft features, but the other plugins should continue working and did not require any updates.

Additionally, work has been done on the wiki documentation. Primarily of Factions. It is still under construction, but you can check it out here: https://factions.wiki

Factions

• Spigot/Paper 1.21.9 support has been officially added. All new block types and entities should be properly protected in faction land. Please file an issue if you experience any problems. The main noticeable new blocks that are now protected include:
  • Copper Doors (all oxidized and waxed variants)
  • Copper Trapdoors (all oxidized and waxed variants)
  • Copper Chests (all oxidized and waxed variants)
• Improved pressure plate protection:
  • Triggering of pressure plates via dropped items is now properly protected in faction land.
  • Triggering of pressure plates via tamed animals (i.e. wolves, cats, etc.) is now properly protected in faction land
  • Triggering of pressure plates while riding another entity (i.e. pigs, horses, etc.) is now properly protected in faction land
  • Triggering of pressure plates via leashed mobs is now properly protected in faction land
  • Triggering of pressure plates via projectiles (i.e. arrows, etc.) is now properly protected in faction land
  • Reduced "cannot use" message spam that could occur in some cases.
• Improved button protection:
  • Triggering of buttons via projectiles (i.e. arrows, etc.) is now properly protected in faction land.
• Improved armor stand protection:
  • Adding/removing of armor pieces is now properly protected in faction land (before only destruction of the armor stand was being protected)
• Adding wind charge protection support:
  • Blocks that can be triggered via wind charges (i.e. doors, buttons, etc.) are now properly protected in faction land.
    • This uses the corresponding permission to determine if players are allowed to trigger those items via wind charges (for example, if a player cannot use buttons, but they can use doors, then they will not be able to trigger a button with a wind charge, but they could open a door with a wind charge).
  • Blocks that can be broken via wind charges are now properly protected in faction land.
    • This uses the "build" permission to determine if players are allowed to break these blocks.
  • Please note that combat-related usage of wind charges is not protected (players will be knocked back if a wind charge is thrown at them, and players can use wind charges to cause knockback on themselves, such as to jump high).
    • The only exception to this is if explosions are disabled in faction land entirely. Wind charges fall under the category of explosions and would be completely prevented at that point.
• Adding protection against a certain ender pearl block exploit.
  • The solution to this exploit was to add a short (default 1 second) cooldown to using ender pearls after breaking blocks. New configuration settings have been added for the duration of that cooldown as well as enabling/disabling of that exploit.
• Fixing bug with /f seechunk command where the particles that are spawned in the world are visible to all players. They should now be visible only to the player who activated the command.

Known Issues

MassiveCore

• Starting with Paper 1.21.7, a warning will be displayed in the console upon player login about usage of PlayerLoginEvent. Paper has decided to deprecate this in favor of a new protocol. We are aware of this and will be implementing the new protocol into MassiveCore in a future build. Note that this does not apply to servers running Spigot.

---

IMPORTANT DISCLAIMER

This is an alpha release. We recommend exercising caution if considering running this in a production environment. Please test this in a test server before even considering deploying to your main production server! Also remember that bugs may exist - please file them in the Issues tab if you find them!

Thanks to those who have reported issues and continue to test these alpha builds!

---

v3.4.0 ALPHA-8

Overview

This alpha release fixes some bugs and adds some small quality of life features.

Changes/Features

Factions

• The /f home, /f sethome, and /f unsethome commands (which previously existed but were hidden from tab-complete) are no longer hidden from tab-complete. These commands are aliases for the /f warp command to provide an easier way to interact with the home warp. They already existed, but they would not show up in the list of commands for players to use.
• Added an alias for /f unsethome called /f delhome (to match the original Factions command that some may be more familiar with).
• Adding missing mangrove doors, fence gates, and trapdoors to list of door types to protect in faction land. These were missed when we updated the door protection logic to protect all the new wood types from recent years.

CreativeGates

• Adding a new configuration option to disable gate creation on a per-world basis.
  • A new permission has been added to allow players to bypass disabled world gate creation (to enable specific players to still create gates in a world that in general does not allow this). The new permission is creativegates.create.bypassdisabled.
  • This new configuration does not prevent usage in those worlds, only creation. This allows for the scenario where an admin who has the bypass permission could create server gates which players can use, but players themselves cannot create their own gates in that world.
• Fixing bug with duplicate alias config values being put into the CreativeGates config file. This would occur on server shutdown, where the aliases would get added again to the file even though they already existed. It did not cause any issues with the plugin as far as we could tell, it just made the file messy.
  • After you update to this version, your config file will be cleaned up upon the next server shutdown (the duplicate values will be removed).
• Fixing bug with placement direction (where the gate would spawn with the portal blocks facing the wrong direction).

MassiveCore

• Implemented new methods into the InventoryUtil to support better handling of main-hand/off-hand item usage. Deprecated old methods. If any external plugins are using the old methods for interacting with player inventories (specifically related to looking at items being held by the player in their hands), it is recommended to switch to the new methods. The old methods will be removed in a future release which could cause breaking changes.

Known Issues

MassiveCore

• Starting with Paper 1.21.7, a warning will be displayed in the console upon player login about usage of PlayerLoginEvent. Paper has decided to deprecate this in favor of a new protocol. We are aware of this and will be implementing the new protocol into MassiveCore in a future build. Note that this does not apply to servers running Spigot.

---

IMPORTANT DISCLAIMER

This is an alpha release. We recommend exercising caution if considering running this in a production environment. Please test this in a test server before even considering deploying to your main production server! Also remember that bugs may exist - please file them in the Issues tab if you find them!

Thanks to those who have reported issues and continue to test these alpha builds!

---

v3.4.0 ALPHA-7

Overview

This alpha release fixes some bugs and adds some small quality of life features.

Changes/Features

General

• Significantly decreased plugin JAR size of all plugins by removing generated source code files from the final JARs. Source code for all JARs can still be obtained here on GitHub, as this project is open source.

Factions

• Changed the default particle for the /f seeChunk command (previously was using an explosion particle which was a bit of an eyesore - the new particle is much more pleasing)
• Added new configuration values for the /f seeChunk command - previously none of this was configurable
  • seeChunkParticle → The particle to use when displaying chunk borders
    • Valid values can be found HERE
  • seeChunkParticleSpeed → The speed at which the particle effect displays (this only effects some particles)
  • seeChunkParticleAmount → The amount of particles to spawn
• Removed the /f seeChunkOld command - this command had been considered deprecated for a long time and would lag the server when used.
• Fixed bug with vehicle destruction in faction land (i.e. boats/minecarts) where the check for faction protection was occurring based on the location the player was standing in, not the location of the boat/minecart.
• Added protection for placing vehicles (i.e. boats/minecarts) in faction land (this is tied to the same build permission that destroying boats/minecarts is tied to - based on community feedback of this change we could make this a separate permission in the future for placing/destroying vehicles if desired).

FactionsChat

• Tweaking config.yml
  • IMPORTANT NOTE: This update will replace your previous config.yml file. It is recommended you create a backup of your previous settings and copy those settings over after you install the updated version.
• Fixing bug with DiscordSRV Integration (it was broken using the latest version of DiscordSRV)

Known Issues

Factions

• The same known issue with Factions that was present in past releases with SlimeFun4 still exists in this version. We will no longer be mentioning this in future releases as we have done all we can - we submitted a fix for them, but they have yet to implement it. Please contact them with further questions, and refer to the following links:
  • Slimefun/dough#279
  • Slimefun/dough#280

MassiveCore

• Starting with Paper 1.21.7, a warning will be displayed in the console upon player login about usage of PlayerLoginEvent. Paper has decided to deprecate this in favor of a new protocol. We are aware of this and will be implementing the new protocol into MassiveCore in a future build. Note that this does not apply to servers running Spigot.

---

IMPORTANT DISCLAIMER

This is an alpha release. We recommend exercising caution if considering running this in a production environment. Please test this in a test server before even considering deploying to your main production server! Also remember that bugs may exist - please file them in the Issues tab if you find them!

---

v3.4.0 ALPHA-6

Overview

This alpha release fixes some bugs and adds some small quality of life features.

Changes/Features

General

• Updated and did general testing of all plugins under Minecraft 1.21.8. Some bugs may still be present and will be fixed in new alpha builds, but all versions from 1.21.4 to 1.21.8 can now be considered officially supported.

MassiveCore

• Added placeholder processor which allows support for conditional placeholder modifiers. Examples include "rp", "lp", "trim" - which add one space of right padding, one space of left padding, or trim the value of a placeholder respectively.
  • This feature is currently only used by Factions and FactionsChat. For a comprehensive list of all placeholder modifiers available, see the FactionsChat Wiki (will be available in the Factions wiki in the future as well).

Factions

• If plugins integrate using the Factions Compatibility Layer that adds basic support for legacy Factions, a warning will be displayed in the console that the integration is not fully supported. This is primarily for if the plugin has issues as the compatibility layer is not guaranteed to work and we encourage plugin developers to integrate using the MCore API.
• Prevent disbanding of the Wilderness faction
• Improved the /f perm show command
• Added aliases for the following commands:
  • /f l → /f list
  • /f sc → /f seeChunk
• Improved exploit engine to prevent exploiting ender pearls
• Improved land protection with the following updates:
  • Build protection now fully accounts for mounted players and projectiles
  • Lead protection no longer causes duplicate error messages in some scenarios and is now more efficient
  • Lecterns are now fully protected
  • Vehicles are now fully protected
  • Frost Walker enchantment will not place ice in land you cannot build in
  • Containers (chests, barrels, etc.) cannot be destroyed if you do not have permission
  • Added missing enum values for various blocks and entities that should be protected but were not.
    • Various redstone-related blocks that players can interact with (comparators, repeaters, etc)
    • Farmland
    • Cake
    • Glow Ink Sac
    • Campfire
    • Painting
    • Turtle Egg
• Improvement to territory change messages when moving across chunks to account for newline characters
• PlaceholderAPI Integration:
  • Improved handling of null values (scenarios such as the console)
  • Implemented the new MassiveCore Placeholder Processor to allow support for conditional modifiers in placeholders. The Factions wiki is still under construction and has not yet been updated with this information, however, the FactionsChat Wiki has.
• Fixed a few typos in a few commands

FactionsChat

• Updating config.yml with new structure and new defaults
  • NOTE: If you were previously using FactionsChat, it's recommended you delete your config.yml and run /f c reload to generate the default one (or restart your server). From there, reconfigure any values you may have previously configured.
• Changing permissions nodes from factionschat.* to factions.chat.*
• Adding permission nodes for color codes and formatting. The new nodes are:
  • factions.chat.color - allows a player to use legacy ampersand color codes in chat to modify chat colors
  • factions.chat.format - allows a player to use legacy ampersand format codes in chat to modify chat formats
  • factions.chat.magic - allows a player to use the legacy &k format code to turn on "magic" chat
  • factions.chat.rgb - allows a player to use ampersand hex codes in the format &#000000 to use rgb chat colors. Also supports three character hex codes &#000.
  • factions.chat.url - allows a player to paste urls into chat and have them be clickable in chat
• Improved performance by only saving the current player chat modes to disk on server shutdown rather than every time a player switched chat modes
• Implemented basic auto-config updater to add new config values when they are added to the default config.yml and are missing from the config.yml in your plugins directory. Future enhancements will be made to this in later releases.
• PlaceholderAPI Integration:
  • This integration did not actually work in the last release - it was not fully tested and was not working. It is now working and fully tested.
  • Improved handling of null values (scenarios such as the console)
  • Implemented the new MassiveCore Placeholder Processor to allow support for conditional modifiers in placeholders. See the FactionsChat Wiki for more details on how to use this feature.
  • Improved this integration to hook directly into the Factions PlaceholderAPI integration and just expand it with the chat-related functionality. Rather than implementing this as a separate PlaceholderAPI extension with a separate prefix, this allowed us to keep the factions prefix for factions_chat prefixes.
• Implemented the new MassiveCore Placeholder Processor in our internal placeholder logic to allow it to work the same as the PlaceholderAPI Integration to support conditional modifiers in placeholders. Again, see the FactionsChat Wiki for more details on how to use this feature.
• Improved both the Spigot and Paper chat listeners to be more efficient and to support both legacy and RGB color/format codes.
• Made Spigot and Paper behavior consistent so all messages are sent via the server for security and privacy

Known Issues

Factions

• The same known issue with Factions that was present in past releases with SlimeFun4 still exists in this version, where SlimeFun does not properly check for when admin override/bypass mode is enabled when checking if a user has permission to access SlimeFun-related blocks in protected land. This means that if you are trying to access blocks of another faction, it will not work, even if you are in admin override/bypass mode. I submitted a pull request to SlimeFun to fix the issue, so hopefully it is fixed in a future version of SlimeFun.

MassiveCore

• Starting with Paper 1.21.7, a warning will displayed in the console upon player login about usage of PlayerLoginEvent. Paper has decided to deprecate this in favor of a new protocol. We are aware of this and will be implementing the new protocol into MassiveCore in a future build.

---

IMPORTANT DISCLAIMER

This is an alpha release. I recommend exercising caution if considering running this in a production environment. Please test this in a test server before even considering deploying to your main production server! Also remember that bugs may exist - please file them in the Issues tab if you find them!

---

v3.4.0 ALPHA-5

Overview

This alpha release fixes some bugs and adds new features, primarily around Minecraft 1.21.7 support and chat/placeholder-related features. A few quality of life improvements have also been added around Faction permissions.

Features

General

• Updated and did general testing of all plugins under Minecraft 1.21.7. Some bugs may still be present and will be fixed in new alpha builds, but all versions from 1.21.4 to 1.21.7 can now be considered officially supported.

Factions

• Removed all chat functionality from Factions. This functionality has been integrated into FactionsChat instead.
  • This includes the VentureChat integration (which was untested and unknown if it even worked anymore)
• Adding permission to prevent pressure plate usage in factions.
  • This can be modified with the /f perm command. Example: /f perm show pressureplate, /f perm set pressureplate
• Improving button permission to support all button variants (not just stone buttons)
• Adding full support for lead attach/break events to support Minecraft 1.21.6+ lead changes. This includes a new lead permission.
  • This can be modified with the /f perm command. Example: /f perm show lead, /f perm set lead
  • Our previous support prior to 1.21.6 worked to prevent removing a lead from a mob attached to a fence post, but with the 1.21.6 changes, that was not enough to fully support removing leads.
• Config files will be automatically upgraded to add the pressure plates, buttons, and lead support.
• Adding support for Happy Ghasts for Minecraft 1.21.6+
• Fixing bug with custom color faction names (i.e. Wilderness) in Minecraft 1.21.6+ (error in console)
• Fixing bug with custom color faction names (i.e. Wilderness) when using click-commands (command hover suggestions)
• Fixing bug with /f perm show command when no ranks were granted permission
• Adding additional placeholders to PlaceholderAPI integration, including relational placeholders. The new list of supported placeholders has been greatly expanded. It should be noted that the old placeholder names still work - but going forward these are the ones we want people to use instead for clarity.
  • rel_factions_relation
  • rel_factions_relation_lowercase
  • rel_factions_relation_color
  • factions_faction_name
  • factions_faction_nameforce
  • factions_faction_power
  • factions_faction_powermax
  • factions_faction_claims
  • factions_faction_onlinemembers
  • factions_faction_allmembers
  • factions_player_name
  • factions_player_power
  • factions_player_powermax
  • factions_player_title
  • factions_player_rank
  • factions_player_rankforce
  • factions_player_rankprefix
  • factions_player_rankprefixforce

FactionsChat

• Fixing FactionsChat (was broken in the last build due to issue with optional parameter to support quick messages)
• Added /f c reload command to reload the settings from the configuration
• Removed /f c qm command since it is now integrated directly into the /f c command without needing a separate command to send a quick message.
• Added chat formatting capabilities (to act as a true chat plugin and not inject itself into other chat plugins which is not feasible for the latest versions of Paper). Chat formatting will use different internal processes based on if the server is running Spigot or Paper.
• Added PlaceholderAPI support (to act as a true chat plugin and not inject itself into other chat plugins which is not feasible for the latest versions of Paper). If installed, any PlaceholderAPI placeholder will work with FactionsChat.
• Added two placeholders to PlaceholderAPI for factions chat:
  • factions_chat_prefix - The prefix of the current chat mode
  • factions_chat_color - The main chat color of the current chat mode
• Added non-integrated placeholder parsing - if PlaceholderAPI is not detected, a subset of faction placeholders will still work in the chat format. This allows a server administrator to not have to install PlaceholderAPI unless they want other placeholders in their chat format (or if they already have it installed for other use-cases). Currently supported placeholders when PlaceholderAPI is not installed are:
  • rel_factions_relation
  • rel_factions_relation_lowercase
  • rel_factions_relation_color
  • factions_faction_name
  • factions_faction_nameforce
  • factions_player_rank
  • factions_player_rankforce
  • factions_player_rankprefix
  • factions_player_rankprefixforce
  • factions_player_title
  • factions_chat_prefix
  • factions_chat_color
• Plugin will now disable itself if we detect another chat plugin. Currently only looks for a few specific chat plugins - in the future we will attempt to make this a bit more dynamic.
  • This was done as our official stance is that you should only have one single chat plugin on your server. We will not support running FactionsChat when other chat plugins are present. You must pick one chat plugin.

MassiveCore

• Added a utility function to MUtil to check if the server is running Spigot or Paper.

Known Issues

Factions

• The same known issue with Factions that was present in v3.4.0 ALPHA-4 with SlimeFun4 still exists in this version, where SlimeFun does not properly check for when admin override/bypass mode is enabled when checking if a user has permission to access SlimeFun-related blocks in protected land. This means that if you are trying to access blocks of another faction, it will not work, even if you are in admin override/bypass mode. I submitted a pull request to SlimeFun to fix the issue, so hopefully it is fixed in a future version of SlimeFun.
• On Spigot 1.21.7, attempting to attach a lead to a fence post in a faction you don't have permission to do so will display the error message twice. This does not affect Paper 1.21.7. This will be fixed in a future alpha build.

FactionsChat

• If you use the default chat format, when you are not in a faction, there is a space before the display name. This will be fixed in a future alpha build.
• If you previously had FactionsChat installed, installing the new version will currrently not update the config file with the newly added config value for controlling the chat format.
  • Workarounds:
    • Manually add the ChatFormat field to the config.yml file. The default value looks like this: ChatFormat: '%factions_chat_prefix% &f<%rel_factions_relation_color%%factions_player_rankprefix%%factions_faction_name% &r%DISPLAYNAME%> %factions_chat_color%%MESSAGE%'. You can then use /f c reload to get the new setting without having to restart again.
    • Delete the config.yml file (or rename it) and restart your server. A new file will be generated, which you can then re-configure and use /f c reload to get the new settings without having to restart again.
• On Paper, sending a quick message sends the chat as an "unsecured" message (cannot be reported), whereas non-quick messages are sent "secured". Investigating possible solutions and will be dealt with in a future alpha build. On Spigot, all chats are sent as "unsecured" which is by design.
• On Paper, you cannot use color codes in chat messages (this will be implemented in a future alpha build). In Spigot you can - we will make this consistent between server types and lock it behind permissions.

MassiveCore

• Starting with Paper 1.21.7, a warning will displayed in the console upon player login about usage of PlayerLoginEvent. Paper has decided to deprecate this in favor of a new protocol. We are aware of this and will be implementing the new protocol into MassiveCore in a future alpha build.

---

IMPORTANT DISCLAIMER

This is an alpha release. I recommend exercising caution if considering running this in a production environment. Please test this in a test server before even considering deploying to your main production server! Also remember that bugs may exist - please file them in the Issues tab if you find them!

---

v3.4.0 ALPHA-4

Overview

This alpha release adds FactionsChat into the repository. FactionsChat is an optional Factions addon that adds faction chat channel functionality (similar to faction chat from Factions 1, for anyone who remembers that). The code for this plugin was based on Factions3Chat by eirikh1996, refactored to Java from Kotlin.

Features

FactionsChat

Like MassiveCore, Factions, and CreativeGates before it, this release of FactionsChat is not compatible with prior versions of Minecraft, as the minimum API version was bumped up to 1.21.4.

Known Issues

• The same known issue with Factions that was present in v3.4.0 ALPHA-3 with SlimeFun4 still exists in this version, where SlimeFun does not properly check for when admin override/bypass mode is enabled when checking if a user has permission to access SlimeFun-related blocks in protected land. This means that if you are trying to access blocks of another faction, it will not work, even if you are in admin override/bypass mode. I submitted a pull request to SlimeFun to fix the issue, so hopefully it is fixed in a future version of SlimeFun.

---

IMPORTANT DISCLAIMER

This is an alpha release. I recommend exercising caution if considering running this in a production environment. Please test this in a test server before even considering deploying to your main production server! Also remember that bugs may exist - please file them in the Issues tab if you find them!

---

v3.4.0 ALPHA-3

Overview

This alpha release fixes a bug with lingering potions (as well as Ender Dragon fire breath), where the console would be spammed in certain cases when a player was in the area of effect of the potion or fire breath. Additional compatibility layer work has been done, but it is still a work in progress. No new features have been implemented in this version.

Minecraft 1.21.5 was recently released, though we are still targeting 1.21.4. It's likely that it supports both, but 1.21.5 is at this point untested.

Known Issues

• The same known issue that was present in v3.4.0 ALPHA-2 with SlimeFun4 still exists in this version, where SlimeFun does not properly check for when admin override/bypass mode is enabled when checking if a user has permission to access SlimeFun-related blocks in protected land. This means that if you are trying to access blocks of another faction, it will not work, even if you are in admin override/bypass mode. I submitted a pull request to SlimeFun to fix the issue, so hopefully it is fixed in a future version of SlimeFun.

---

IMPORTANT DISCLAIMER

This is an alpha release. I recommend exercising caution if considering running this in a production environment. Please test this in a test server before even considering deploying to your main production server! Also remember that bugs may exist - please file them in the Issues tab if you find them!

---

v3.4.0 ALPHA-2

Overview

This alpha release adds CreativeGates into the repository and has been updated to support Minecraft 1.21.4. The beginnings of a compatibility layer have also been added to Factions. Also a couple bug fixes.

Features

CreativeGates

Like MassiveCore and Factions before it, this new release of CreativeGates is not compatible with prior versions of Minecraft, as there were numerous breaking changes made to both Spigot and Paper's APIs in recent Minecraft versions (including a hard fork of Paper from Spigot) which has resulted in needing to update the minimum API version to 1.21.4.

Factions

The beginnings of a compatibility layer between FactionsV1/FactionsUUID and Factions3 is in the works. This will allow us to translate API calls for FactionsUUID to Factions3. While not as efficient as a direct integration, it will expand our capabilities in the long run to support other plugins creating integrations. Theoretically, this will allow any plugin that integrates with FactionsUUID to integrate with Factions3. Such integrations will not be officially supported, but this at least will allow many features to work that would not have otherwise. This compatibility layer is not robust yet, and still needs some work. I plan to complete it (or at least the majority of it) for the full 3.4.0 release.

Bug Fixes

Factions

• Fixed a bug with leads, where a user could detach a mob connected to a lead and fence post in claimed land (this was a pre-existing bug)
• SlimeFun4 incorrectly attempts to load Factions3 as FactionsUUID, causing a console error when booting a server that has both SlimeFun4 and Factions3 installed. The new compatibility layer mentioned in the features list above should allow SlimeFun to provide proper compatibility with Factions3, but is not fully tested.
• Blocks, Items, and Entities that were added between 1.15 and 1.21.4 were not yet being protected/supported. This meant that certain mobs could still spawn when mob spawning was disabled (or animals for that matter), and certain blocks/items would allow interaction in claimed land when they shouldn't.
  • Properly protected Block/Item updates include:
    • Beehives/nests
    • New Buckets (multiple added since 1.15)
    • Chiseled Bookshelf
    • Crafter
    • Decorated Pot
    • Glow Item Frame
    • Lodestone
    • Potted plant variants (multiple added since 1.15)
    • Vault
    • Ender Chests
    • New Door/Trapdoor/Fence Gate variants (multiple added since 1.15)
    • Boats with Chests
    • All Sign variants (since sign editing was added in 1.20)
    • Brushable blocks (since archaeology was added in 1.20)
    • Copper (since copper waxing was added in 1.15)
  • Properly prevented entity (mob/animal) spawning support includes:
    • Allay
    • Armadillo
    • Axolotl
    • Bee
    • Bogged
    • Breeze
    • Camel
    • Creaking
    • Frog
    • Glow Squid
    • Goat
    • Hoglin
    • Mooshroom (technically was already correctly supported, but fixed a bug with it)
    • Piglin
    • Piglin Brute
    • Sniffer
    • Strider
    • Tadpole
    • Warden
    • Zoglin
    • Zombified Piglin

Known Issues

• With the addition of the compatibility layer, in testing SlimeFun4 (which was the reason it was added), it was discovered that SlimeFun does not properly check for when admin override/bypass mode is enabled when checking if a user has permission to access SlimeFun-related blocks in protected land. This means that if you are trying to access blocks of another faction, it will not work, even if you are in admin override/bypass mode. I will be working with SlimeFun to see if we can have them implement a fix.

---

IMPORTANT DISCLAIMER

This is an alpha release. I recommend exercising caution if considering running this in a production environment. Please test this in a test server before even considering deploying to your main production server! Also remember that bugs may exist - please file them in the Issues tab if you find them!

---