Spyon [Unmaintained]

Discussion in 'Plugin Support' started by sqroot, Feb 8, 2016.

  1. sqroot submitted a new resource:

    Spyon - Logs console and chat command usage for both ingame users and RCON

    Read more about this resource...
     
  2. sqroot updated Spyon with a new update entry:

    1.0.1

     
  3. log Player
    inventory.giveid "1983936587" "1"
    What does this mean?
     
  4. v3x

    v3x

    Can this be set to show only admins/mods commands in chat? I'm a server owner and would like it to announce when my guys are using their commands. Thank you. +1 like
     
  5. set "authlevel": 2, in Spyon.json
     
  6. That's an item id. It means that somebody gave himself one entity of the item with the id 1983936587.
    You can compare the IDs here:
    Rust

    Do you want to log the commands of everyone and show only admin/moderator commands in chat?
    When authlevel is set to 1 and public is set to true, the commands of both admins and moderators are logged and broadcasted to the chat.
    When authlevel is set to 2 and public is set to true, only the commands of admins are logged and broadcasted to the chat.
     
  7. @sqroot Getting errors with conf, whats wrong? Also if I add "/kick" and someone does /kick NAME will it log?
    Code:
    {
      "authlevel": 1,
      "chatcmds": [
        "/remove admin",
        “/kick”,
        “/ban”,
        “/mute”,
        “/give”,
        “/spectate”,
        “/god”,
        “/tp”,  
        "/remove all"
      ],
      "cmds": [
        "global.setinfo",
        "global.kick",
        "global.kickall",
        "global.unban",
        "global.mutevoice",
        "global.unmutevoice",
        "global.mutechat",
        "global.unmutechat",
        "global.spectate",
        "global.teleport",
        "global.teleport2me",
        "global.teleportany",
        "inventory.give",
        "inventory.giveall",
        "inventory.givebpall",
        "inventory.giveto",
        "inventory.givearm",
        "inventory.giveid",
        "inventory.givebp",
        "heli.drop",
        "heli.calltome",
        "heli.call",
        "heli.strafe"
      ],
      "public": false
    }
     
    Last edited by a moderator: Jun 19, 2016
  8. Config doesn't appear to be wrong, what error are you getting?
     
  9. Idk now :/ but it spammed my server and froze it
     
  10. It shouldn't spam the server much since the plugin is only called when a command is called.
    Check the file Log.Error.txt in your server identity folder. All errors are logged to that file.
    It'd be great if you could find the error so I can fix whatever error you encountered.
    [DOUBLEPOST=1455122587,1455101000][/DOUBLEPOST]Nevermind, I found out why it doesn't work.
    The quotation marks you used in your config are no quotation marks parsable by Oxide.
    You used: “ (Unicode: 0x201C)
    You should use: " (Unicode: 0x22)
    The same goes for closing quotation marks.

    Do not edit configs with something that is not a basic text editor like Notepad, Sublime Text or Notepad++.
    Editing configs with word editors or similar tools can cause lots of issues, for every plugin.
     
    Last edited by a moderator: Feb 10, 2016
  11. Hello @sqroot
    is there a way that a message comes up when typing a specific message? As example someone type
    #report

    that this player gets a message, that we received the message or something like that?
     
  12. You mean giving the players the ability to write to the log to report abusers?
    Sure, I can add that, but I'll have to limit it with a spam limit so users don't get direct, full access to something that is logged (this could be very easily abused, for instance to fill the server HDD).
    [DOUBLEPOST=1455899421,1455815458][/DOUBLEPOST]Actually, I've decided not to implement this, as it would just be a duplicate of what Tickets for Rust | Oxide accomplishes.
    Use Tickets instead for stuff like this.
     
  13. Hi sqroot,
    Nice plugin, I have just implemented it to track all /remove, /tpr, /tpa to help me to investigate raiders and bad clan mates using remove.
    I was wondering if you had thought about maybe creating a new log file for each day so old ones can be easily removed.
    The same way oxide creates a new log file each day.
    Thank you.
     
  14. Sure, I didn't really intend for the plugin to be used for players (which is why it didn't support this behaviour yet, it's usually not needed for admins), but I could add that option to the config.
    Maybe I'll get around to adding that later.
     
  15. no rush, this is a great tool to help investigate those situations where a clan member goes rogue and the building owner tells me it was a hacker. 8)
    Also can answer a question about a raid so I can coincide the box looter log with a tpr or home command.
    Great job on this much needed plugin. 8)
     
  16. I give spectate permission to admin, when he try spectate, in chat was killed by player who was spectate on 3 000 m range, automatic switch on 3rd person cam and stay like this, even when he respawn... Any idea how fix that?
     
  17. This has nothing to do with Spyon.
     
  18. How do i do to log all commands done?
     
  19. sqroot updated Spyon with a new update entry:

    1.1.0


    [DOUBLEPOST=1457025766][/DOUBLEPOST]
    Use Logger for Rust | Oxide, it makes use of a blacklist instead of a whitelist for logging.
     
  20. You now just need a support the developer link for PayPal on here.
    I went to do a donation and couldn't see a link. 8)