-
元素说明魔法值此方法仅供内部使用, 将被移除duration 现在为浮点数属性不再存在属性不再存在属性不再存在Upgraded / extended potions are now their own
PotionType
use them instead.removed in Minecraft 1.20.5. Do not use. Will be removed at a later date. Until then, this constant now acts as a reference toTag.ITEMS_BREAKS_DECORATED_POTS
which largely shares the same contents of the old "minecraft:tools" tag.
-
接口说明除材质本身之外, 本状态未提供有用的信息赞成使用
FishHook
滞留状态仅取决于药水物品/lingering status depends on only on the potion item.splash status depends on only on the potion item.tipped status depends only on base potion type not being UNCRAFTABLE and effects being empty.现在使用BiomeProvider
设置生物群系this API part has been replaced by thePersistentDataHolder
API. Please usePersistentDataHolder
instead of this.this API part has been replaced byPersistentDataHolder
. Please usePersistentDataAdapterContext
instead of this.please usePersistentDataType
as this part of the api is being replaced请勿使用, 该接口将被移除, 插件将无法运作请使用Consumer
only for backwards compatibility.
-
类说明仅为保障向后兼容性, EnchantmentWrapper 已不再使用chat previews have been removedUse the more generic
PlayerBucketEntityEvent
这个事件将被主线程触发,允许使用所有的 Bukkit API,不像AsyncPlayerChatEvent
.监听这个事件迫使聊天等待主线程,会导致聊天消息延迟展现。建议使用线程安全的
AsyncPlayerChatEvent
因客户端的改变(1.13更新较大幅度改善了命令输入的体验), 该事件不再触发. 1.13+版本可以参考:PlayerCommandSendEvent
这个事件使登录线程同步; 建议使用AsyncPlayerPreLoginEvent
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.所有关于MaterialData的用法已过时,并且将来会被移除. 请使用BlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.请使用SpawnEggMeta
all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.all usage of MaterialData is deprecated and subject to removal. UseBlockData
.Upgraded / extended potions are now their ownPotionType
use them instead.仅为保障向后兼容性, PotionEffectTypeWrapper 已不再使用.应使用Criteria
内定义的常量This class does not represent the structures of a world well. UseStructure
orStructureType
instead.
-
枚举说明将来 Minecraft 会有更多的可施法的生物不同的种类对应不同的类.不同猫种现在属于不同的生物/Cats are now a separate entity.classes are different types. This interface only remains in the Skeleton interface to preserve backwards compatibility.这个API被废弃了,具体见后面的网址,很快就要被移除了,就不深入解释了.This API is responsible for a large number of implementation problems and is in general unsustainable to maintain. It is likely to be removed very soon in a subsequent release. Please see this thread for more information.被
Team.OptionStatus
取代现在(Bukkit 1.13版本及以上)不同种类的头颅都有他们自己的常量了.已弃用, see usage methods for replacement(s)
-
注解说明This should generally not be used in any new API code as it suggests a bad API design.
-
字段说明unused, not intended to be APIunused, not intended to be APInot available since 1.20not available since 1.21Magic valueMagic valueMagic valueMagic valueMagic valueMagic valueMagic valueMagic valueMagic valueMagic valueMagic valueMagic valueMagic valueMagic valueUse
PersistentDataType.LIST
'sListPersistentDataTypeProvider.dataContainers()
instead asListPersistentDataType
s offer full support for primitive types, such as thePersistentDataContainer
.removed in Minecraft 1.20.5. Do not use. Will be removed at a later date. Until then, this constant now acts as a reference toTag.ITEMS_BREAKS_DECORATED_POTS
which largely shares the same contents of the old "minecraft:tools" tag.
-
方法说明不鼓励使用本 API, 建议使用传统克隆副本holdover from when this class was an enumholdover from when this class was an enumholdover from when this class was an enumholdover from when this class was an enumMagic valueMagic value属性现通过 key 区分该方法返回了一个形参化类的原始使用, 推荐使用带泛型参数的
BanList.getEntries()
魔法值不安全的参数不安全的参数不安全的参数only for internal use不安全的参数,请使用BaseSpawner.getSpawnedType()
.in favor ofDecoratedPot.getSherds()
不安全的参数不安全的参数A sign may have multiple writable sides now. UseSign.getSide(Side)
andColorable.getColor()
.告示牌现在多面可写. 请使用Sign.getSide(Side)
和SignSide.getLines()
.告示牌现在多面可写. 请使用Sign.getSide(Side)
和SignSide.getLines()
.请使用Sign.isWaxed()
A sign may have multiple writable sides now. UseSign.getSide(Side)
andSignSide.isGlowingText()
.A sign may have multiple writable sides now. UseSign.getSide(Side)
andColorable.setColor(org.bukkit.DyeColor)
.请使用Sign.isWaxed()
A sign may have multiple writable sides now. UseSign.getSide(Side)
andSignSide.setGlowingText(boolean)
.告示牌现在多面可写. 请使用Sign.getSide(Side)
和SignSide.getLines()
.请使用BlockData
请检查Material
类型请使用BlockData
请检查Material
类型不安全的参数由于玩家名在某个会话后(某次游戏后)不再唯一, 应使用uuid作为唯一标识来持久化存储用户. (译注:正版玩家更改它们的玩家名后,其uuid不会改变,其他正版玩家可以使用这些玩家的曾用名, 可能会出现同一玩家名对应两个或多个不同玩家的情况)Deprecated in favor ofBukkit.getSpawnLimit(SpawnCategory)
chat previews have been removedbiomes are now 3-dimensional不安全的参数biomes are now 3-dimensional魔法值魔法值自1.13版本, 权限消息对玩家执行的命令已不再可用, 因为没有执行相关命令的权限的客户端不知晓其存在性, 因此不会向服务端发送执行的命令. 此消息将只能在控制台上看到, 或命令使用Bukkit.dispatchCommand(CommandSender, String)
执行时也能看到.自1.13版本, 权限消息对玩家执行的命令已不再可用, 因为没有执行相关命令的权限的客户端不知晓其存在性, 因此不会向服务端发送执行的命令. 此消息将只能在控制台上看到, 或命令使用Bukkit.dispatchCommand(CommandSender, String)
执行时也能看到.This method only exists for backwards compatibility. It will do nothing and should not be used! Please useFileConfigurationOptions.getHeader()
instead.CallFileConfigurationOptions.parseComments()
instead.CallFileConfigurationOptions.parseComments(boolean)
instead.use getHeader() instead.use setHeader() instead不安全的参数不安全的参数不安全的参数不安全的参数不安全的参数魔法值魔法值不安全的参数legacy use only不安全的参数不安全的参数仅为保障作向后兼容性, 请使用Registry.get(NamespacedKey)
instead这些附魔的命名简直糟透了,建议使用Enchantment.getByKey(org.bukkit.NamespacedKey)
.附魔分组现由标签管理, 而非分类这些附魔的命名简直糟透了, 建议使用Keyed.getKey()
.诅咒附魔不再是特殊的. 当且仅当附魔为Enchantment.BINDING_CURSE
或Enchantment.VANISHING_CURSE
时才会返回true附魔类型现由标签管理a function of the firing weapona function of the firing weapona function of the firing weapon insteaddifferent variants are different classesyou are required to spawn a different entity应检查这是什么类实例Must spawn a new subtype variant另请参阅Breedable.canBreed()
另请参阅Breedable.canBreed()
Upgraded / extended potions are now their ownPotionType
useAreaEffectCloud.getBasePotionType()
instead.Upgraded / extended potions are now their ownPotionType
useAreaEffectCloud.setBasePotionType(org.bukkit.potion.PotionType)
instead.Upgraded / extended potions are now their ownPotionType
useArrow.getBasePotionType()
instead.Upgraded / extended potions are now their ownPotionType
useArrow.setBasePotionType(org.bukkit.potion.PotionType)
instead.船是复杂的,其中许多方法不能在多个版本中正常的工作.船是复杂的,其中许多方法不能在多个版本中正常的工作.船是复杂的,其中许多方法不能在多个版本中正常的工作.建议使用Boat.getBoatType()
船是复杂的,其中许多方法不能在多个版本中正常的工作.船是复杂的,其中许多方法不能在多个版本中正常的工作.船是复杂的,其中许多方法不能在多个版本中正常的工作.船是复杂的,其中许多方法不能在多个版本中正常的工作.船是复杂的,其中许多方法不能在多个版本中正常的工作.only for backwards compatibility, useRegistry.get(NamespacedKey)
instead.useIterable.iterator()
.本功能不再存在(自1.17版本起)本功能不再存在(自1.17版本起)实体可能有多名乘客. 请使用Entity.getPassengers()
此方法仅供内部使用, 将被移除实体可能有多名乘客. 请使用Entity.addPassenger(org.bukkit.entity.Entity)
不安全的参数不安全的参数不安全的参数不安全的参数将来 Minecraft 会有更多的可施法的生物将来 Minecraft 会有更多的可施法的生物badly named method, returns the value ofFireball.getAcceleration()
Minecraft新版本中已无效果has no effect in newer Minecraft versionsonly for backwards compatibility, useRegistry.get(NamespacedKey)
instead.useIterable.iterator()
.应检测此实例是否为ElderGuardian
(entity instanceof ElderGuardian)必须生成新的ElderGuardian
请参阅ChestedHorse
请参阅ChestedHorse
人类现能双持, 请使用PlayerInventory
中更明确的方法Bukkit中目前还没有关于序列化实体的语义(格式)的良好定义. 请谨慎使用.Bukkit中目前还没有关于序列化实体的语义(格式)的良好定义. 请谨慎使用.人类现能双持, 请使用PlayerInventory
中更明确的方法Bukkit中目前还没有关于序列化实体的语义(格式)的良好定义. 请谨慎使用.Bukkit中目前还没有关于序列化实体的语义(格式)的良好定义. 请谨慎使用.由于现已支持多个同种类型的药水效果, 没必要强制添加.译注:在某次版本更新后, Minecraft 自身支持了多个同种药水效果, 效果弱的会被隐藏; 但为兼容性考虑, 如确有覆盖效果需求的, 还是指定force为true
实体分组现在由标签管理,而不是类别猫现在是单独的实体猫现在是单独的实体不安全的参数不安全的参数seeAgeable.setBaby()
andAgeable.setAdult()
Misleading name. This method also returns the location of respawn anchors.This value is controlled only by the client and is therefore unreliable and vulnerable to spoofing and/or desync depending on the context/time which it is accessed不安全的参数不安全的参数不安全的参数suppressLightUpdates is not functional in versions greater than 1.19.4API行为有所改变Misleading name. This method sets the player's respawn location more generally and is not limited to beds.Misleading name. This method sets the player's respawn location more generally and is not limited to beds.Minecraft已经不使用材质包了,应该用Player.setResourcePack(String)
设置资源包(额这不是一个意思么..).不起任何作用不起任何作用only for backwards compatibility, useRegistry.get(NamespacedKey)
instead.useIterable.iterator()
.only for backwards compatibility, useRegistry.get(NamespacedKey)
instead.useIterable.iterator()
.seeAgeable.setBaby()
andAgeable.setAdult()
另请参阅Ageable.isAdult()
检查 instanceofZombieVillager
的是与否.must spawnZombieVillager
.不安全的参数由于史莱姆方块的特性, 这个方法是不准确的因为它不包含史莱姆方块粘走的方块, 如MC版本低于1.8请无视此句.not all cauldron contents are Levellednot all cauldron contents are Levellednot all cauldron contents are Levelled在较新版本的Minecraft(1.13及以上)无效在较新版本的Minecraft(1.13及以上)无效duration 现在为浮点数not currently functional马的跳跃行为被移动到了客户端horse jumping was moved client side.MC 1.14 has changed how villagers restock their trades. UseMerchantRecipe.getUses()
.MC 1.14 has changed how villagers restock their trades. This has no effect anymore.This changes the ItemStack in their hand before any calculations are applied to the Inventory, which has a tendency to create inconsistencies between the Player and the server, and to make unexpected changes in the behavior of the clicked Inventory.这个方法使用了来自PlayerPreLoginEvent
的已弃用的枚举这个方法使用了来自PlayerPreLoginEvent
的已弃用的枚举这个方法使用了来自PlayerPreLoginEvent
的已弃用的枚举该方法无法保证在每个版本上的效果书可能被副手签名This event has two possible cancellation states, one forPlayerInteractEvent.useInteractedBlock()
and one forPlayerInteractEvent.useItemInHand()
. It is possible a call might have the former false, but the latter true, eg in the case of using a firework whilst gliding. Callers should check the relevant methods individually.chat previews have been removed魔法值魔法值biomes are now 3-dimensionalbiomes are now 3-dimensionalUses magic valuesChunkGenerator.ChunkData
are now directly providedThe generation is now split up and the new methods should be used, seeChunkGenerator
the chunk generation code should be thread safehas no effect, bedrock generation is part of the surface step, seeChunkGenerator.shouldGenerateSurface()
魔法值魔法值不安全的参数不安全的参数现在实体可以双持, 所以需要特定的方法来获取指定的手现在实体可以双持, 所以需要特定的方法来设置指定的手现在实体可以双持, 所以需要特定的方法来获取指定的手现在实体可以双持, 所以需要特定的方法来设置指定的手for internal compatibility use onlyMagic value不安全的参数耐久度现在是 ItemMeta 的一部分. 为避免疑虑和误用, 请使用ItemStack.getItemMeta()
,ItemStack.setItemMeta(ItemMeta)
和Damageable.setDamage(int)
. 这是因为在调用此方法之前创建的 ItemMeta 的后续变动将覆盖调用此方法设置的物品元数据.only for internal usecreative categories no longer exist on the server该 API 已被PersistentDataHolder
API 取代. 请使用PersistentDataHolder.getPersistentDataContainer()
.属性不再存在属性不再存在属性不再存在本方法没有预期效果, 这实际上是ItemMeta.getLocalizedName()
的别名这些方法是设计糟糕的API:它们依赖调用者, 仅传递一个整数属性值, 并且曾经有着糟糕的实现 - 未判断地图 id 是否合法(是否存在). 现代的实现 - 例如, 服务器会生成一个不同 id 的新地图. 开发者应使用 xxxMapView 家族的方法.本方法没有预期效果, 这实际上是ItemMeta.hasLocalizedName()
的别名这些方法是设计糟糕的API:它们依赖调用者, 仅传递一个整数属性值, 并且曾经有着糟糕的实现 - 未判断地图 id 是否合法(是否存在). 现代的实现 - 例如, 服务器会生成一个不同 id 的新地图. 开发者应使用 xxxMapView 家族的方法.本方法没有预期效果, 这实际上是ItemMeta.setLocalizedName(String)
的别名这些方法是设计糟糕的API:它们依赖调用者, 仅传递一个整数属性值, 并且曾经有着糟糕的实现 - 未判断地图 id 是否合法(是否存在). 现代的实现 - 例如, 服务器会生成一个不同 id 的新地图. 开发者应使用 xxxMapView 家族的方法.Upgraded / extended potions are now their ownPotionType
usePotionMeta.getBasePotionType()
instead.Upgraded / extended potions are now their ownPotionType
usePotionMeta.setBasePotionType(org.bukkit.potion.PotionType)
instead.另请参阅SkullMeta.getOwningPlayer()
..不同实体类型对应不同的刷怪蛋物品不同实体类型对应不同的刷怪蛋物品players can duel wield now use the methods for the specific hand insteadplayers can duel wield now use the methods for the specific hand insteadfor compatibility onlyMagic valueMagic valueMagic valueMagic valueMagic valueno longer functionalno longer functional魔法值, 请使用MapCanvas.getPixelColor(int, int)
不安全的参数不安全的参数Magic valueMagic valueonly for backwards compatibility, useRegistry.get(NamespacedKey)
instead.useIterable.iterator()
.Magic valueMagic valueMagic valueMagic valueMagic valueMagic valueMagic valueMagic valueMagic valueMagic value不应使用此方法;请使用hinge/facing对应的getterMagic value不安全的参数不安全的参数目前还没有一个与底层服务器联系紧密的 实现。欢迎贡献.(如果你有idea,请左转Spigot Stash贡献你的代码)不安全的参数不安全的参数该方法创建了一个堆叠数为0的物品堆,一般没什么用. 请考虑MaterialData.toItemStack(int)
.Use MushroomBlockType cap optionsMagic value现存储在SpawnEggMeta
.现存储在SpawnEggMeta
.Magic valueMagic valueMagic valueMagic value不安全的参数不安全的参数UseRegistry.get(NamespacedKey)
instead.useIterable.iterator()
.插件应永不使用此方法, 仅供内部使用!!不安全的参数不安全的参数不安全的参数不安全的参数不安全的参数误导性的方法名称. 此方法也同时返回复活锚点的位置not an API methodnot an API methodunused时长延长/升阶的药水已经有其专属的PotionType
. 请使用PotionType.getPotionEffects()
无任何作用现在粒子效果颜色不属于药水效果的一部分魔法值仅为保障向后兼容性, 请使用Registry.get(NamespacedKey)
仅为保障向后兼容性, 请使用Registry.get(NamespacedKey)
未被使用, 总是 1.0魔法值仅为保障向后兼容性, 请使用Keyed.getKey()
请使用Iterable.iterator()
.有误导性Potions can have multiple effects usePotionType.getPotionEffects()
PotionType can have multiple effects, some of which can be instant and others not. UsePotionEffectType.isInstant()
in combination withPotionType.getPotionEffects()
andPotionEffect.getType()
魔法值魔法值这个名称具有误导性.因为它没有执行“同步”任务.而是“异步”任务这个名称具有误导性.因为它没有执行“同步”任务.而是“异步”任务这个名称具有误导性.因为它没有执行“同步”任务.而是“异步”任务计分板可包含非玩家项目计分板可包含非玩家项目计分板可包含非玩家项目计分板可包含非玩家项目计分板可包含非玩家项目应明确指定计分项的显示名计分板可包含非玩家项目队伍可包含非玩家项目队伍可包含非玩家项目队伍可包含非玩家项目队伍可包含非玩家项目不安全的参数由于玩家名在某个会话后(某次游戏后)不再唯一, 应使用uuid作为唯一标识来持久化存储用户. (译注:正版玩家更改它们的玩家名后,其uuid不会改变,其他正版玩家可以使用这些玩家的曾用名, 可能会出现同一玩家名对应两个或多个不同玩家的情况)chat previews have been removed不安全的参数不安全的参数only for backwards compatibility, old enums can not be compared.only for backwards compatibility.only for backwards compatibility, it is not guaranteed that an old enum always has the same ordinal.不安全的参数不安全的参数this method does not handle tile entities (bee nests)1.15更新后生物群系已三维化1.15更新后生物群系已三维化使用GameRule.SPAWN_CHUNK_RADIUS
以更好地控制1.15更新后生物群系已三维化Deprecated in favor ofWorld.getTicksPerSpawns(SpawnCategory)
Deprecated in favor ofWorld.getTicksPerSpawns(SpawnCategory)
Deprecated in favor ofWorld.getTicksPerSpawns(SpawnCategory)
Deprecated in favor ofWorld.getSpawnLimit(SpawnCategory)
Deprecated in favor ofWorld.getSpawnLimit(SpawnCategory)
world type is only used to select the default word generation settings and is not stored in Vanilla worlds, making it impossible for this method to always return the correct value.本方法曾被添加用于促进区块的垃圾回收. 由于当前 Minecraft 的区块被严格管理, 并且除非那些区块正被使用, 否则不会加载超过1tick时长 (意思是mc现在对区块管理更好了, 不用的区块会被及时卸载并回收)这个方法不能保证在所有的客户端接口都正常地工作。无法保证重新生成单个区块会产生与之前相同的区块, 因为地形装饰可分布在区块上. 应避免使用本方法, 由于已知本方法易产生bug1.15更新后生物群系已三维化使用GameRule.SPAWN_CHUNK_RADIUS
以更好地控制Deprecated in favor ofWorld.setTicksPerSpawns(SpawnCategory, int)
Deprecated in favor ofWorld.setTicksPerSpawns(SpawnCategory, int)
Deprecated in favor ofWorld.setTicksPerSpawns(SpawnCategory, int)
Deprecated in favor ofWorld.setTicksPerSpawns(SpawnCategory, int)
Deprecated in favor ofWorld.setSpawnLimit(SpawnCategory, int)
Deprecated in favor ofWorld.setSpawnLimit(SpawnCategory, int)
不安全的参数sound is now client side and cannot be removedsound is now client side and cannot be removed
-
构造器说明仅供内部使用, 将被移除options requiredoptions requiredorg.bukkit.event.player.PlayerBucketEmptyEvent
(Player, Block, Block, BlockFace, Material, ItemStack) 该方法使用了意义不明确的data byte对象Recipes must have keys. UseShapedRecipe(NamespacedKey, ItemStack)
instead.as of Minecraft 1.20, smithing recipes are now separated into two distinct recipe types,SmithingTransformRecipe
andSmithingTrimRecipe
. This class now acts as a base class to these two classes and will do nothing when added to the server.不安全的参数Magic valueMagic valueMagic value不安全的参数Magic valueMagic value不安全的参数Magic valueMagic value不安全的参数Magic valueMagic valueMagic valueMagic valueMagic valueMagic value遗留的旧API,相当于newDoor(Material.LEGACY_WOODEN_DOOR);
不安全的参数Magic value不安全的参数Magic valueMagic value不安全的参数Magic valueMagic valueMagic valueMagic valueMagic valueMagic valueMagic value不安全的参数Magic valueMagic valueMagic valueMagic valueMagic valueMagic valueMagic valueMagic value不安全的参数Magic valueMagic valueMagic valueMagic valueMagic valueMagic valueMagic valueMagic valueMagic value不安全的参数不安全的参数Magic value不安全的参数Magic valueMagic valueMagic valueMagic valueMagic valueMagic valueMagic valueMagic valueMagic value不安全的参数不安全的参数
-
枚举常量说明被
BanList.Type.PROFILE
取代不复存在不复存在不复存在不复存在不复存在不复存在不复存在不复存在不复存在不复存在原版中该适用目标不复存在已分为单独的效果已分为单独的效果不再调用, 区块与已经存在的实体一同生成. 请考虑使用ChunkLoadEvent.isNewChunk()
和Chunk.getEntities()
以达到类似效果all plugins are now assumed to be UTF-8 aware.