md678685
c29599d39a
Create .travis.yml
2018-10-09 19:34:07 +01:00
md678685
692e0adde4
Use MONSTER_EGG in SpawnEggRefl
2018-09-09 16:37:02 +01:00
md678685
cdba518bae
Revert "Implement 1.13 item support ( #2153 )"
2018-09-09 16:35:20 +01:00
md678685
b70b67fa1f
Remove unnecessary CraftBukkit dependency
2018-09-09 16:34:15 +01:00
md678685
ff0ca9bc7b
Remove unnecessary CraftBukkit dependency
2018-09-05 19:20:18 +01:00
md678685
320bc25d94
Implement 1.13 item support ( #2153 )
...
Uses two distinct providers to support items on 1.13 while falling back to `items.csv` for previous versions of Minecraft.
2018-09-05 14:23:16 +01:00
md678685
425e955b5d
Update items.json
...
Add some more aliases to the file
2018-09-05 14:19:09 +01:00
pop4959
33ae9a2597
Fix TropicalFish spawning ( #2159 )
...
The name can't have a space in it or it won't be matched by any commands.
2018-09-05 13:26:33 +01:00
pop4959
19913d3612
Implement abstract method Entity::getFacing in OfflinePlayer ( #2157 ) @pop4959
...
Allows EssentialsX to compile against the latest Spigot version.
Reference: [8ab814cd5c
2018-09-05 11:00:27 +01:00
pop4959
a3eb58724f
Add a way to use unsafe nicknames ( #2152 ) @pop4959
...
Pretty much what the title says. Closes #1630 .
This is a fun little feature that I'm sure many people have always wanted. I can understand that the original authors of Essentials were probably concerned about users entering names that cannot display correctly in the chat, and that is understandable.
I have added a new permission "essentials.nick.allowunsafe", which must be given to anyone who is allowed to use characters outside of the alphanumeric set. The name of the permission is inspired from "essentials.enchantments.allowunsafe", which allows unsafe enchantment levels to be applied to items without guaranteed behaviour. Similarly, the permission "essentials.nick.allowunsafe" allows unsafe characters to be entered for the user's nickname without making any guarantee that those characters will show up in chat correctly.
2018-09-02 12:14:26 +01:00
md678685
0afa00779c
Add some comments to LegacyItemDbProvider
2018-09-01 19:31:32 +01:00
md678685
17d5545804
Update items.json
...
Fix incorrect type for Uncraftable Potions
2018-09-01 16:46:55 +01:00
md678685
cd70662f01
Update items.json
...
Fixes some potions spawning incorrectly where the vanilla name didn't match the Bukkit enum name
2018-09-01 16:27:28 +01:00
md678685
a89c97409b
Use potion data when looking up items
2018-09-01 15:48:14 +01:00
md678685
102cb6d949
Merge branch '1.13' into 1.13-items
2018-09-01 10:46:27 +01:00
md678685
6c9c9ad42a
Use enum methods throughout plugin for cross-version enum lookups
2018-09-01 10:35:08 +01:00
md678685
acbc96fd55
Add enum utility helpers for Statistic and Material
2018-09-01 10:34:11 +01:00
md678685
ca721c1acb
Add V1_13_R2 to ReflUtil
2018-08-27 21:29:30 +01:00
md678685
3bf669c42a
ItemDbProvider#resolve returns ItemData
...
More useful than just returning the Material.
2018-08-27 21:21:06 +01:00
md678685
cdc5f75fcb
Remove unnecessary equals method on abstract ItemData
2018-08-27 21:19:36 +01:00
md678685
d74f19970b
Strip out legacy ItemDb code, pt 1928371236123897
2018-08-27 21:19:15 +01:00
md678685
2ddde37771
Improve FlatItemData#equals
2018-08-27 21:02:27 +01:00
md678685
c1c422e03d
Update items.json
2018-08-27 21:00:57 +01:00
md678685
7608b7d658
Merge branch '1.13' into 1.13-items
2018-08-27 20:01:48 +01:00
md678685
d1d5ae814f
Merge branch '2.x' into 1.13
2018-08-27 20:01:01 +01:00
md678685
452fa61717
Change tryProvider test values
2018-08-27 19:58:19 +01:00
md678685
825f697fd2
Update items.json
2018-08-27 19:30:05 +01:00
md678685
4ea71ae88e
Implement missing methods in FakeWorld
2018-08-27 14:10:06 +01:00
md678685
bdb32f5878
Bump Bukkit version to 1.13.1
2018-08-27 13:10:15 +01:00
md678685
e3c726b8f6
Log total loaded items on reload
2018-08-27 13:06:27 +01:00
md678685
96c6c7b1ca
Add per-provider implementations of ItemData
2018-08-27 11:23:47 +01:00
md678685
634d62f9ef
Fix typo in /kickall
2018-08-27 10:30:29 +01:00
md678685
2806156cf4
Add "allow-world-in-broadcastworld" option
...
Allows players to send broadcasts to a specified world by running `/broadcastworld [world] <message>` if enabled.
This is disabled by default in old configs to avoid confusion between updates.
2018-08-27 10:26:54 +01:00
md678685
e642192461
Kick players in /banip
...
The four-year-old to-do has finally been done!
Closes #2143 .
2018-08-26 22:54:00 +01:00
md678685
959c788f22
Don't kick exempt players when running /kickall
2018-08-26 21:03:17 +01:00
montlikadani
cda520589a
Revert "Doesn't kick all players if the player has permission ( #2145 ) @montlikadani"
...
This reverts commit 5c1db129d3
2018-08-26 20:59:46 +01:00
montlikadani
5c1db129d3
Doesn't kick all players if the player has permission ( #2145 ) @montlikadani
...
So, if a player has permission (eg, an operator or more), they will not kick them out because of permission.
2018-08-26 20:13:05 +01:00
Leomixer17
c718962426
Update messages_it.properties ( #2144 ) @Leomixer17
2018-08-26 17:07:05 +01:00
Thomas
575a11b645
Updated "createKitSuccess=" ( #2133 ) @DutchUser
...
* Updated "createKitSuccess="
They have the old one, its now in the "kits.yml" not in "config.yml"
* Update messages_da.properties
* Update messages_de.properties
* Update messages_es.properties
* Update messages_en.properties
* Update messages_et.properties
* Updated "createKitSuccess="
* Updated "createKitSuccess="
* Updated "createKitSuccess=
* Updated "createKitSuccess=
* Updated "createKitSuccess=
* Updated "createKitSuccess=
* Updated "createKitSuccess="
* Updated "createKitSuccess="
* Updated "createKitSuccess="
* Updated "createKitSuccess="
* Updated "createKitSuccess="
* Updated "createKitSuccess="
* Updated "createKitSuccess="
* Updated "createKitSuccess="
* Updated "createKitSuccess="
* Updated "createKitSuccess="
* Update messages_vi.properties
Going add the other later today,
* invalidItemFlagMeta
* noJailsDefined
* openingDisposal
* socialSpyMsgFormat
* socialSpyMutedPrefix
* tempbanJoin
* whoisUuid
* Update messages_vi.properties
* Update messages_vi.properties @md678685
I have no idea why this whole file is in `\u` codes
* Update messages.properties @md678685
2018-08-26 16:12:13 +01:00
Xeyame
f97c5fc1ff
Make /realname configurable ( #1952 ) @Xeyame
...
Closes #1810 .
@md678685: I've added colour codes to the `realName` messages by default, which was not originally part of this PR.
2018-08-26 15:39:37 +01:00
montlikadani
81397d98b8
Added editable messages ( #2072 ) @montlikadani
...
**If it is accepted then I will add it to the other message files.**
2018-08-26 15:17:07 +01:00
Leomixer17
82b2ff0b3f
Update messages_it.properties ( #2142 ) @Leomixer17
2018-08-26 15:13:33 +01:00
md678685
05fcb7b1aa
Refactor to allow items to be added after first load
2018-08-25 18:38:50 +01:00
md678685
c79db98978
Add more debug logging to Settings ( #2140 )
...
Adds debug logging for `getChatFormat` and `getCommandCooldownEntry`, which makes it much easier to track down issues with group formats in EssentialsX Chat and command cooldowns respectively.
2018-08-25 18:09:08 +01:00
md678685
303aa77901
Add missing import
2018-08-25 16:55:12 +01:00
md678685
65a4ef7ee5
Use items that actually exist in tryProvider
2018-08-25 16:54:50 +01:00
md678685
1be7fbd8a6
Remove hash comment when rebuilding JSON database
2018-08-25 16:54:09 +01:00
Max Roncace
935b5cfe0f
Fix unbreakable attribute for kits ( #2071 ) @caseif
...
This PR fixes the `unbreakable` attribute on kit items. Previously, Essentials was exclusively using an internal Spigot method to set this on `ItemMeta` objects; however, this solution seems to be non-functional on more recent Spigot builds (1.12.2).
I have altered the `MetaItemStack#setUnbreakable` method to use the native Bukkit method, available for [some time now](https://hub.spigotmc.org/stash/projects/SPIGOT/repos/bukkit/commits/d986a3f ), by default. Essentials will still use the old solution as a fallback in case of an older Bukkit version which does not have native support for the attribute.
2018-08-25 11:33:17 +01:00
md678685
bad02729db
Allow /eco take to subtract a user's exact balance
2018-08-24 15:42:17 +01:00
md678685
80f7ded687
SPECTATOR mode is safe for teleporting everywhere. ( #2049 )
...
Teleporting in spectator mode is as safe as creative mode for every target.
2018-08-24 15:24:26 +01:00
