2.1.2latest2.1.2 | Fixes & Dependency UpdatesJan 20, 2024 You can review the changelog found on the release page on GitHub here. Feeling generous? By a developer a coffee! Every little bit helps2.1.12.1.1 | Minor Tweaks & Dependency UpdatesOct 8, 2023 You can review the changelog found on the release page on GitHub here. Feeling generous? By a developer a coffee! Every little bit helps2.12.1 | New AdditionAug 19, 2023 You can review the changelog found on the release page on GitHub here. Feeling generous? By a developer a coffee! Every little bit helps2.0.92.0.8 | Hot FixesJul 23, 2023 You can review the changelog found on the release page on GitHub here. Feeling generous? By a developer a coffee! Every little bit helps2.0.82.0.8 | 1.20.1 UpdateJun 29, 2023 You can review the changelog found on the release page on GitHub here. Feeling generous? By a developer a coffee! Every little bit helps2.0.7| 2.0.7 | Minor Update |Nov 14, 2022 You can review the changelog found on the release page on GitHub here. Feeling generous? By a developer a coffee! Every little bit helps2.0.6| 2.0.6 | Minor Update |Jun 7, 2022 You can review the changelog found on the release page on GitHub here. Feeling generous? By a developer a coffee! Every little bit helps2.0.5| 2.0.5 | Minor Update |Jun 10, 2020 You can review the changelog found on the release page on GitHub here. Feeling generous? By a developer a coffee! Every little bit helps 2.0.4-C| 2.0.4-C | Hook Hot FixMay 1, 2020 You can review the changelog found on the release page on GitHub here. Feeling generous? By a developer a coffee! Every little bit helps 2.0.4-B| 2.0.4 | Hot FixApr 15, 2020 You can review the changelog found on the release page on GitHub here. Feeling generous? By a developer a coffee! Every little bit helps 2.0.4| 2.0.4 | Minor Adjustments & FixesApr 15, 2020 You can review the changelog found on the release page on GitHub here. Feeling generous? By a developer a coffee! Every little bit helps 2.0.3⍟ 2.0.3 (Moderate Update) ⍟Apr 4, 2020 ⍟ Changes ⍟ · Implemented the "container-restoration" and "sign-restoration" options to the "config.yml". These two options will determine if data such as inventory or sign text is restored when regeneration takes effect. ⍟ Bug Fixes ⍟ · Resolved an issue where after an explosion the final block to be restored will always vanish to air. · Resolved an issue with the MassiveCore Factions hook.2.0.2⍟ 2.0.2 (Minor Update) ⍟Apr 3, 2020 ⍟ Changes ⍟ · Hooks are now stored in their own individual classes and checked back-to-back to ensure a location is safe. · Implemented the LandsAPI. ⍟ Bug Fixes ⍟ · Fixed an issue involving the Factions hook.2.0.1-B⍟ 2.0.1-B (Hot Fix) ⍟Apr 2, 2020 ⍟ Bug Fixes ⍟ · Resolved a simple issue where the world blacklist would require the world name to be in all caps.2.0.1⍟ 2.0.1 (Moderate Update) ⍟Apr 1, 2020 ⍟ Changes ⍟ · Implemented the “world-blacklist” option. This new list option will allow the ability to prevent PTG from functioning in particular worlds. · Automated general Factions support has been implemented in the form of the “block-in-factions” option. This option is here so that the ability to remove regenerative effects inside ALL claims rather than just allowing it where they can build/break. · The “block-entity-regeneration” option. This new list option will allow the ability to block regenerative effects from explosions by entity types found in the list.2.0PhysicsToGo 2.0 (Re-mastered)Mar 30, 2020 * The block sorting algorithm used throughout the plugin now uses a material priority system which significantly improves the overall performance, quality, and looks of regeneration effects. * Regeneration is now handled through instances of a single block. This allows the plugin to be more precise and detect the exact location without hesitation nor loss of data. * Location cloning is now used for container and sign data. This prevents any loss of data completely with these two restoration methods. * The configuration files have been re-evaluated, re-named, and improved. The “advanced.yml” should NOT be touched unless you know what you are doing or are instructed to. This is only because the values located inside the file are sensitive and require precision as well as deep knowledge of your current MC version’s materials. * Tree manipulation involving physics, regeneration, and cosmetic decal have been revamped using a mixture of algorithms bridged off of Merge Sort to capture the design/delay of a realistic tree plunge. * Implemented new checks to resolve and prevent any new or upcoming issues involving block state overrides and/or vanilla physics overrides such as normal liquid effects. * Hooks are no longer a thing. The plugin now cancels its own events when other plugins do so. This will allow it to be compatible with pretty much any plugin. Hooks can still be added using the events; however, as long as the protection plugin cancels explosives, breaking, or placing in regions PTG will NOT interfere. * Implemented tab completion, a new reload command, and new messages for each individual feature. * Completely documented all code intended to be available for source readers.1.9.4-B⍟ 1.9.4-B (Moderate Update) ⍟Jan 31, 2020 ⍟ Changes ⍟ · Removed the use of the 'Container' class since it was causing issues with versions 1.8.x and 1.7.x. · Most events now no longer yield to other plugins in terms of cancellation. The plugin now ignores cancellation and relies on direct hooks to keep things consistent among other plugins.1.9.4⍟ 1.9.4 (Hot Fix) ⍟Jan 21, 2020 ⍟ Changes ⍟ · Removed Kingdoms support due to major API issues. · Implemented the New Feudal API in replacement over the old. · Updated to the latest LandsAPI. · Implemented the new configuration system created for my other plugins.1.9.3-B⍟ 1.9.3-B (Hot Fix) ⍟Dec 17, 2019 ⍟ Bug Fixes ⍟ · Reversed a couple internal methods that prevented tree physics from functioning correctly without determining specific materials.1.9.3⍟ 1.9.3 (Moderate Update) ⍟Dec 17, 2019 ⍟ Bug Fixes ⍟ · Fixed an issue causing tree physics to incorrectly handle the initial broken block. ⍟ Changes ⍟ · Updated all methods and more to 1.15. · Implemented a new blacklist for tree physics falling blocks. · Adjusted the tree physics algorithm to handle tree detection a little better.1.9.3-SNAPSHOT⍟ 1.9.3 (Tiny Update) ⍟Dec 6, 2019 ⍟ Changes ⍟ · Changed event priorities to highest to let other plugins have first say (Change is mainly for protection plugins). · Removed the ability for tree physics to initiate from breaking leave blocks. · Updated some hooks and re-arranged some methods to better listen for hooks.1.9.2⍟ 1.9.2 (Moderate Update) ⍟Nov 21, 2019 ⍟ Changes ⍟ · Re-worked tree physics (Further tweaking and optimizing is still to come). This change includes the removal of some tree configuration features; however, has an improved algorithm built for speed and pretty looks! · Updated the Towny API to the latest!1.9.1⍟ 1.9.1 (Tiny Addition) ⍟Oct 22, 2019 ⍟ Additions ⍟ · Implemented a basic percentage for falling blocks.1.9⍟ 1.9 (Hot Fix) ⍟Aug 27, 2019 ⍟ Fixes ⍟ · Fixed the tree physics not containing hook checks. This should now support all active hooks.1.9-SNAPSHOT⍟ 1.9 (Small Update) ⍟Aug 26, 2019 ⍟ Changes ⍟ · Processed a GitHub merge adding more world blacklist options. · Added the update checker toggle option. · Made adjustments to resolve an issue where blocks would be replaced by the block regeneration feature.1.8.9⍟ 1.8.9 (Lands Fix) ⍟Jul 28, 2019 ⍟ Bug Fix ⍟ · Changes to the lands hook were made, due to a removed method in the lands api.1.8.8⍟ 1.8.8 (1.14.4 Update) ⍟Jul 21, 2019 ⍟ Changes ⍟ · Built against Bukkit and Spigot 1.14.4 instead of 1.14.3.1.8.7-F⍟ 1.8.7-F (Update) ⍟Jul 8, 2019 ⍟ Removals: ⍟ · Removed the advertisement due to it looking unpleasant and the lack of benefits. ⍟ Changes: ⍟ · Changed some loops to enhanced loops due to a small index issue on reloads and restarts.1.8.7-E⍟ 1.8.7-E (Teany Tiny Micro Update) ⍟Jul 7, 2019 This update was just for this small addition, but there were some adjustments that were not included in this build for a new update. Plans are still being reviewed to make sure PTG goes in the correct direction! ⍟ Additions: ⍟ · Added a small PebbleHost advertisement due to a new partnership! ⍟ Changes: ⍟ · Updated dependency to 1.14.3+, alongside some other hook dependencies.1.8.7-D⍟ 1.8.7-D (Silky Jam) ⍟Jun 18, 2019 ⍟ Additions: ⍟ · Added Beds and Banners to their proper lists in the default configuration. Since these blocks act like a single block with a "fake" half they are blocked from being destroyed by default. · Block Placing and Breaking has been given hook checks when the regeneration effect is fired. This is to hopefully prevent regenerating in blocked regions or protected land after the action was already performed. ⍟ Changes: ⍟ · No matter what, containers and inventory holders will now always be restored first when exploded. ⍟ Bug Fixes: ⍟ · Fixed a small issue involving chests not to regenerate correctly.1.8.7-C⍟ 1.8.7-C (Peanut) ⍟Jun 14, 2019 ⍟ Bug Fixes: ⍟ · Reversed some permission checks. Block placing and breaking were not registering without permissions.1.8.7-B⍟ 1.8.7-B (Pineapple) ⍟Jun 10, 2019 ⍟ Bug Fixes: ⍟ · Fixed an issue where placing and breaking would overlap each other and fight until the location was left as AIR. · Fixed an issue where if placing and breaking are done simultaneously the locations would be lost.1.8.7⍟ 1.8.7 (Pineapple) ⍟Jun 7, 2019 ⍟ Changes: ⍟ · Adjusted some code to ensure placing and breaking are functional. · Re-designed the world guard hook integration to better support 'block-in-all'. ⍟ Bug Fixes: ⍟ · Fixed the world guard hook ignoring configuration logic due to the path defined. · Fixed the place event overriding everything no matter if the event was enabled or not. · Fixed the break event overriding everything no matter if the event was enabled or not.1.8.7_SNAPSHOT⍟ 1.8.7_SNAPSHOT (Pineapple) ⍟Jun 7, 2019 ⍟ Additions: ⍟ · Added the 'block-in-all' option to the world guard hook section. This was added to prevent PTG from doing anything within ANY world guard region. The following was what was added: Code (Text): # If this is enabled, PTG will not work in ANY regions of worldguard. block-in-all: false1.8.6-C⍟ 1.8.6-C (Toast) ⍟Jun 5, 2019 ⍟ Changes: ⍟ · Updated dependencies to 1.14.2 and 1.12.2 JAR respectfully. · Updated some other dependencies that updated recently. · Reformatted code.1.8.6-B⍟ 1.8.6-B (Minor Update) ⍟May 27, 2019 ⍟ Change ⍟ - adjusted the Feudal hook to resemble that of 1.8.5. ⍟ Change ⍟ - adjusted the WorldGuard hook to work a little quicker and understandable. If blacklist is set to 'true', the region will be avoided and explosions, breaking, etc. will all act as it did in Vanilla to allow other plugins to interact with things. If blacklist is 'false', PTG stuff will only occur in those regions and nowhere else. ⍟ Addition ⍟ - added the 'config_latest.yml' file to the JAR and my all-new configuration auto-updater MK.1 that was added to many of my other plugins. ⍟ Addition ⍟ - added bStats Metrics to the plugin for logging. This can be disabled in the bStats folder; however, it does not effect the performance what so ever. This being said, I encourage everyone to leave it enabled.1.8.6⍟ 1.8.6 (Hot Fix) ⍟May 17, 2019 Though this build is not considered a SNAPSHOT, there are still some minor things that aren't necessarily issues, but something I would like to improve. ⍟ Fix ⍟ - minor fix that deals with the place and break event alongside regeneration where the bypass permission did the exact opposite of what they were supposed to do.1.8.5-C_SNAPSHOT⍟ 1.8.5-C_SNAPSHOT (Tiny Fix) ⍟May 3, 2019 For this update please reset your configurations to get fully updated material lists. If you wish to copy things over that is fine, but with new changes to the code, you are going to want some new materials in specific lists. The entire point of this build is to minimize "failed" regeneration for materials like double chests, crops, railings, and doors. The problem is due to 1.8-1.12 using different physics than 1.13-1.14. A lot of work is going into resolve this backward compatibility issue; therefore, be sure to leave PTG some love! ⍟ Fix ⍟ - fixed internal regenerative issues such as crops. Doors and Containers are somewhat still having minor issues, but I'm still experimenting with mechanics that newer MC versions broke.1.8.5-B⍟ 1.8.5-B (Hot Fix) ⍟May 3, 2019 ⍟ Fix ⍟ - fixed internal container saving when involving the "container-drops" option due to the new regeneration algorithm. ⍟ Fix ⍟ - fixed an issue where when TNT blocks are transformed into PRIMED_TNT they would erase the saved chest contents a split second after. This caused restoration issues. ⍟ Addition ⍟ - added the "tnt-fuse" option to the explosive-options section for ease configuration.1.8.5⍟ 1.8.5 (Major Update) ⍟May 2, 2019 PLEASE review these changes and add things accordingly to your configuration if an important change was made for you. This update is experimental, so of course report issues you encounter. Please review the known issues below: · Sand, Gravel, Anvils, and similar natural falling blocks don't regenerate and are affected by explosions and similar effects. Although this is not truly an issue, in the future I may implement a physics regeneration for this in particular. · 1.14 and 1.13 still encounter some uncommon double chest regeneration issues. However, it works a lot better and in general works great! ⍟ Change ⍟ - Explosive regeneration now uses the quicksort algorithm and regenerates from the lowest Y axis to the highest. ⍟ Addition ⍟ - major container adjustment for 1.13 and 1.14 servers. Containers regenerate with items properly; however, there are still some smaller facing issues within 1.14. ⍟ Removal ⍟ - removed the container fix tick option within the explosive options. Instead, items in containers for servers below 1.13 will be restored after the regeneration process is complete. ⍟ Fix ⍟ - fixed some blocks dropping items after exploding. All blocks are now set to air when drops are disabled. ⍟ Addition ⍟ - added the "blacklist" option under the world-guard hook section. This allows the user to swap between whitelist and blacklist.1.8.4-C⍟ 1.8.4-C (Tiny Update) ⍟Apr 28, 2019 ⍟ Change ⍟ - console based messages have made a return to the Logger with many levels from INFO to SEVERE. ⍟ Change ⍟ - minor adjustments via code and messages to clean up some looks.1.8.4-B⍟ 1.8.4-B (Hot Fix) ⍟Apr 27, 2019 ⍟ Fix ⍟ - fixed a modern ID issue with the old STEP_SOUND effects. STEP_SOUND effects will only enable via MC 1.7.x-1.12.x from now on due to material name changes and more.1.8.4⍟ 1.8.4 (1.14 Support) ⍟Apr 23, 2019 ⍟ Addition ⍟ - added 1.14 check for the setData method getter. 1.14 is fully supported!1.8.3-D⍟ 1.8.3-D (Extension Patch) ⍟Apr 16, 2019 This is an extension of the previous update (includes a feature that was intended to be added). Make sure to review the previous changelog: https://www.spigotmc.org/resources/...ental-regeneration.… The following must be updated and added to your configuration file: Under the "block-place-options": Code (Text): # If this is enabled, reversion effect will only occur above the set reversion height. reversion-above-height: false Under the "explosive-options" and "block-break-options": Code (Text): # If this is enabled, regeneration effect will only occur above the set regeneration height. regeneration-above-height: false1.8.3-C⍟ 1.8.3-C (Finishing Up Tree Physics & Polishing) ⍟Apr 16, 2019 These are small adjustments, but I hope you enjoy the update! Similar to SimplePortals, please note that this plugin is undergoing many changes and updates due to requests. Be sure to drop a review, like, or donation to show PhysicsToGo some love, so I can continue to improve the plugin! The following must be updated and added to your configuration file: Code (Text): # If this is enabled, falling tree blocks will drop their correct material drops upon impact (Natural drops). (This requires "physics-form" to be disabled). # THIS IS NOT THE SAME AS "physics-drops". tree-drops: true # If this is enabled, falling tree block entities will drop their items if harmed ("physics-form" must be enabled). physics-drops: false ⍟ Addition ⍟ - added natural drop capabilities to tree physics. ⍟ Change ⍟ - changed code around for polishing the build out of SNAPSHOT.1.8.3-C_SNAPSHOT⍟ 1.8.3-C_SNAPSHOT (Tiny Adjustments) ⍟Apr 14, 2019 These are small adjustments, but please note that this is still a SNAPSHOT build. ⍟ Change ⍟ - changed some code around to resolve an issue preventing the tree physics feature from disabling via the configuration. ⍟ Change ⍟ - tree physics falling blocks check will no longer be executed when tree physics is disabled.1.8.3-B_SNAPSHOT⍟ 1.8.3-B_SNAPSHOT (Hot Fix) ⍟Apr 8, 2019 This is a SNAPSHOT build please report any issues or ask questions as needed. ⍟ Fix ⍟ - fixed an issue preventing falling blocks from forming when enabled. ⍟ Fix ⍟ - fixed an issue causing some falling blocks to not stack when landing on one another. ⍟ Change ⍟ - normalized and randomized offsets of the explosive physics to provide a form of realism to the feature.1.8.3_SNAPSHOT⍟ 1.8.3_SNAPSHOT (Tree Physics) ⍟Apr 8, 2019 This is a SNAPSHOT build please report any issues or ask questions as needed. ⍟ Addition ⍟ - radial tree physics have been implemented. Add the following to your configuration file: Code (Text): tree-physic-options: # If this is enabled, tree physics will be enabled. tree-physics: true # For performance, tree physics goes from current location to max height and around the broken block with radius below. # This being said, note that blocks attached to other trees within this radius will be effected (Recommended value is 5). tree-physics-radius: 5 # If this is enabled, falling tree blocks will form on the ground. physics-form: false # If this is enabled, falling tree blocks will drop their correct material drops (Natural drops). physics-drops: false # If this enabled, formed falling blocks will be removed after the duration defined below. physics-removal: false # This is the formed falling block removal delay in ticks (20 ticks = 1 second). physics-removal-delay: 20 # Here is where tree regeneration can be configured. tree-regeneration: # If this is enabled, tree physics will be regenerated. regeneration: true # This option is how fast each block is regenerated in ticks (Note: 20 ticks equals 1 second.) speed: 20 # This option is how long before the regeneration process takes place in ticks (Note: 20 ticks equals 1 second.) delay: 20 # When an effected break material is destroyed the materials in this list will be effected by physics and dropped to # the ground if attached to the broken block (Format: <Material>:<Durability>). Use -1 for all durabilities. effected-physic-materials: - "ACACIA_LEAVES:-1" - "BIRCH_LEAVES:-1" - "DARK_OAK_LEAVES:-1" - "JUNGLE_LEAVES:-1" - "OAK_LEAVES:-1" - "SPRUCE_LEAVES:-1" - "LEAVES:-1" - "LEAVES_2:-1" - "ACACIA_LOG:-1" - "BIRCH_LOG:-1" - "DARK_OAK_LOG:-1" - "JUNGLE_LOG:-1" - "OAK_LOG:-1" - "SPRUCE_LOG:-1" - "STRIPPED_ACACIA_LOG:-1" - "STRIPPED_BIRCH_LOG:-1" - "STRIPPED_DARK_OAK_LOG:-1" - "STRIPPED_JUNGLE_LOG:-1" - "STRIPPED_OAK_LOG:-1" - "STRIPPED_SPRUCE_LOG:-1" - "LOG:-1" - "LOG_2:-1" # These are the materials that will begin tree physics when broken. (Format: <Material>:<Durability>). Use -1 for all durabilities. effected-break-materials: - "ACACIA_LOG:-1" - "BIRCH_LOG:-1" - "DARK_OAK_LOG:-1" - "JUNGLE_LOG:-1" - "OAK_LOG:-1" - "SPRUCE_LOG:-1" - "STRIPPED_ACACIA_LOG:-1" - "STRIPPED_BIRCH_LOG:-1" - "STRIPPED_DARK_OAK_LOG:-1" - "STRIPPED_JUNGLE_LOG:-1" - "STRIPPED_OAK_LOG:-1" - "STRIPPED_SPRUCE_LOG:-1" - "LOG:-1" - "LOG_2:-1"1.8.2⍟ 1.8.2 (Minor Update) ⍟Apr 7, 2019 ⍟ Addition ⍟ - the block physics form feature has been extended and now formed blocks can be removed after a defined delay. The following must be added to the configuration under the explosive section: Code (Text): # If this is enabled falling blocks that are formed will be removed after the defined delay. block-physics-removal: true # This is the delay in which formed blocks are removed (Note: 20 ticks equals 1 second.) block-physics-removal-delay: 601.8.1⍟ 1.8.1 (WorldGuard Backwards Compatibility) ⍟Mar 5, 2019 This update aimed to bring back support for WorldGuard 6.x, which is now fully functional thanks to some heavy testing in the HyperDrive 5.x hooking system that was created fairly recently! I hope you guys enjoy! ⍟ Change ⍟ - the WorldGuard hook now supports 6.x - 7.x thanks to the new interface version adjustment approaches. ⍟ Fix ⍟ - the Kingdoms hook was not cooperating with the safe location double check feature that was implemented at an earlier date.1.8⍟ 1.8 (Tiny Update) ⍟Feb 2, 2019 Please note that WorldGuard 7.x is the only form of WorldGuard supported in newer versions until further evaluation is applied. ⍟ Change ⍟ - hooks now all work together and respect each other to make sure the location is safe for all hooks instead of one at a time. ⍟ Addition ⍟ - added the HookCallEvent which can be used to implement custom hooks for any plugin required. The point of this is to remove the hundreds of requests I get for specific plugin hooks. Hooks will be limited by default to maximize plugin performance. ⍟ Fix ⍟ - factions hooks have been reversed and tested using FactionsUUID to ensure proper prevention is being applied.1.7.9⍟ 1.7.9 (Lands Hook) ⍟Jan 31, 2019 ⍟ Addition ⍟ - added Lands hook back into the plugin using the LandsAPI. This hook will prevent PTG from applying physics and other forms of block manipulation inside of claimed regions. The following must be added to the configuration under the hooks section: Code (Text): lands: # If this is enabled, physics to go features will not work within land claims. use-lands: false1.7.8⍟ 1.7.8 (Super Hot Fix) ⍟Jan 4, 2019 ⍟ Addition ⍟ - the following option needs to be added under the "explosive-options.block-regeneration-options" section: Code (Text): # This is the delay after the general regeneration for containers to be re-checked to ensure every item is restored. container-fix-rate: 40 ⍟ Addition ⍟ - the following option needs to be added under the "explosive-options" section: Code (Text): # Drop watch is a list of materials that are double checked during explosions to ensure blocks don't drop items. drop-watch: - "BEETROOT_SEEDS:-1" - "WHEAT_SEEDS:-1" - "CROPS:-1" - "CARROT:-1" - "CARROTS:-1" - "POTATO:-1" - "POTATOES:-1" - "BEETROOT_BLOCK:-1" - "BEETROOTS:-1" - "BEETROOT:-1" - "WHEAT:-1" ⍟ Fix ⍟ - fixed an issue involving block drops by adding a double check list under the "explosive-options" section that will ensure crops and other sensitive materials don't drop block unless told otherwise. ⍟ Fix ⍟ - fixed an issue involving double chests not restoring properly by adding a second delay to restore the container contents again as a double check to ensure the items are restored. There are no duplications that come with this, in fact, when the container is restored it will take X amount of time until the player will even see that the items restored.1.7.7⍟ 1.7.7 (Hot Fix) ⍟Dec 27, 2018 ⍟ Fix ⍟ - fixed a towny hook issue that caused exceptions to be thrown when the hook is disabled. This fix changed the exception and try catch statements to suppress potential missing class issues.1.7.6.9⍟ 1.7.6.9 (Small Adustment) ⍟Dec 26, 2018 ⍟ Adjustment ⍟ - suppressed hook location grabbing failures. This would lead to some meaningless errors in console stating that a location was not used by a hook.1.7.6.8⍟ 1.7.6.8 (Tiny Adjustment) ⍟Dec 24, 2018 This update was microscopic, but Merry Christmas to everyone! ⍟ Removal ⍟ - removed many unnecessary exceptions that were harming location restoration speeds. ⍟ Adjustment ⍟ - adjusted a couple values for future physic features like tree decapitation. ⍟ Fix ⍟ - fixed a small material loading issue. When a material was in a list with more than one ":" symbol the material would be skipped entirely.1.7.6.7⍟ 1.7.6.7 (Minor Update) ⍟Nov 29, 2018 ⍟ Addition ⍟ - Added the "ptg.reload" permission for the reload command. ⍟ Change ⍟ - All messages dealing with commands are now configurable. Add the following to your configuration file: Code (YAML): # These are all the configurable messages that can be configured (Set the message "" to disable). messages: usage : "&cUsage: /ptg <reload>" reloaded : "&aAll configurations have been reloaded for PhysicsToGo." no-permission : "&cYou don't have permission to use this."1.7.6.5⍟ 1.7.6.5 (Hot Fix) ⍟Nov 28, 2018 This update fixes the WorldGuard and WorldEdit hook entirely for the Beta 2 versions of 7.0 that were recently released on Bukkit. 6.2.2 and older versions are not currently supported. ⍟ Fix ⍟ - Reversed the whitelist and changed values to the new Vectors introduced in the latest World Edit 7.0. ⍟ Fix ⍟ - Fixed an issue where block physics would always randomize to the right of the explosion giving off a weird looking animation. ⍟ Fix ⍟ - Fixed a smaller issue internally that caused 1 out of 50 blocks to disappear and not regenerate until every other block does. ⍟ Fix ⍟ - Fixed a permission issue where the permission also canceled out hook checks. ⍟ Change ⍟ - Changed values in the Update Checker and the plugin.yml to match the resource pages description and awkward version links.1.7.6.4-C⍟ 1.7.6.4-C (World Guard 7.0 Legacy Update 3) ⍟Nov 28, 2018 This is still an experimental phase for the WorldGuard hook. ⍟ Fix ⍟ - This update is stable with build #1756 of WorldGuard 7.0 Legacy. The API of WorldGuard is currently under heavy changes to the point where there is no way around using reflection to have both WG 7.0 and 6.2.2. I have dropped 6.2.2 support from this point on until further research is done since this type of change would heavily impact the performance of the plugin.1.7.6.4-B⍟ 1.7.6.4-B (Hot Fix) ⍟Nov 27, 2018 This build like most letter builds is experimental in terms of World Guard hooks. If World Guard is not in your interest, this build is optional. ⍟ Fix ⍟ - Reversed the new WorldGuard hook auto-detection ratio. This will fix an issue where the whitelist performed the exact opposite of what originally was intended.1.7.6.4⍟ 1.7.6.4 (Minor Update) ⍟Nov 26, 2018 GitHub page has been updated live for v1.7.6.4 . ⍟ Change ⍟ - The WorldGuard hook has been adjusted and given in auto detection for the 7.0 and 6.2.2 APIs (Please note that the 7.0 API is the experimental build found here ) ⍟ Addition ⍟ - Added the "ptg.bypass", "ptg.bypass.break", and "ptg.bypass.place" permissions.1.7.6.3-B⍟ 1.7.6.3-B (World Guard 7.0 Legacy Hot Fix) ⍟Nov 25, 2018 ⍟ Fix ⍟ - Adjusted the world guard 7.0 support due to class changes in the latest experimental build. Due to the constant updates that are done to World Guard 7.0 classes are constantly changing, therefore, updates for PTG will be released when needed.1.7.6.3⍟ 1.7.6.3 (WorldGuard 7.0 Legacy Hook) ⍟Nov 25, 2018 ⍟ Change ⍟ - This update changes the world guard hook to only work with the new 7.0 API. (If you use 6.2.2 or below with this update will not work)1.7.6.2⍟ 1.7.6.2 (Tiny Update) ⍟Nov 24, 2018 ⍟ Change ⍟ - The WorldGuard hook now uses the region list as intended by allowing regions within the list to be modified by PTG. ⍟ Change ⍟ - Adjusted some code around for the update checker and command sources.1.7.6.1⍟ 1.7.6.1 (Super Hot Fix) ⍟Nov 5, 2018 ⍟ Change ⍟ - The block break event no longer cancels the entire event if the materials in the affected material blacklist. ⍟ Fix ⍟ - Fixed an issue with tall flowers no regenerating properly on 1.11.x versions.1.7.6⍟ 1.7.6 (Tiny Update) ⍟Nov 4, 2018 This is an attempt to bridge two of the modular events. Without doing a full re-code to how either is implemented. Hope you guys enjoy! ⍟ Change ⍟ - Adjusted the placement and break events to respect each other. When both events are active placed block are remembered and watched for when the player breaks a block to make sure the broken block does not drop items. ⍟ Fix ⍟ - Fixed a small old id system issue that would affect client-side performance due to intense particles in 1.7.10. ⍟ Change ⍟ - Changed some values around to support the adjustment for the events.1.7.5⍟ 1.7.5 (Hot Fix) ⍟Nov 2, 2018 ⍟ Fix ⍟ - Fixed a small issue preventing the Feudal hook from functioning with the block place events. ⍟ Adjustment ⍟ - Adjusted some code for 1.12.2 and below support changes.1.7.4⍟ 1.7.4 (Minor Update) ⍟Sep 21, 2018 ⍟ Fix ⍟ - Since 1.7.10-1.12.2 deal with block states differently doors and other 2 block materials have been having issues with restoring and such. This was potentially fixed, but there may be some exceptions in the game. ⍟ Addition ⍟ - In the 'explosive-options' section the option below has been added as a work around for 2 block item regeneration and destruction prevention. Code (YAML): # If a material is placed in this list the block directly under the material will be saved as well to prevent damage from default physics. # (Note: Set the durability to -1 to ignore durability) help-needed-material : - "WOODEN_DOOR:-1" - "ACACIA_DOOR:-1" - "BIRCH_DOOR:-1" - "DARK_OAK_DOOR:-1" - "IRON_DOOR:-1" - "JUNGLE_DOOR:-1" - "SPRUCE_DOOR:-1" ⍟ Fix ⍟ - The block breaking feature no longer allows destruction of the block if it's material is in the blacklist.1.7.3⍟ 1.7.3 (Minor Update) ⍟Sep 20, 2018 Small update, but this fixes a moderate issue along side a nice couple changes, enjoy! ⍟ Fix ⍟ - Fixed an issue where the explosion material blacklist would not prevent the destruction of a block, but prevent any external features from occurring. ⍟ Change ⍟ - Adjusted the explosion material blacklist so that it now accepts -1 or lower as a durability value behind materials to ignore the durability entirely. ⍟ Removal ⍟ - Removed the Lands plugin support hook due to internal issues when adding new hooks. ⍟ Addition ⍟ - In replacement to the Lands hook, Kingdoms+ support has been added.1.7.2.1⍟ 1.7.2.1 (Super Hot Fix) ⍟Sep 9, 2018 ⍟ Fix ⍟ - After examination a better method with a more universal approach completely fixes the non updating plants with the block breaking regeneration. This update should fix the entire issue altogether alongside removing the previous configuration option from the config.1.7.2⍟ 1.7.2 (Hot Fix) ⍟Sep 9, 2018 Note: This update was quite difficult to perform as many default mechanics were bypassed. Some default mechanics still occur with regeneration at time; however, they are natural enough that they do not need to be worried about, unless plants are too close to each other for example. ⍟ Fix ⍟ - With block breaking regeneration there was a new list, which can be found below, that was implemented to automatically fix the top or bottom block of plants when regenerated. (Note: Add the following to the block breaking options section.) Code (YAML): # These materials will be fixed when regenerating broken blocks. # (Note: This feature is targeted at double block plants, add/remove needed/unwanted materials) stack-fixing-materials : - "TALL_GRASS" - "ROSE_BUSH" - "PEONY" - "LARGE_FERN" - "LILAC" ⍟ Fix ⍟ - Fixed a small material issue for 1_13_R2 builds. ⍟ Addition ⍟ - Added Towny and Residence hooks. Add the following to your hooks section: Code (YAML): residence : # If this is enabled, physics to go features will not work within residence land. use-residence : false towny : # If this is enabled, physics to go features will not work within town blocks. use-towny : false1.7.1⍟ 1.7.1 (Minor Update) ⍟Aug 28, 2018 Please note that I do have a list of things that need to be addressed for all of my plugins, but due to my college semester my updates and support have been slowed down. I do appreciate all the requests coming in, but I hope you guys understand if the request doesn't get into the plugin immediately. Note: The hooks below are still experimental I do need to tweak them and such to get their maximum performance, but this update is for those in need. As always please report bugs, but also please be patient with fixes and such with my current schedules. Thank you! P.S. The GitHub is always up to date, so if there are issues and you happen to have found it within the current code don't hesitate to create a pull request as it greatly would speed up the process of that particular fix. ⍟ Addition ⍟ - Added ASkyBlock hooks. ⍟ Addition ⍟ - Added GriefPrevention hooks. ⍟ Addition ⍟ - Added Factions & FactionsUUID hooks. ⍟ Addition ⍟ - Added Lands hooks.1.7⍟ 1.7 (Tiny Update) ⍟Aug 27, 2018 ⍟ Addition ⍟ - Added full 1.13-1.13.1 packets and support.1.6.9⍟ Minor Update ⍟Jul 25, 2018 ⍟ Change ⍟ - reverted the effects to use material ids. Since the method has not yet been converted to the new materials the method remains unusable for 1.13. All this means is that for now in 1.13, block effects and sounds will not be displayed.1.6.8⍟ 1.13 Update ⍟Jul 23, 2018 It's finally here! This update adds 1.13 support by removing useless material data values that were removed in the update. Since PhysicsToGo is block modification based this update was a bit difficult; however, I'm doing everything in my power to keep support for all versions! ⍟ Change ⍟ - Until the bukkit effect methods are updated to support the new block data the original block effects have been set to ID 1 from previous versions to simply keep the plugin in the stable zone. ⍟ Fix ⍟ - Fixed an issue with 1.13 changes that removed some methods that were used for instance creating.1.6.7⍟ 1.13-pre7 Update ⍟Jul 16, 2018 Even though this update is not Beta, be prepared for issues in regards to the 1.13 support that was implemented. ⍟ Addition ⍟ - Added 1.13-pre7 support! ⍟ Addition ⍟ - Added the all-new 'reversion-height' to the 'block-place-options' sections. ⍟ Addition ⍟ - Added the all-new 'regeneration-height' to the 'block-break-options' and 'explosive-options' sections.1.6.5⍟ Large Update ⍟Jun 30, 2018 Please review to the new configuration below and apply any changes/additions. .SpoilerTarget">Spoiler: Configuration /w Changes Code (YAML): hooks-options : # Here is where you can customize all options about the WorldGuard hook. world-guard : # This toggles the WorldGuard hook. use-hook : false # Regions inside the list below will allow PTG to perform its magic inside each region. region-whitelist : - "allowed_zone" feudal : # If this is enabled, kingdoms will not be effected by anything in PTG. use-hook : false explosive-options : # If this is enabled blocks will not be effected by explosions. block-damage : true # When blocks are damaged from explosions, should all effected blocks be tossed in different directions? block-physics : true # When blocks are damaged from explosions, should they be effected by PTG's regeneration effects? block-regeneration : true # If this is enabled falling blocks will form upon contact. block-physics-form : false # Here is where you can customize options that effect the block regeneration. block-regeneration-options : # This option is how fast each block is regenerated in ticks. (Note: 20 ticks equals 1 second.) speed : 20 # This option is how long before the regeneration process takes place in ticks. (Note: 20 ticks equals 1 second.) delay : 20 # Materials inside the list below will be avoided by any regeneration or physic effects involved with explosions. effected-material-blacklist : - "MOB_SPAWNER:0" - "BEDROCK:0" # When blocks are damaged from explosions, should the effected blocks drop their relative items? block-drops : false # If this option is enabled, previously destroyed container and sign contents will be restored to regenerated blocks. block-restoration-memory : true # Should destroyed containers drop their items? # (Note: The items will be restored inside the container if the above option is enabled.) container-drops : false # The worlds inside the list below will not be effected by any explosive modification made by PTG. blacklisted-worlds : - "world_the_end" # Entity types inside the list bellow will be effected by any explosive modification made by PTG. entity-explosion-blacklist : - "CREEPER" block-break-options : # If this is enabled PTG will listen when a player breaks a block and perform effects. block-break-event : false # When blocks are damaged by players, should the blocks be regenerated? block-regeneration : true # Here is where you can customize options that effect the block regeneration. block-regeneration-options : # This option is how long before the regeneration process takes place in ticks. (Note: 20 ticks equals 1 second.) delay : 20 # Materials inside the list below will be avoided by any regeneration or physics effects involved with block breaking. effected-material-blacklist : - "OBSIDIAN:0" - "BEDROCK:0" # When blocks are damaged from players, should the effected blocks drop their relative items? block-drops : false # If this option is enabled, previously destroyed container and sign contents will be restored to regenerated blocks. block-restoration-memory : true # Should destroyed containers drop their items? # (Note: The items will be restored inside the container if the above option is enabled.) container-drops : false # The worlds inside the list below will not be effected by any player block damage modified by PTG. blacklisted-worlds : - "world_the_end" block-place-options : # If this is enabled PTG will listen when a player places a block and perform effects. block-place-event : false # If this is enabled block placing will be cancelled. (Note: This will avoid the 'block-reversion' feature.) block-place-cancel : false # When blocks are damaged by players, should the blocks be regenerated? block-reversion : true # Here is where you can customize options that effect the block regeneration. block-reversion-options : # This option is how long before the regeneration process takes place in ticks. (Note: 20 ticks equals 1 second.) delay : 20 # Materials inside the list below will be avoided by any reversion or physics effects involved with block placing. effected-material-blacklist : - "OBSIDIAN:0" - "BEDROCK:0" # The worlds inside the list below will not be effected by any player placement modifications by PTG. blacklisted-worlds : - "world_the_end" ⍟ Change ⍟ - When the plugin is disabled a restored block count is now displayed for more information on the process. ⍟ Addition ⍟ - Falling blocks are now given metadata and removed entirely when the plugin is disabled. A removal count is also displayed for more information. ⍟ Addition ⍟ - The 'block-place-options' section was added. ⍟ Addition ⍟ - The 'explosive-options' section now has the brand new 'entity-explosion-blacklist' section to allow entity control. ⍟ Fix ⍟ - All methods no longer store block states and information if restoration or reversion is un-used. ⍟ Fix ⍟ - Falling block no longer sometimes drop items if 'drop-items' for the section is disabled. ⍟ Fix ⍟ - All sections have had their 'blacklisted-worlds' option properly defined. Before they were all running off an integrated default value within the code.1.6.2⍟ Minor Update ⍟Jun 28, 2018 ⍟ Fix ⍟ - Reversed the 'block-physics-form' option to work properly as intended. ⍟ Change ⍟ - Block physics now take a random offset from 0 - 1 to give a sense of random flow. All blocks that perform the animation should fly in different directions.1.6.1⍟ Minor Update ⍟Jun 25, 2018 ⍟ Change ⍟ - All used events in PTG are now registered in a normal manner to allow other plugins to flex around it and not become affected in the long run. ⍟ Fix ⍟ - Fixed an issue with the block physics offset internally. (This was causing a block to randomly go straight down instead of away from the blast site) ⍟ Addition ⍟ - Do to a request Feudal support has been added. You can find the added configuration portion below. This feature has been tested heavily and prevents all PTG effects while inside a kingdom claim. Code (YAML): hooks-options : # Here is where you can customize all options about the WorldGuard hook. world-guard : # This toggles the WorldGuard hook. use-hook : false # Regions inside the list below will allow PTG to perform its magic inside each region. region-whitelist : - "allowed_zone" feudal : # If this is enabled, kingdoms will not be affected by anything in PTG. use-hook : false ⍟ Change ⍟ - New plugin startup and shutdown messages have been added to console to provide more information about the plugin's process. ⍟ Addition ⍟ - The block physics form option has made a return to the explosive options section. Please view the changed configuration here and add missing content. Code (YAML): explosive-options : # If this is enabled blocks will not be effected by explosions. block-damage : true # When blocks are damaged from explosions, should all effected blocks be tossed in different directions? block-physics : true # When blocks are damaged from explosions, should they be effected by PTG's regeneration effects? block-regeneration : true # If this is enabled falling blocks will form upon contact. block-physics-form : false # Here is where you can customize options that effect the block regeneration. block-regeneration-options : # This option is how fast each block is regenerated in ticks. (Note: 20 ticks equals 1 second.) speed : 20 # This option is how long before the regeneration process takes place in ticks. (Note: 20 ticks equals 1 second.) delay : 20 # Materials inside the list below will be avoided by any regeneration or physic effects involved with explosions. effected-material-blacklist : - "MOB_SPAWNER:0" - "BEDROCK:0" # When blocks are damaged from explosions, should the effected blocks drop their relative items? block-drops : false # If this option is enabled, previously destroyed container and sign contents will be restored to regenerated blocks. block-restoration-memory : true # Should destroyed containers drop their items? # (Note: The items will be restored inside the container if the above option is enabled.) container-drops : false # The worlds inside the list below will not be effected by any explosive modification made by PTG. blacklisted-worlds : - "world_the_end" ⍟ Change ⍟ - The update checker's messages have been re-worked into the new changes. ⍟ Addition ⍟ - The plugin has been optimized once more to allow easy integration of future hooks.1.6⍟ Minor Update ⍟Jun 25, 2018 Yes, the plugin is out of Beta that fast! ⍟ Fix ⍟ - The block break regeneration now properly breaks blocks to drop their natural items. ⍟ Fix ⍟ - Fixed all block regeneration animation effects. ⍟ Addition ⍟ - The update checker has been re-enabled! ⍟ Change ⍟ - The block break regeneration states are no longer removed on startup instead they now restore when needed.1.6-Beta⍟ Large Update ⍟Jun 24, 2018 This update requires a full reset of your current configuration file. This update brings a more modular look to the plugin. The point of this update is to welcome future physic based features and hooks! Please note that this update is a BETA build. This means everything has been tested; however, there could be potential issues that will be heavily monitored. ⍟ Re-Code ⍟ - The entire configuration was re-created from scratch and re-designed. ⍟ Removed ⍟ - The automatic explosion drop pick up has been entirely removed. This feature was not useful since it didn't use the player who used the explosive. ⍟ Addition ⍟ - Many new block breaking options. ⍟ Change ⍟ - Many options in the configuration were combined into a single option. This may seem a little confusing at first; however, overall it gives a better approach when configuring. ⍟ Fix ⍟ - When the server is stopped or the plugin is disabled untouched states will no longer be restored. Extra checks were added to ensure modified blocks in need of restore are the only things restored. ⍟ Change ⍟ - TNT and animation effects are now automatically set inside the code at default values. Since these options are untouched by many users there default MC values have been pre-assigned. ⍟ Removed ⍟ - The update checker has been disabled temporarily until next update.1.5.4⍟ Minor Update ⍟Jun 17, 2018 ⍟ Fix ⍟ - modified some listing code to remove a potential memory leak when the plugin was disabled. ⍟ Addition ⍟ - added the new 'player-break-regeneration' option this option applies all regeneration effects to blocks that are broken by a player. This feature was fully implemented meaning all container and sign restoration methods were integrated. Please add the following to your configuration file: Code (YAML): # When a player mines a block should it be regenerated? # (Note: This option uses the regeneration speed, offsets, etc.) player-break-regeneration : false1.5.3* Moderate Update *May 23, 2018 * Change * Moved some options around for better design inside the default configuration file. * Fix * Fixed the soft-dependencies inside the plugin configuration file. * Fix * Fixed the yielding within explosions (This was causing blocks to forcefully drop items). * New * Implemented the new update checker used within all of my newest plugin updates!1.5.2* Small Fix *May 21, 2018 * Fix/Change * - Implemented a new method of dealing with block drop prevention. When enabled, exploded blocks should no longer drop items.1.5.1* Minor Update *May 16, 2018 * Fix * - fixed some issues involving the update checker. * Addition * - added a new toggle option for the update checker in the config. (Note: You must either add it in manually using the id 'update-checker' or reset configuration to get this option.) * Change * - updates are no longer mentioned to players in-game. The console will be the only area updates are announced. * Change * - moved and reformatted code.1.5Minor UpdateMay 1, 2018 Removed - MCUpdate due to code changes is being removed for connectivity issues. Fix - Fixed the repository for future updates.1.4.9| Minor Update |Dec 16, 2017 What was changed in 1.4.9? · Fixed some MCUpdate issues where the runnable would duplicate itself during the '/ptg reload' command. · Fixed a abstract class issue which was due to obfuscation that shouldn't have been in the plugin in the first place. · Added some method enhancing code. · Removed unnecessary code. · Rebuilt the GitHub repository due to the IDE switch to NetBeans.1.4.8| Bug Fixes & Improvments | v1.4.8 |Dec 11, 2017 What was changed in v1.4.8? · Fixed the 'block-regeneration-blacklist' and 'block-physic-blacklist' lists inside the configuration. There was a issue where a typo happened while compiling the last update causing the both list to look like 'block-regeneration-blackList' and 'block-physic-blackList', so the reading is now fixed. You will, however, need to fix these lists in your configuration by changing them to 'block-regeneration-blacklist' and 'block-physic-blacklist' if you wish to not reset your configuration once more. · Improved the block physics speed when forming new entities. · improved the speed of the regeneration code, including container restoration. · Added some extra methods for when I decide, can get to it, to add more physics like trees falling, environmental physics, and more.1.4.7<| Important Pre-1.13 Update |>Dec 8, 2017 What was changed in PhysicsToGo v1.4.7? · Material Ids were completely replaced with Material names due to the huge Minecraft 1.13 change. In result your configuration file will need to be either compared to the new configuration and updated or reset entirely unfortunately. · Fixed some issues with the regeneration blacklist as it was not functioning at all.1.4.6.5Small UpdateDec 5, 2017 What was changed in v1.4.6.5? · Fixed a issue with container saving and restoring. · Updated to the latest 1.12.2 build. · Added the following option to the configuration for chest dropping. Code (Text): # When containers such as chests, furnaces, or hoppers are exploded shall they drop their contents like normal? # (Note: If container drops is enabled container saving and restoring will be automatically disabled due to incompatibility via code) container-drops: false1.4.6.1FixJun 22, 2017 · A fix for McUpdate nothing to major in this update!1.4.5The Revive of The Non-Dead...Apr 11, 2017 Due to the configuration re-code you will need to reset you configuration, but the good news is you can just copy over most of your previous configuration options. However I thank you personally for using PhysicsToGo! Look foward to future updates! Bug Fixes: · Fixed a issue involving torches. · Fixed a issue where containers would sometimes forget their purpose in life. Improvements : · Increased runtime speeds through all block queries. · Added McUpdate support. · Redid the configuration a little bit. · Added a switch option so you can tell PhysicsToGo whether you want the WorldGuard region list to only allow physics in the region or block physics in the regions!1.4.2Block State Saving UpdateJan 23, 2017 · Added Block State Saving. When the server disables all destroyed block will be restored if in memory.1.4* New Features & Bug Fixes *Dec 14, 2016 New Features: · Added Container Content Restoring Support · Added Sign Information Restoring Support · Added Block State Support (Torches, Grass, Snow, etc. all regenerates properly now) · Added Support so that I can begin adding more features for regeneration like System Memory (Tasks to restore blocks will save to disk so that the plugin can start back where it left off in regeneration) and more ways/events for PTG to regenerate blocks. Bug Fixes: · Fixed a issue where blocks would occasionally glitch and not finish regenerating what was exploded.1.3.1* Minecraft Version Updated v1.3.1 *Nov 17, 2016 · Small update that adds 1.11.x (R1) Spigot/Bukkit Support!1.3* Minecraft Version Updated v1.3 *Jun 29, 2016 · Updated to support 1.7-1.10.21.2.7* Per World Support v1.2.7 *May 18, 2016 · Added per world support so you can now enable this plugin in curtain worlds or disable this option to enable like normal!1.2.6.3* Hot Fixes v1.2.6.3 *May 13, 2016 · Fixed a small bug with regeneration · Fixed a bug with the Y axis of block physics1.2.6May 13, 2016 1.2.5May 12, 2016
Similar projects
Plugin →Let Me Despawn
Improves performance by tweaking mob despawn rules. Say bye to pesky unintentional persistent mobs.
25MSueta
JourneyMap
Real-time map used for mapping in-game or your browser as you explore.
14.7MSueta
Emotecraft
Create your own emotes in Minecraft.
7.5MSueta
Simple Tpa
A simple tpa plugin which sends requests
5.4MSueta
Common Network
Forge and Fabric Unified Networking Solution
3.9MSueta
Set Home
A lightweight plugin for players to set their homes.
3.8MSueta