![]() Only online players with the permission will be able to see the broadcast.-S for extra silent punishments. These flags can be used for bans, mutes, warnings, and kicks:-s for silent punishments. ![]() If the duration is not provided, a permanent ban will be placed. If the plugin is installed on Spigot, a server is represented by the 'servername' option in config.yml. The duration can be provided anywhere, even after the reason. Please note, some permissions values may be missing, however, these permissions should be similar to normal liteban's permissions. If display names are not enabled in the configuration or if the players display name is not available in the messages context, the players regular name will be used instead. Fixed short-format durations in the configuration specified in days (e.g. If a player has '', they will bypass these. The new duration limits: Code (Text): The highest limit matched by permissions will be used for duration limits. There was a check for this, but it didn't trigger as intended. Yes, the new duration limits also apply to IP bans and IP mutes. " BanBroadcast: "Player %1$s was banned by %2$s for %3$s duration: %4$s " MuteBroadcast: "Player %1$s was muted by %2$s for %3$s duration: %4$s " WarnBroadcast: "Player %1$s was warned by %2$s for %3$s " KickBroadcast: "Player %1$s was banned by %2$s for %3$s " Permissions: LiteBans has an easy to view web punishment history, theres heavy customization of messages, limitations of Staff permissions, network-sync, and even staff rollback for any punishments that occur. Fixed permitted players (via '/litebans allow') being able to join the server even if they have a ban matching their account directly. But this doesnt make sense since you have separate permissions for banning and temp-banning. When invoked via npx this adds another 300ms or so, so for faster startup, either. It supports the most popular spigot versions, starting from 1.7 up to the latest 1.19. There are also hover messages that show more information about punishments. All themes and colors have been tested and are 100 ready to use. " BanIPJoinMessage: "%s tried to join, but they were ipbanned. durations: Can be bypassed with the permission '' tempbanmax: 7 days I understand it is probably because the ban and tempban commands are the same command. The baseline startup time for a script is about 170ms seconds on my laptop. Customized LiteBans Messages designed for almost every server. Reason: %1$s Punished By: %2$s Duration: %3$s You may appeal your ban at BanJoinMessage: "%s tried to join, but they were banned. #See checkAlts: false #You should change this for each proxy running the server servername: litebans serveruuid: f15b78eda7294493b847f54b2005dd2e #Messages SilentPrefix: " " BanMessage: >- You have been banned on network. Feel free to raise a PR if you want this feature. But this doesn't make sense since you have separate permissions for banning and temp-banning. #This also is not supported on H2 stores. durations: Can be bypassed with the permission '' tempbanmax: 7 days I understand it is probably because the ban and tempban commands are the same command. : : class : at litebans.hM.b(hM.java:33) : at litebans.eC.d(eC.java:167) : at litebans.gk.a(gk.java:157) : at litebans.gF.a(gF.java:37) : at litebans.en.a(en.java:82) : at litebans.en.a(en.java:56) : at litebans.en.onCommand(en.java:38) : at (BukkitPlugin.java:232) : at .execute(PluginCommand.java:45) : at .dispatch(SimpleCommandMap.java:172) : at 1_16_R3.CraftServer.dispatchCommand(CraftServer.java:826) : at 1_16_R3.CraftServer.dispatchServerCommand(CraftServer.java:788) : at 1_16_R3.DedicatedServer.handleCommandQueue(DedicatedServer.java:483) : at 1_16_R3.DedicatedServer.b(DedicatedServer.java:450) : at 1_16_R3.MinecraftServer.a(MinecraftServer.java:1416) : at 1_16_R3.MinecraftServer.w(MinecraftServer.java:1142) : at 1_16_R3.MinecraftServer.lambda$a$0(MinecraftServer.java:293) : at java.base/(Thread.java:834) : An internal error occurred while attempting to perform this command.# What datastore to use # Options available: h2 (local), mysql store: h2 jdbcurl: "jdbc:mysql://localhost:3306/litebans?allowPublicKeyRetrieval=true " dbusername: "root " dbpassword: "password " #This statement may cause issues on MySQL 5.7 or MariaDB versions less than 10.2.2 #If it is, disable this option. I tried deleting all the files and having them re-created, but I still get this error. Java version: 11.0.6+10 (Java OpenJDK 11 HotSpot)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |