Upstream/MobArena
1
0
Fork 0
mirror of https://github.com/garbagemule/MobArena.git synced 2024-11-26 04:25:21 +01:00
Code Issues Projects Releases Wiki Activity
5566d8fd86
MobArena/changelog.md

183 lines
21 KiB
Markdown
Raw Normal View History

Add changelog. This, along with a (currently not committed) script to generate github releases and Spigot/DBO formatted release notes from this changelog, should reduce some of the friction associated with new releases.
2018-08-05 20:47:06 +02:00
# Changelog
All notable changes to the project are recorded in this document in a user-friendly format.
The format is loosely based on [Keep a Changelog](https://keepachangelog.com/).
Each version in the document contains only user-facing changes (including API changes).
However, each version in the document is also a link, and clicking a version link reveals all commits that went into the given version.
The release notes published on Spigot and DBO are derived from this document.
The "Unreleased" section contains changes that have not yet been released.
These changes will (most likely) be included in the next version.
## [Unreleased]
Add changelog entry for 90d1f211fa5f3b6fe6f472606c86b3ffd4355730. Adds a changelog entry for the changes made in 90d1f211fa5f3b6fe6f472606c86b3ffd4355730.
2020-01-13 11:07:33 +01:00
- A new `ready` state is now available for arena sign templates. Signs are in this state when all players in the lobby have readied up, but the arena has not yet started due to a start delay timer. Check the wiki for details.
Add changelog entry for 6e8a3e1626cfebd7cd26586cae516c481d864a96. Adds a changelog entry for the changes made in 6e8a3e1626cfebd7cd26586cae516c481d864a96.
2020-01-11 01:37:08 +01:00
- Arena signs now support dynamic list entry variables for 4 different player lists. As an example, `<notready-1>` results in the name of a player in the lobby who hasn't readied up yet. This is useful for visualizing who is holding up the lobby. Check the wiki for details.
Add support for Elytra as chest pieces in class chests. Makes the class chest armor guessing logic pair `"ELYTRA"` up with the chest piece slot. This specific matching works, because there are no underscores in the `"ELYTRA"` item name. Fixes #616
2020-04-25 21:08:08 +02:00
- Elytra are now supported chest pieces in class chests.
Guess Equippables from Material name suffix. This commit changes the way Equippable wrappers are created, such that they more closely match the way class chest armor pieces are "guessed". That is, instead of looking directly at the Material value of the given item, we instead look at the name _suffix_, i.e. the part after the last underscore in the name, e.g. `BOOTS` in `IRON_BOOTS`. The neat thing about this approach is that it is compatible with future items that follow the same naming convention, such as Netherite armor pieces. The downside is that it is stringly typed and not particularly "pretty", and if the naming convention breaks or new items are introduced (such as the elytra), we will have to make modifications anyway. Fixes #636
2020-08-09 12:42:44 +02:00
- Elytra and Netherite armor pieces now correctly auto-equip if specified in the generic `armor` node in classes in the config-file.
Add support for color codes in boss names. Translates color codes for the boss name string right before setting it in the BossWave object. Closes #610
2020-04-27 11:21:05 +02:00
- Boss names now support color codes.
Add per-arena setting `arena-warp-offset`. This commit introduces a quality-of-life feature for spreading players out during the warp to the arena floor. The feature is configured via the new per-arena setting `arena-warp-offset`. When the value is greater than 0.01, MobArena will add a random number of units between 0 and the offset value to the X and Z axes in either direction. For example, if the value is set to 3, players will be teleported to a random location in a 3x3 square centered on the arena warp, rather than directly to the arena warp itself. Closes #371
2020-08-20 23:30:57 +02:00
- New per-arena setting `arena-warp-offset` can be used to spread out players randomly by an offset from the arena warp. This should help prevent players taking suffocation damage.
Add per-arena setting `announcer-type`. Introduces the concept of an Announcer, which is invoked whenever the `announce` methods on the Arena interface are invoked. Previously, all announcements would simply be sent to the arena's Messenger, but this new feature allows us to move them up into titles to help declutter the somewhat overloaded chat box. By default, to help people discover the new feature, the announcer type is `title`, but it is possible to switch back to `chat` for the original behavior. Closes #272
2020-08-22 11:32:45 +02:00
- New per-arena setting `announcer-type` determines where to display per-arena announcements such as wave spawns, auto start timers, boss abilities, and death messages. Options are `title` (default) or `chat`.
Rework Root Target. This commit completely reworks the Root Target ability implementation by replacing the repeated teleportation code with potion effects. The old implementation relied on teleporting the target every tick for a given duration, but because teleporting also involves pitch and yaw, the result was a constant "snapping back in place" experience. The new implementation works by applying the following potion effects with a very large amplification: - Slowness, to prevent the player from moving out of place. - Slow falling, to negate fall damage. - Negative jump boost, to prevent the player from jumping around. Note that the jump boost uses a _negative_ amplification to make it have the inverse effect, i.e. a much worse jump ability. It is still possible to jump an arguably negligible amount away from the root location. Fixes #490
2020-05-04 07:49:20 +02:00
- The Root Target ability now uses potion effects (slowness, slow falling, and negative jump boost) instead of repeated teleports. This should make for a smoother root experience.
Don't kick players when `spectate-on-death: true`. This commit forgoes some of the work done in the join/leave refactoring of commit b1c6b618279fd181799aeafdb041ad2d1775a585. The intent behind the original commit was to make the join/leave process a very strictly defined set of steps that would work atomically to try to ensure a stable, predictable process. As a result, the idea of making spectators out of respawning players meant first kicking them out of the arena and then re-joining as spectators, as if they had manually typed `/ma leave` followed by `/ma spec`. However, on some multi-world setups, this process causes people to get thrown around a bit, which makes for a poor user experience. This commit changes the behavior when `spectate-on-death: true` such that the player isn't kicked, but is instead added to the spectator player pool when they respawn. If the flag is false, players will still get sent to the spectator area for one tick and then immediately kicked out as if they had manually typed `/ma leave`. This does create a little bit of jumping around, but because there is only one world change (as there would be anyway), it is deemed acceptable at this point in time. Closes #508
2020-08-19 22:51:27 +02:00
- Using `spectate-on-death: true` no longer forces players out to their join location/exit warp before moving them to the spectator area. This should prevent "jumpy" behavior in multi-world setups.
Bump to `HIGHEST` priority for PlayerRespawnEvent. Plugins like Multiverse and EssentialsX have features that override the world spawn location for players respawning both with and without bed locations. If MobArena catches the PlayerRespawnEvent too early, these plugins will likely overwrite the respawn location set for players that respawn after dying in an arena session. Because MobArena is a minigame and its respawn manipulation logic only runs for respawning arena players, it is perfectly reasonable for it to get the final say in where these players should respawn. It would have been nice to just use `HIGH`, but that is what EssentialsX runs at, so we gotta go higher than that.
2020-08-19 22:55:23 +02:00
- Players should now properly respawn at the spectator area rather than at world spawn on servers with plugins that override respawn locations.
Allow non-existent `pet-items` nodes. If someone spins up MobArena with a really old config-file or simply removes the `pet-items` section, the plugin throws an NPE. This commit fixes that by allowing the section to not exist. It might be a good idea to log some helpful information, but let's wait and see if this isn't good enough. Fixes #606, closes #608. Thanks Chew!
2020-03-28 17:05:41 +01:00
- Config-files with missing `pet-items` nodes no longer errors. A missing `pet-items` node in `global-settings` is treated as empty, i.e. no pet items will be registered.
Use `toUpperCase()` in SetPlayerTime step. This commit fixes the `player-time-in-arena` per-arena setting by switching to `toUpperCase()` on the string value, which means that the values can actually result in something meaningful, rather than always throwing an exception. The feature was broken in commit b1c6b618279fd181799aeafdb041ad2d1775a585, and it appears to be the only such instance to sneak through. Fixes #621 Co-authored-by: Bobcat00 <Bobcat00@users.noreply.github.com> Co-authored-by: Chew <chew@chew.pw>
2020-05-17 08:15:05 +02:00
- The `player-time-in-arena` setting has been fixed.
Fix `soft-restore` for blocks broken by players. This commit fixes the per-arena config setting `soft-restore`. Due to commit 92c4ce1a8ba5e441ca670bd3690c9db58a4d852f, the soft restore logic won't run on BlockBreakEvents, because to reach that specific part of the event handler, the `protect` flag has to be set to `true`. However, due to an early return in the soft restore logic if the `protect` flag _is_ set to `true`, it is effectively impossible for it to run. The fact that this functionality has been broken for over 6 years (!) with almost no reports of it is perhaps a testament to how little it is being used in the wild.
2020-07-21 16:07:10 +02:00
- The `soft-restore` setting has been fixed for blocks broken by players. Note that the functionality is still unreliable for non-trivial blocks.
Improve config-file errors from `/ma setting`. Catches ConfigError and prints its message rather than letting it bubble up to the command handler as an uncaught exception. This means that instead of seeing "An internal error occurred...", command senders now see the underlying error message, as well as a short message telling them to fix the error in the config-file and reload. Closes #599
2020-05-31 21:12:47 +02:00
- Config-file errors imposed by incorrect usage of `/ma setting` no longer cause "internal errors". Instead, the errors are properly communicated in the command output similar to how the `/ma reload` command works.
Prevent guardians from instantly retargeting. The vanilla behavior for most mobs is that they just stop minding their targets' business if aggro is lost. The same applies to guardians and elder guardians. To prevent the pace of gameplay from stagnating, MobArena compensates for target loss by helping the mobs find a new target. The issue with this in terms of guardians is that breaking line of sight is the only way - besides killing it very quickly - to avoid taking damage from a guardian due to its lock-on laser attack. This means that guardians and elder guardians need to be excluded from the retargeting logic to make sense in an arena setting. This commit introduces a new EnumSet of EntityTypes to exclude from the retargeting logic. It is not a particularly pretty solution, especially not since ArenaListener is such a huge class already, but it does make it easier to add more mobs later down the road, and it does a slightly better job at giving way to a config setting at some point. For the Mobs Rework, a per-monster flag like `auto-retarget` or similar might be a much better solution, so it's possible to have encounters like a small batch of guardians that _don't_ lose their targets but have very little health, so the "race against time"-aspect can exist, but in a much more configurable way. Fixes #601
2020-07-28 09:45:18 +02:00
- Guardians and elder guardians no longer instantly retarget players when they break line of sight. This should make their behavior work a bit closer to vanilla.
Clone class chest contents before modifying them. Certain class chest items are cloned before they are made unbreakable, but not all. This commit changes that, so all items in the input array are cloned prior to setting the unbreakable flag on them. The items that were previously cloned specifically no longer need to be, since they are included in the initial cloning. Fixes #637
2020-08-18 23:37:54 +02:00
- Items in class chests are now cloned before they are made unbreakable and given to players. This fixes an issue where setting `unbreakable-weapons: false` had no effect on the items. Note that any affected items in existing class chests will need to be replaced.
Remove MagicSpells integration. The integration only works reliably with the `clear-wave-` settings set to `true`, because it relies on there being only one "current" wave. This is a fundamental issue with the way sessions run right now, and is another good example of why the Sessions Rework is necessary. It is possible to achieve the exact same functionality by just making a couple of Upgrade Waves before and after the waves that need to have limited skill sets (thanks Lucy). With just a couple of quality-of-life features like wave "triggers", it's possible to make things just the way they were with the integration, but by using some more general building blocks. Closes #609
2020-07-16 22:19:33 +02:00
- The MagicSpells integration has been removed. This means that the extra `magicspells.yml` config-file (if it exists) no longer does anything and can be removed.
Release 0.104.2.
2020-01-03 21:28:44 +01:00
## [0.104.2] - 2020-01-03
Cross check arena/lobby regions in `intersects()`. This commit changes how the ArenaRegion `intersects()` method works: - The implicit null checks in the `setup` and `lobbySetup` flags have been replaced with actual null checks inside the auxiliary `intersects()` function. Not only does this make the auxiliary method more robust for potential future use, it also helps tidy up the code a bit. So neat! - The semantics have changed, since `setup` depends on more than just the `p1` and `p2` points. This fixes an (unreported) bug where the check would report a false negative in case an overlapping arena region was defined, but e.g. the arena warp was missing. - Instead of only checking arena vs. arena and lobby vs. lobby, we now also check arena vs. lobby and lobby vs. arena. That is, if the arena region is defined, we check it against both the arena region and lobby region of the other ArenaRegion (if they are defined). Same deal with the lobby region. This should ensure that no combination of overlaps pass through the check.
2020-01-03 01:39:41 +01:00
- The region overlap check now works across both arena and lobby regions, i.e. all four combinations of intersections between two regions (arena-arena, arena-lobby, lobby-arena, and lobby-lobby) are evaluated.
Fix NPE in region overlap check. This commit fixes an issue with the new `intersects()` method on ArenaRegion. Instead of blindly assuming that the region points `p1` and `p2` are set when the method is called, we first make sure both regions are properly set. Fixes #590
2020-01-03 01:28:11 +01:00
- Arenas with missing regions no longer cause errors in the region overlap check.
Release 0.104.1.
2019-12-31 23:27:49 +01:00
## [0.104.1] - 2019-12-31
Don't check for recurrent waves on join. This commit removes a condition in ArenaImpl#canJoin(Player) that checks to see if the arena's WaveManager has any recurrent waves. Removing this condition is safe, because the WaveManager already makes sure to have a "catch all" default wave at hand for when no wave definitions match a given wave number. As such, the condition in ArenaImpl is completely unnecessary, and was in fact the root cause of a bug. Fixes #566
2019-08-16 00:46:01 +02:00
- It is no longer necessary to have recurrent waves for an arena to work. MobArena automatically creates a "catch all" recurrent wave in case the arena session reaches a wave number that isn't covered by any other wave definitions.
Rewrite EntityTargetEvent handling. This commit is a complete rewrite of the target event handling logic in the ArenaListener class. Instead of the complex, inconsistent code structure with too many line breaks between control flow branches, we just have a thin logic wrapper that delegates the event handling to smaller, more focused functions that handle arena pets, arena monsters, and foreign entities on their own. A couple of auxiliary methods are introduced to try to limit the amount of warnings produced by checking set membership with `contains()` when the entity/target is an Entity and the collection is a sub type. Fixes #572
2019-12-29 17:34:56 +01:00
- Entities outside of the arena can no longer target players, pets, or monsters inside of the arena.
Use regular player name when tab completing `/ma kick` and `/ma restore`. Since the actual execution of these commands use the regular player name instead of the display name, the tab completion is useless if it doesn't also use the regular player name. Fixes #589
2019-12-29 17:47:32 +01:00
- Tab completion for `/ma kick` and `/ma restore` now uses actual player names instead of display names.
Fail fast if world is null when parsing locations. This commit introduces a null check in the ConfigUtils `parseLocation` method. If the world of a location string does not exist, the method now throws an IllegalArgumentException, which allows callers to fail more gracefully instead of having to resort to null checks. Additionally, the parsing of exit warps, leaderboards, or linked class chests is wrapped in try-catch statements that re-throw ConfigErrors for better error reporting. Fixes #421
2019-12-31 20:40:51 +01:00
- If the world of an exit warp, leaderboard, or linked class chest is not available on (re)load, MobArena now throws a config error instead of failing silently later down the road.
Report overlapping arena regions on load. This commit introduces an `intersects()` method on ArenaRegion that allows us to check whether two regions intersect. The new method is employed in ArenaMasterImpl during arena load. If an arena's region intersects with any other arena's region (in the same world), we print a warning to the server log. Fixes #367
2019-12-31 23:21:08 +01:00
- Overlapping arena regions are now reported as warnings in the server log during arena load, because overlapping regions can result in undefined, buggy behavior.
Rewrite plugin version checker. This commit removes the old version checker that used the DBO resource page and replaces it with a custom checker that uses the "legacy" Spigot resource API. The Spigot API is much more lightweight and doesn't require any sort of parsing. The new version checker uses a simple cache, keeping version checks fresh for up to one hour, reducing the need to go fishing on every op login. The cache resets on restarts, though, but this is acceptable. Note that no attempt has been made to ensure correctness on multiple, consecutive invocations when the cache is stale. If a cache refresh is initiated, all update checks invoked before the cache refresh has ended will behave as if no update is available. This is acceptable, because update checks are non-essential, the time frame is extremely narrow, and the most common result of an update check is "no updates available", since the amount of update checks made is vastly greater than the amount of updates released.
2019-12-31 14:01:27 +01:00
- MobArena's internal version checker has been rewritten. It now uses the resource API of Spigot instead of DBO. It's also a lot more lightweight and caches results for up to one hour.
Release 0.104.
2019-08-09 00:04:06 +02:00
## [0.104] - 2019-08-08
Add support for extended and/or upgraded potions in the item syntax. This commit adds support for altering the data portion of a potion item by prefixing either `long_` or `strong_` to get extended duration or level II versions of the given potion, respectively. Closes #520
2019-07-24 19:56:36 +02:00
- Extended and upgraded potions are now supported in the item syntax by prepending `long_` or `strong_` to the data portion of a potion item (e.g. `potion:strong_instant_heal:1` will yield a Potion of Healing II). Check the wiki for details.
Add basic tab completion support. This commit adds support for basic tab completion for most of the commands that take arguments. Some completions are somewhat intelligent, e.g. `/ma join` which only lists enabled and "functional" arenas that the given player is permitted to use. Others are just kinda dumb, e.g. `/ma enable` which indiscriminately lists all arenas. Closes #405
2019-07-26 22:26:10 +02:00
- MobArena now has basic tab completion support for most of the commands that take arguments.
Make class pets aggro hostile mobs who attack their owners. When a player takes damage from a hostile mob, the player's class pets will have their target set to that mob. This means that even zombies can function as "real" pets!
2019-08-05 16:08:53 +02:00
- The `pet-items` node in `global-settings` now supports any living entity as a pet - even zombies! Pets will aggro hostile mobs that damage their owner, but only tameable pets (wolves, cats, etc.) will properly follow their owners around. This should also allow 1.14 servers to replace `ocelot` with `cat` in their `pet-items` node to get cat pets working again.
Add names to class pets. This commit adds custom names to class pets in the form `<player name>'s pet`. This should help players more easily distinguish between pets and hostile mobs.
2019-08-05 14:34:05 +02:00
- Pets now have custom names that denote who their owner is, e.g. "garbagemule's pet".
Call pet spawning logic in Upgrade Waves. Due to the package structure and location of MASpawnThread, SpawnsPets doesn't need to be opened up for this to work. This change opens up for quite a few different upgrade strategies, since pet items obtained outside of Upgrade Waves are transformed as well. It is technically a breaking change, because it breaks the invariant that "after arena start, no items are transformed to pets". However, since pet items are customizable, it is possible to just change the `bone` to `sponge` in the config-file if bones carry some sort of implicit meaning in an existing setup. Closes #524
2019-08-08 00:23:51 +02:00
- Pet items can now be used in Upgrade Waves. When an Upgrade Wave spawns, all pet items are transformed to pets just like when the arena session starts. Note that while only Upgrade Waves trigger this behavior, pet items obtained elsewhere (e.g. from Supply Wave drops) will also be transformed on subsequent Upgrade Waves.
Add support for potion effect upgrades in Upgrade Waves. It doesn't seem like there was any real reason to leave out potion effects as upgrades in Upgrade Waves previously, so they were likely just forgotten in the Things API overhaul. Closes #565
2019-08-07 23:43:11 +02:00
- Potion effects can now be used as upgrades in Upgrade Waves. Check the wiki for details.
Make all "damageable" items unbreakable. This commit changes how the unbreakable setting works by just assuming that everything that is "damageable" (implements the Damageable interface) needs to be set as unbreakable. This means that the entire weapons/armor collection in ArenaClass is obsolete, and all of the checking is contained in ArenaImpl. Fixes #544
2019-07-20 22:47:00 +02:00
- Tridents and crossbows are now considered weapons with regards to the `unbreakable-weapons` flag. All class items that have durability now have their unbreakable flag set to true unless the `unbreakable-weapons` and/or `unbreakable-armor` flags are set to `false`.
Use new BlockData API for Leaderboards. This commit fixes a bug on Minecraft 1.14 servers where leaderboards would cause a NullPointerException due to the MaterialData API being broken. Instead, we now use the new BlockData API, and everything is back to normal. Fixes #536
2019-07-20 22:48:48 +02:00
- Leaderboards now work again on servers running Minecraft 1.14+.
Use new BlockData API for non-linked class chests. Similar to the previous commit about leaderboards, this commit fixes the crash caused by using the MaterialData API on Minecraft 1.14 servers. Fixes #546
2019-07-20 22:54:05 +02:00
- Class chests (non-linked) now work again on servers running Minecraft 1.14+.
Use max health value instead of base value in SetHealth step. This commit changes the SetHealth step such that it uses the player's own value for max health rather than the generic base value. As a result, players who join holding items that lower their max health will be missing health as soon as they join the lobby. But because food levels are maxed and locked, the health will quickly regenerate. Unfortunately, players who join with a higher health value than the base max health value will have their health capped to the base max health value on the way out of the arena. This was also the case before this commit, but it is worth mentioning again for completeness. These odd side effects are currently "necessary" because the effects of items that change max health values for players don't take immediate effect in the same tick as they are added/removed, so because MobArena's join sequence is synchronous, we can't feasibly "get it right". Fixes #545
2019-07-20 22:37:23 +02:00
- MobArena no longer crashes when players try to join with items that lower their max health below the default of 20. Players with lower max health will notice missing health in the lobby, but it will quickly regenerate to full.
Lock food level for players in the lobby or spectator area. There is no reason why food should be a thing in the lobby or spectator area. This commit effectively disables it for players in those places/states, while retaining the in-arena conditional logic based on the config-file setting. Fixes #514
2019-07-20 21:40:24 +02:00
- Food levels no longer deplete for players in the lobby and spectator area.
Give stone swords to wither skeletons on spawn. Fixes #538
2019-07-20 22:39:22 +02:00
- Wither skeletons now correctly spawn with stone swords.
Fix check for arena monsters in monster damage logic. This commit changes how the final "catch all" works for incoming monster damage. Instead of checking if the damager entity is a LivingEntity, we check if it is a monster of the arena and then proceed as normal. Note that this change may make it possible for monsters in the arena to take damage from non-arena entities. The so-called "catch all" doesn't really catch everything, but it does catch the infighting that it was designed to catch. One "not thought of" damage source is that of player-made golems, so coincidentally, this commit fixes #550.
2019-07-25 23:15:05 +02:00
- Mobs now correctly take damage from player-made iron golems.
Don't assume implemented interfaces by EntityType in SitPets. This commit changes how SitPets determines if a nearby entity is "pet material". Instead of assuming that wolves and ocelots are tameable, we check for the Tameable interface. This means that we get rid of the "concrete" types, Wolf and Ocelot, and also fixes a bug on Minecraft 1.14 servers where ocelots are no longer tameable, but cats are. It also kinda catches parrots, but they will not sit if they are flying or perching on the player's shoulder when joining. Because ocelots are no longer tameable in 1.14, they shouldn't cause trouble here, but because they are tameable in 1.13, we need to rely on the Tameable interface to maintain both backwards and forwards compatibility. Fixes #548 (kind of - no more exceptions thrown, but the pet ocelots from SuperLuckyBlock may misbehave, however that is a different issue).
2019-07-26 23:13:34 +02:00
- Cat and parrot pets now also sit when their owner joins an arena (although parrots perching on players' shoulders will still follow them into the arena).
Explicitly make pig zombies angry when they spawn. This commit changes the MACreature spawn logic such that any pig zombie spawned will be angered immediately. Fixes #561
2019-08-03 20:30:45 +02:00
- Pig zombies are now angry immediately after they spawn as they should be.
Keep track of Vexes summoned by Evokers. This is a bit of an overhaul of how CreatureSpawnEvent is handled: - Events happening outside the arena region are still ignored, as are armor stands placed in edit mode. - Otherwise, if the arena isn't running, we blanket reject all entities. - Player-mode iron golems and snowmen are still allowed. - Anything that isn't spawned by a plugin is rejected, _unless_ it is a Vex spawned with "default" spawn reason, which is what the Evoker summon spell uses. In the end we have a "custom" spawn reason inside the arena region while it's running, which is perfectly "legal". And because of the unfortunate use of Creature (instead of Mob) in MACreature, Slimes and Magma Cubes still need to be handled separately here. Fixes #564
2019-08-07 23:41:02 +02:00
- Vexes summoned by evokers are now kept track of, so they count towards `clear-wave-before-next`, and they are properly removed at arena end.
Drop support for getting potion effect types by magic number IDs. getById() is deprecated, and while this does break existing functionality, it is a good kind of breakage because it forces people over to the name-based IDs, which they will eventually be happier with. Partial fix for #406
2019-07-22 00:05:45 +02:00
- Support for denoting potion effects by magic number IDs has been dropped. This means that if your config-file has any such magic numbers in it, MobArena will no longer successfully parse them and will throw an error on startup.
Drop support for auto-respawn. This commit removes the `auto-respawn` arena setting and the logic associated with it. MobArena's hacky implementation of auto-respawning is buggy and discouraged. To get true auto-respawn functionality we'd have to move to the Spigot API instead of the Bukkit API.
2019-08-05 16:00:01 +02:00
- Support for auto-respawning has been dropped. The hacky way it was implemented is not officially supported by the Bukkit API and is highly discouraged because it is very buggy.
Release 0.103.2.
2019-04-23 11:21:44 +02:00
## [0.103.2] - 2019-04-23
Don't change player flySpeed on join/spec. From a purist standpoint, the flySpeed tag should never be messed with in MobArena, because simply turning off flight should be enough. It is likely that the flySpeed tag was originally included to cull "cheaters" who somehow managed to activate flight in the arena anyway, but this isn't really MobArena's responsibility and can very probably be handled by other means of cheat prevention in WorldGuard regions or the like. By not touching the flySpeed tag, it makes it much easier for server owners to recover from crashes where the leave steps aren't executed, leaving players "locked in the air" when they try to fly. Closes #509 since this "fix" was the reason that feature request was made.
2019-02-03 14:08:13 +01:00
- MobArena no longer touches the `flySpeed` player attribute when players join an arena. This should fix issues where a crash would result in players being "locked in the air" when trying to fly outside of the arena. It also introduces compatibility with plugins that use flight to augment player abilities.
Clone ItemStack before adding to player inventory. Spigot is at it again with another breaking change to the API where the JavaDocs have been retrofitted to match the new, ancient way of writing software. The addItem and removeItem methods originally just added or removed whatever they could when called, and returned a map of items that failed due to lack of space/items. Now, with the breaking API change, these methods actually *mutate their arguments* - a practice that has been heavily discouraged for decades in modern software development, and something you usually only see in C these days. This change, like many others in the same vein, show the complete recklessness, incompetence, and lack of awareness from an otherwise talented team of developers. Hopefully, they will continue to hone their skills so that we can eventually have a stable API again.
2019-02-03 14:15:40 +01:00
- Fixed a bug introduced by a breaking API change in Spigot where a player with a nearly full inventory might cause item rewards to change stack amounts.
Relocate `mobarena.admin.teleport` permission check. Instead of explicitly ALLOW'ing a teleport if a player has the permission, we let the teleport handler logic run its course. If an arena explicitly REJECTs the teleport, we need to cancel the event, but the permission now overrides that behavior. This means that only in the case of an impending event cancellation, the permission kicks in. This is important, because the permission is supposed to override the decision to cancel, rather than drive the decision to uncancel. With this change, MobArena never uncancels something it wouldn't have uncancelled otherwise, meaning it won't interfere with teleports outside of its own context, and thus won't interfere with other plugins. Fixes #515, closes #516 Thanks to @minoneer for the bug report and pull request that this code was based upon!
2019-02-16 13:32:07 +01:00
- MobArena no longer uncancels teleport events that occur outside of its own context when players have the `mobarena.admin.teleport` permission. This fixes a bug where the permission could override the cancellation of events that weren't related to MobArena.
Use attribute base value instead of 20 when setting player health. The previous hardcoded value of `20.0` works in most cases, but if a server uses a base health higher than 20, players don't get a full heal. Worse, if the base health is lower than 20, MobArena crashes when it tries to set the health to 20, which is now out of range. This commit introduces the Attribute enum to MobArena's code base and uses it to get the base value for player max health. This should fix the aforementioned issues. Fixes #513
2019-02-16 13:45:59 +01:00
- When resetting player health, MobArena now uses the player max health attribute base value rather than a fixed value of 20. This fixes crashes associated with max health values lower than 20, and ensures that players always get a full heal with values higher than 20.
Use a blacklist for the server version check. The whitelisting approach works well for the legacy builds, because the version landscape doesn't change with those. However, the main build on the master branch will not run on a server version other than 1.13, so come 1.14, MobArena will be broken. This commit fixes this problem by changing to a blacklisting approach for the main build on the master branch. Checking for versions that the build *can't* run on brings back MobArena's old resilience to version changes on the Minecraft side of things.
2019-04-16 11:32:16 +02:00
- The server version check on the main build (currently for 1.13) now explicitly looks for incompatible versions rather than compatible versions. This brings back the "works unless otherwise specified" nature of the plugin, and thus a MobArena build for Minecraft 1.13 should (knock-on-wood) work on 1.14.
Relocate `mobarena.admin.teleport` permission check. Instead of explicitly ALLOW'ing a teleport if a player has the permission, we let the teleport handler logic run its course. If an arena explicitly REJECTs the teleport, we need to cancel the event, but the permission now overrides that behavior. This means that only in the case of an impending event cancellation, the permission kicks in. This is important, because the permission is supposed to override the decision to cancel, rather than drive the decision to uncancel. With this change, MobArena never uncancels something it wouldn't have uncancelled otherwise, meaning it won't interfere with teleports outside of its own context, and thus won't interfere with other plugins. Fixes #515, closes #516 Thanks to @minoneer for the bug report and pull request that this code was based upon!
2019-02-16 13:32:07 +01:00
Thanks to:
- minoneer for help with fixing and testing the teleport bug
Release 0.103.1.
2018-12-31 15:33:06 +01:00
## [0.103.1] - 2018-12-31
Update changelog with change from 6a8c6a9.
2018-09-23 15:41:37 +02:00
- Like the other user commands, the permission for `/ma ready` now defaults to true.
Use unbreakable item meta flag for unbreakable weapons and armor. This changes how unbreakable items work in MobArena. It removes the legacy "repair logic" and replaces it with the item meta unbreakable flag. This approach should work all the same, except now if weapons and armor in class chests have special durability values, these are preserved in the cloning. This should make MobArena compatible with plugins that depend on special durability values, such as QualityArmory.
2018-09-23 15:44:54 +02:00
- Unbreakable weapons and armor now use the unbreakable item flag instead of item durability and on-hit repairs. This means that MobArena's unbreakable items are now compatible with plugins that depend on special durability values, such as QualityArmory.
Prevent spectators from taking damage at all times. Spectating is possible both during and before/after arena sessions. This means that an early return from the entity damage cancellation logic when the arena isn't running is going to allow damage to go through to spectators of non-running arenas, which means they can die. By simply removing the early return (and placing it in the one branch that actually requires it explicitly), spectators should no longer be able to take damage. This fixes #502.
2018-12-30 14:05:02 +01:00
- Spectators can no longer take damage when the arena isn't running.
Allow class pets to teleport to their owners. This closes #497.
2018-12-31 14:20:27 +01:00
- Pets can now teleport back to their owners if they get too far away.
Make enchantments case insensitive. Lowercasing the enchantment string before feeding it to the Bukkit API makes the enchantments a little more "copy/paste proof" when grabbing the uppercased names from the JavaDocs/Minecraft wiki.
2018-12-31 14:27:05 +01:00
- Enchantment names are now case insensitive (i.e. `FIRE_PROTECTION` is the same as `fire_protection`).
Make commands case insensitive. Note that this doesn't make the arguments for commands case insensitive. Each command is still responsible for lowercasing their arguments if it makes sense for them to do so. This closes #446.
2018-12-31 14:47:05 +01:00
- All commands are now case insensitive. This means that typing `/ma join` is the same as typing `/MA JOIN`. This should help reduce the confusion with commands like `/ma l` where the L can be confused with a 1 (one).
Release 0.103.
2018-08-28 22:00:59 +02:00
## [0.103] - 2018-08-28
Add changelog. This, along with a (currently not committed) script to generate github releases and Spigot/DBO formatted release notes from this changelog, should reduce some of the friction associated with new releases.
2018-08-05 20:47:06 +02:00
- It is now possible to add a fixed delay (in seconds) between waves with the new per-arena setting `next-wave-delay`.
Add join-interrupt-timer per-arena setting. This commit adds a new per-arena setting, join-interrupt-timer, which, when set to a positive number, will introduce a delay to the join and spec commands. During this delay, if the player takes damage or moves more than one block's distance, the command will be interrupted. Closes #482
2018-08-05 21:17:05 +02:00
- The new per-arena setting `join-interrupt-timer` makes it possible to add a "delay" to the join and spec commands. If the player moves or takes damage during this delay, the command is interrupted. This should help prevent exploits on PvP servers.
Add changelog. This, along with a (currently not committed) script to generate github releases and Spigot/DBO formatted release notes from this changelog, should reduce some of the friction associated with new releases.
2018-08-05 20:47:06 +02:00
- Right-clicking is now allowed in the lobby. This makes it possible to activate blocks like buttons and levers.
- Snow and ice no longer melts in arenas.
Rewrite ThingParser usages. This commit changes how the ThingParser is used throughout the code base. Instead of blindly filtering out null values, we're now throwing a new InvalidThingInputString exception. This exception is caught in an outer scope that has more context. The exception is then unwrapped and rethrown as a ConfigError with the additional context. In the outermost scope of (re)loading the config-file, the ConfigError is caught and printed, and then (re)loading stops gracefully. We still need a proper way to handle loads/reloads consistently to get rid of the default command usage message, but this is a good step towards better usability in the face of user errors. Fixes #478
2018-08-05 22:48:35 +02:00
- Much of the parsing logic has been rewritten so that MobArena now logs more user-friendly errors when it encounters invalid values in the config-file.
Refactor startup logic. This commit re-implements and rearranges a lot of the logic in the main plugin class. It also removes the ConfigCommand class and moves its functionality into the CommandHandler to allow for reloads to be a bit more special than normal commands. In the refactoring of the main class, the startup logic is broken up into two phases, setup and (re)load: - In the setup phase, we create the data folder, and the command handler, config serializer(s), plugin integrations, boss abilities, the global event listener, and metrics are initialized. The ArenaMaster is instantiated, but it isn't initialized. These are things that need to be set up just once and don't change on reloads. - In the (re)load phase, the config-file is loaded from disk, the global messenger is instantiated, the arena master is initialized (loads settings, classes, and arenas), the announcements file is loaded from disk along with the sign data/templates. These are things that we want to be reloadable. If anything goes wrong during these phases, we store the exception thrown. This puts MobArena into a state where it prints the exception message to anyone who types a non-reload MobArena command to bring attention to the error so it can be fixed.
2018-08-10 22:39:38 +02:00
- If MobArena fails to load due to config-file errors, it now enters a type of "error state". In this state, it responds to all commands (except for the reload command) with a short message explaining why it's disabled.
- It is now possible to reload config-files with `/ma reload`.
- The reload command now also reloads global settings, e.g. the global messenger prefix.
Allow armor stands in arenas and lobbies. This commit adds an event handler for the PlayerArmorStandManipulateEvent and cancels it if the arena protection is on, we aren't in edit mode, and the region contains the armor stand. The same logic applies to the armor stand damage event.
2018-08-11 00:16:21 +02:00
- Armor stands can now be placed in arenas and lobbies.
Update changelog with /ma ready command.
2018-08-19 11:05:00 +02:00
- The new command `/ma ready` (`/ma rdy` for short) can be used as an alternative to the iron block for readying up.
Include total experience in SetExperience step. It turns out that experience in Minecraft is split out on a couple of different variables, and they are only loosely coupled. Total experience, level, and level progress are three completely different variables that can be manipulated individually. This means that while 10 experience points from level 0 should bring you up to level 1 with a third of the experience bar full (level 0 to 1 takes 7 points, level 1 to 2 takes 9 points), simply setting the total points value to 10 won't automatically level you up. Using the Player#giveExp(int) method will, however, work this way.
2018-08-18 23:47:15 +02:00
- Total experience is now correctly stored, reset, and restored on arena join/leave. This fixes a potential bug where total experience could increase in the arena, but levels and progress would still get reset at arena end.
Bring keep-exp per-arena setting back. This setting was removed a long time ago, likely by "happy mistake" in a larger refactoring. When enabled, players are granted any collected experience during the arena session as a reward when they die or reach the final wave of the arena. Note that deliberately leaving the arena is not included here, because "leaving" an arena is a highly ambiguous and conditional concept at the time of this commit. Figuring out when and how the experience reward should be added is complicated, and unless someone puts in a request for it, I think it's enough that the "legitimate" reasons for getting the experience (honorable death and reaching the final wave) are covered. Closes #485
2018-08-19 00:48:56 +02:00
- The per-arena setting `keep-exp` returns. If enabled, any experience collected during an arena session is added as a reward on death or when the final wave is reached.
Make MASpawnThread logic cancellable. This commit changes how MASpawnThread is started. Instead of simply scheduling a task and letting it run whenever, we now explicitly tell it to stop when the arena ends. This matters, because if the scheduled task does not get cancelled, it will run at the scheduled time. MASpawnThread's run() method has an early return to stop whenever the arena isn't running, but with unlucky timing, it's possible to start a new arena session before the task runs again, meaning the same MASpawnThread keeps scheduling itself on the previous scheduling loop. Instead of this whacky approach, we now specifically have MASpawnThread track its own BukkitTask. Upon arena start, we instantiate a new MASpawnThread and call its start() method, which in turn schedules itself and stores a reference to the associated BukkitTask. Upon arena end, we call the MASpawnThread's stop() method, which explicitly calls the BukkitTask's cancel() method, effectively stopping/unscheduling the task. This fixes the (very) long-standing "double wave spawner" bug that we haven't been able to reproduce for so long. Hooray!
2018-08-19 18:47:42 +02:00
- Waves will no longer intermittently progress at double frequency in some arena sessions. This long-standing bug where waves progress at "double speed" has finally been fixed.
Add changelog. This, along with a (currently not committed) script to generate github releases and Spigot/DBO formatted release notes from this changelog, should reduce some of the friction associated with new releases.
2018-08-05 20:47:06 +02:00
Thanks to:
Update changelog with /ma ready command.
2018-08-19 11:05:00 +02:00
- Sait for adding the /ma ready command
Update Thanks in changelog. Thanks, kitty!
2018-08-24 19:44:23 +02:00
- PrinceIonia, Nesseley, and Diamond\_Cat for help with test of dev builds
Add changelog. This, along with a (currently not committed) script to generate github releases and Spigot/DBO formatted release notes from this changelog, should reduce some of the friction associated with new releases.
2018-08-05 20:47:06 +02:00
## [0.102] - 2018-07-05
- It is now possible to change which items are turned into wolf pets in the global-settings in the config-file.
- Ocelots can now be used as class pets by giving a class a raw fish. The item type can, just like with pet wolves, be configured in the global-settings of the config-file.
- The hellhounds setting has been removed. Sorry, fiery puppy lovers.
- Temporary permissions are now supported in the Things API. This means that temporary permissions can now be used in place of items, money, commands, etc. by using the prefix `perm:`. While this isn't particularly useful in and of itself, it does give way to other neat features...
- Upgrade waves now use the Things API. This means that it is now possible to grant economy money or run commands as upgrades for a class. Note that the previous "weapns upgrade" behavior no longer works - only armor upgrades replace existing items, while weapon upgrades are simply added to the inventory. The weapon replacement was a bit wonky and didn't always work as expected, so now it just works consistently by always adding instead of replacing.
- The give-all-items flag in Upgrade waves has been removed. Upgrade waves now always grant all items listed.
- The MobArena item syntax now supports named potion types and dye colors in addition to the numeric values.
- Using numeric IDs for items and data values now results in a warning from MobArena, encouraging the use of equivalent string IDs instead. This should help prepare a bit for the changes in 1.13.
- In 1.8, splash potions are now denoted as splash_potion just like in 1.11 and up.
- Boss bars are now properly cleared from players that die or leave the arena during a boss fight.
- Scoreboards now correctly restore when leaving an arena that uses scoreboards.
- Potion effects are now correctly removed from players who switch from a class that has potion effects to a class that uses class chests but has no potion effects. This is a very specific edge case that probably affected no one, but at least it's fixed now.
- MobArena will now check the server version upon startup, and if the build is incompatible with the server version, it throws a more human-readable error. This should make it easier for people to spot if they accidentally downloaded the wrong build.
- The five default classes have been modernized with string IDs for all items, and a couple of them have been given starting potion effects. If you want to use the updated classes, you can find them in the github repo or you can let MobArena generate a new config-file and copy them over from there.
- A large portion of old setup have been removed. These commands all had extremely specialized functionality that required some semi-nasty coupling throughout the codebase, but none of them were necessary, since they mostly revolved around "shortcuts" to the config-file. By removing them, we now have a much easier path towards Minecraft 1.13 and awesome reworks in MobArena. The removed commands: `addclassperm`, `removeclassperm`, `listclassperms`, `setclassprice`, `setclass`, `removeclass`.
Thanks to:
- ArthurPendragon and other folks who contributed bug reports for the fixes in this version
- Nesseley for help with test of dev builds
## [0.101] - 2018-06-23
- MobArena now has bStats! This will greatly aid the development efforts in terms of figuring out which features are the most popular and which server implementations MobArena runs on. With this kind of data, the community can be involved in the development of the plugin by simply letting bStats speak for them. This "passive" involvement will allow us to trim away obsolete features and focus development efforts in areas that will benefit the most people.
- Join, leave, and info signs have been added. The signs can be used to display live information about an arena via a small templating engine.
- Bosses can now have their health displayed as a boss bar, a chapter title (on hit), or as a custom name. Note that boss bars are only available in 1.11+.
- Players can now dismount and re-mount their horses. Only the owner of a horse may mount it.
- Potion effects can now be added to classes.
- Potion effects can now be added to all wave types.
- The /ma config reload command now reloads the announcements-file (and the new sign templates file) along with the config-file.
- Player inventories are now correctly cleared when leaving the arena on Minecraft 1.8 servers.
Thanks to:
- NathanWolf for the initial pull request for join and leave signs
- PrinceIonia, Nesseley, and KyleGallacher for testing the dev builds
## [0.100.2] - 2018-05-13
- Vault is now optional again. In the previous patch (v0.100.1), Vault was accidentally made a requirement for MobArena to even start. This has been fixed.
- If Vault is not found, or if a compatible economy plugin is not found, MobArena now informs about this with an INFO message instead of a WARNING. However, if MobArena parses a money thing (like '$10') in this state, it will print an ERROR to the server log.
## [0.100.1] - 2018-05-04
- Fixed the plugin-wide economy bug introduced in v0.100. This bug would result in entry fees and class prices being "too expensive" for everyone regardless of balance, and economy rewards would not get paid out.
- Fixed a bug where entry fees weren't actually taken from players upon joining an arena.
- Fixed a bug where item/block entry fees couldn't be refunded. The items/blocks are now refunded *after* the player inventory has been restored, so the player inventory no longer overwrites the refunded items/blocks.
- Entry fees are now only refunded when leaving the arena while in the lobby. As soon as the arena starts, that price is paid, and there are no refunds.
## [0.100] - 2018-05-03
- MobArena now requires Java 8.
- The long-standing per-world inventory bug, by which players sometimes lose their inventories, has finally been fixed with a full rewrite of the join/leave process. It was discovered, however, that for the plugin PerWorldInventory, gamemode-specific inventories MUST be disabled. If not, PerWorldInventory will restore the gamemode-specific inventory after MobArena has already tried to take a backup of the existing inventory, and as a result, it will wipe it when the player leaves.
- Another long-standing bug, the `/back` command exploit, has also finally been fixed. It is no longer possible to use the `/back` command to get back into the arena after dying (unless the player is op or has the mobarena.admin.teleport permission).
- Class items and armor now support the Things API. This means that other plugins can now register simple parser interfaces to provide armor and items (which can be arbitrary things) to MobArena classes. One such plugin is Magic by Nathanwolf. Try it out!
- Item display names are now supported in reward strings, so custom items or named items will be displayed with the custom name if one is set.
- A hardcoded boss kill message has been split into two new announcments in the announcements-file, wave-boss-killed and wave-boss-reward-earned.
- Boss rewards are now granted again. This bug slipped through the cracks during the Things API rewrite.
- TNT placed from the off-hand now correctly depletes.
- The "My Items" class is now a little restricted to prevent some exploiting: ender pearls, ender chests, shulker boxes, and shulker shells are filtered out of the inventory within the arena (but the items are safely backed up with the rest of the player's items).
- A bug where using the /give command would hang the server and throw an error has been fixed.
- Arena names are now case insensitive in commands, meaning if your arena is called 'FirePit', you can type '/ma j firepit' (or even '/ma j FiRePiT') to join it.
- An error thrown when trying to restore scoreboards for disconnecting players has been fixed.
- Reloading config-files with the /ma config reload command is now MUCH faster (from over 10 seconds to under 100 milliseconds on some setups).
- The Things API has seen quite a few improvements. It is now possible for other plugins to register custom item parsers for use in the built-in item parser, making it even simpler to integrate with classes and rewards.
Thanks to:
- jwflory for porting and cleaning up documentation
- ctmartin for help with wrangling the build-up of github issues
- NathanWolf for help with improvements to the Things API
- Pugabyte for performance and permissions testing
- Nesseley, Sikatsu, and ScuroK for testing the inventory bug fix
- Swatacular for help with testing bug fixes
- Haileykins for contributions to the code base
Release 0.104.2.
2020-01-03 21:28:44 +01:00
[Unreleased]: https://github.com/garbagemule/MobArena/compare/0.104.2...HEAD
[0.104.2]: https://github.com/garbagemule/MobArena/compare/0.104.1...0.104.2
Release 0.104.1.
2019-12-31 23:27:49 +01:00
[0.104.1]: https://github.com/garbagemule/MobArena/compare/0.104...0.104.1
Release 0.104.
2019-08-09 00:04:06 +02:00
[0.104]: https://github.com/garbagemule/MobArena/compare/0.103.2...0.104
Release 0.103.2.
2019-04-23 11:21:44 +02:00
[0.103.2]: https://github.com/garbagemule/MobArena/compare/0.103.1...0.103.2
Release 0.103.1.
2018-12-31 15:33:06 +01:00
[0.103.1]: https://github.com/garbagemule/MobArena/compare/0.103...0.103.1
Release 0.103.
2018-08-28 22:00:59 +02:00
[0.103]: https://github.com/garbagemule/MobArena/compare/0.102...0.103
Add changelog. This, along with a (currently not committed) script to generate github releases and Spigot/DBO formatted release notes from this changelog, should reduce some of the friction associated with new releases.
2018-08-05 20:47:06 +02:00
[0.102]: https://github.com/garbagemule/MobArena/compare/0.101...0.102
[0.101]: https://github.com/garbagemule/MobArena/compare/0.100.2...0.101
[0.100.2]: https://github.com/garbagemule/MobArena/compare/0.100.1...0.100.2
[0.100.1]: https://github.com/garbagemule/MobArena/compare/0.100...0.100.1
[0.100]: https://github.com/garbagemule/MobArena/compare/0.99...0.100
Reference in New Issue Copy Permalink