Spigot Logger | 1.7 ~ 1.19 1.8

Log all Activities from Players and Server Side on both Bukkit and Proxy instances!

  1. Added! :D
  2. Prism3 updated Logger with a new update entry:

    1.6.4 // Fixed all issues related to Player Commands, Checkers etc...

    Read the rest of this update entry...
  3. Prism3 updated Logger with a new update entry:

    1.6.5 // Bug Fixes, some improvements and additions

    Read the rest of this update entry...
  4. Prism3 updated Logger with a new update entry:

    1.7 // BungeeCord + messages.yml Files additions and more...

    Read the rest of this update entry...
  5. You ACTUALLY compared my lightweight-intended plugin to a goddamn 11MB bloated logger? Is you has an brains?
    • Funny Funny x 1
  6. Dont work on 1.8 servers
  7. Hello, I fixed that issue, it will be released soon. You can fix it however by deleting the emojis in the messages.yml file. Seems that >12 servers don't like having emojis xD
  8. Hi! Could you add more settings for ingame chat?
    CommandSpy is a good idea, but there would be a need for other settings as well!

    AnvilSpy, BookSpy, SignSpy, etc... These would be most in demand.
  9. Hello, could you elaborate more? If you have examples that would be great!
  10. upload_2021-12-13_13-36-5.png
    I alluded to that. It could be with several settings.


    Unfortunately, I only find old obsolete extensions for such purposes.
    So since this plugin already exists by default, I thought I'd suggest it here.

    The point is to not only save the data to a file, but also publish it for ingame chat.

    Here's an old extension: https://www.spigotmc.org/resources/jspy.14968/

  11. Yeah sounds about right, Your suggestion has been added to our list of ideas to be accomplished. It shall be present in the next release!
    • Agree Agree x 1
  12. Hi there! I really love your plugin but would like to suggest one feature. Perhaps add a blacklist for console commands so we can exclude the /list command, which multicraft tends to spam all the time.
    • Agree Agree x 1
  13. Sure thing! :D
    • Winner Winner x 1
    • Like Like x 1
  14. No problem, anything else just suggest :D
  15. Getting errors after I updated to the most recent version. (I use paper 1.18.1)
    Code (Text):

    17.01 02:22:03 [Server] WARN An error occurred while logging into the appropriate file.
    17.01 02:22:03 [Server] WARN java.io.FileNotFoundException: plugins/Logger/Logs/Block Break/17-01-2022.log (No such file or directory)
    17.01 02:22:03 [Server] WARN at java.base/java.io.FileOutputStream.open0(Native Method)
    17.01 02:22:03 [Server] WARN at java.base/java.io.FileOutputStream.open(FileOutputStream.java:293)
    17.01 02:22:03 [Server] WARN at java.base/java.io.FileOutputStream.<init>(FileOutputStream.java:235)
    17.01 02:22:03 [Server] WARN at java.base/java.io.FileWriter.<init>(FileWriter.java:113)
    17.01 02:22:03 [Server] WARN at Logger-1.7.1.jar//com.carpour.logger.Events.OnBlockBreak.onBreak(OnBlockBreak.java:90)
    17.01 02:22:03 [Server] WARN at com.destroystokyo.paper.event.executor.asm.generated.GeneratedEventExecutor109.execute(Unknown Source)
    17.01 02:22:03 [Server] WARN at org.bukkit.plugin.EventExecutor.lambda$create$1(EventExecutor.java:69)
    17.01 02:22:03 [Server] WARN at co.aikar.timings.TimedEventExecutor.execute(TimedEventExecutor.java:80)
    17.01 02:22:03 [Server] WARN at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:70)
    17.01 02:22:03 [Server] WARN at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:628)
    17.01 02:22:03 [Server] WARN at net.minecraft.server.level.PlayerInteractManager.a(PlayerInteractManager.java:400)
    17.01 02:22:03 [Server] WARN at net.minecraft.server.level.PlayerInteractManager.a(PlayerInteractManager.java:354)
    17.01 02:22:03 [Server] WARN at net.minecraft.server.level.PlayerInteractManager.a(PlayerInteractManager.java:314)
    17.01 02:22:03 [Server] WARN at net.minecraft.server.network.PlayerConnection.a(PlayerConnection.java:1762)
    17.01 02:22:03 [Server] WARN at net.minecraft.network.protocol.game.PacketPlayInBlockDig.a(PacketPlayInBlockDig.java:34)
    17.01 02:22:03 [Server] WARN at net.minecraft.network.protocol.game.PacketPlayInBlockDig.a(PacketPlayInBlockDig.java:8)
    17.01 02:22:03 [Server] WARN at net.minecraft.network.protocol.PlayerConnectionUtils.lambda$ensureRunningOnSameThread$1(PlayerConnectionUtils.java:56)
    17.01 02:22:03 [Server] WARN at net.minecraft.server.TickTask.run(TickTask.java:18)
    17.01 02:22:03 [Server] WARN at net.minecraft.util.thread.IAsyncTaskHandler.c(IAsyncTaskHandler.java:149)
    17.01 02:22:03 [Server] WARN at net.minecraft.util.thread.IAsyncTaskHandlerReentrant.c(IAsyncTaskHandlerReentrant.java:23)
    17.01 02:22:03 [Server] WARN at net.minecraft.server.MinecraftServer.b(MinecraftServer.java:1413)
    17.01 02:22:03 [Server] WARN at net.minecraft.server.MinecraftServer.c(MinecraftServer.java:189)
    17.01 02:22:03 [Server] WARN at net.minecraft.util.thread.IAsyncTaskHandler.y(IAsyncTaskHandler.java:122)
    17.01 02:22:03 [Server] WARN at net.minecraft.server.MinecraftServer.bf(MinecraftServer.java:1391)
    17.01 02:22:03 [Server] WARN at net.minecraft.server.MinecraftServer.y(MinecraftServer.java:1384)
    17.01 02:22:03 [Server] WARN at net.minecraft.util.thread.IAsyncTaskHandler.c(IAsyncTaskHandler.java:132)
    17.01 02:22:03 [Server] WARN at net.minecraft.server.MinecraftServer.a(MinecraftServer.java:1462)
    17.01 02:22:03 [Server] WARN at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:1264)
    17.01 02:22:03 [Server] WARN at net.minecraft.server.MinecraftServer.lambda$spin$0(MinecraftServer.java:317)
    17.01 02:22:03 [Server] WARN at java.base/java.lang.Thread.run(Thread.java:833)
  16. Hello, it's giving this error because the Block Break file can not be found

    If the error persists, try and delete de Logs folder
  17. Hmm, can u add logger.spy.bypass permission?
    The point is, I want to check the staff members in the game as well.

    It would look something like this:
    logger.spy - With this right, we can also see ourselves and the players who have this right.
    logger.spy.bypass - Those with this right who have an exception to the Spy options will not be able to see it.
    #59 ColorsASD, Jan 18, 2022
    Last edited: Jan 18, 2022
  18. Looks that you have a serious spy issue there haha

    Yeah sure, will do in the next update
    • Like Like x 1