1. Easier to run multiple events on a set schedule with repeater but if that's what I need to use, I will.
     
  2. I mean it should work properly but since it somehow "brakes" then use the alternative way.

    Also remember that all the commands set in the repeater will repeat every time their timer finishes. They are not going one by one so for example if i have a config like that:
    Code:
    myfirstcommand, 300//5mins
    mysecondcommand, 600//10mins
    
    There is no queue the are all starting at the same time. And they will repeat all the time.
     
  3. I know. Thanks for the help.
     
  4. Im running one of the configs from the faq and getting this is my error log. Any ideas?
    Code:
    [7/18/2015 9:13:24 PM] [Oxide] 9:13 PM [Error] Failed to call hook 'BroadcastEvent' on plugin 'Event Manager' (NullReferenceException: Object reference not set to an instance of an object)
    [7/18/2015 9:13:24 PM] [Oxide] 9:13 PM [Error] Failed to call hook 'BroadcastEvent' on plugin 'Event Manager' (NullReferenceException: Object reference not set to an instance of an object)
    [7/18/2015 9:13:24 PM] [Oxide] 9:13 PM [Error] Failed to call hook 'EndEvent' on plugin 'Event Manager' (NullReferenceException: )
    [7/18/2015 10:10:50 PM] [Oxide] 10:10 PM [Error] Failed to call hook 'ccmdEventStart' on plugin 'Event Manager' (NullReferenceException: Object reference not set to an instance of an object)
    [7/18/2015 10:10:57 PM] [Oxide] 10:10 PM [Error] Failed to call hook 'ccmdEventEnd' on plugin 'Event Manager' (NullReferenceException: )
    [7/18/2015 10:36:43 PM] [Oxide] 10:36 PM [Error] Failed to call hook 'OnEventPlayerDeath' on plugin 'Arena Deathmatch' (InvalidOperationException: Collection was modified; enumeration operation may not execute.)
    [7/18/2015 10:51:01 PM] [Oxide] 10:51 PM [Error] Failed to call hook 'OnEventPlayerDeath' on plugin 'Arena Deathmatch' (InvalidOperationException: Collection was modified; enumeration operation may not execute.)
     
    Last edited by a moderator: Jul 18, 2015
  5. This plugin just executes the commands. Now there should be an error from your side/plugin's side.
     
  6. Great plugin. Thanks
     
    Last edited by a moderator: Jul 20, 2015
  7. I have a problem with the plugin modifies the config file and does not affect any change in the server and keeps sending the same messages Default
     
  8. Wulf

    Wulf Community Admin

    When editing config files, make sure you verify that your formatting is correct by using a site such as jsonlint.com, and then reload the plugin after saving the config.
     
  9. Is there a way you could make it do chat commands ? such as /stackall 1000000
     
  10. Hmm you can try running the command "chat.say '/stackall xx' " i dont think that it will work.
     
  11. ill give it a try
    [DOUBLEPOST=1439240597][/DOUBLEPOST]Ok so i found out why it doesnt work , It doesnt work because when you do "chat.say '/stackall 100000'" because of the ' it counts it as a wrong command as the plugin can detect it but doesnt remove it for example "say 'hello'" comes out in the chat as 'Hello' with the '
    [DOUBLEPOST=1439240620][/DOUBLEPOST]
    Ok so i found out why it doesnt work , It doesnt work because when you do "chat.say '/stackall 100000'" because of the ' it counts it as a wrong command as the plugin can detect it but doesnt remove it for example "say 'hello'" comes out in the chat as 'Hello' with the '
     
  12. Well to run a chat command i think a BasePlayer has to execute it.. a (player)
     
  13. Ahhh damm because without that stackall basiclly all servers could be crashed , by somone doing somthing that i dont really wanna say
     
  14. And you can do the type of console commands: command (Title) (Time)?
     
  15. I dont understand you..
     
  16. I say you can make the plugin commands in the game?
     
  17. No you cannot run in-game commands.
     
  18. Every time I reload the plugin it resets the config I made. I triple checked all the config formats, brackets, etc.
     
  19. Ik.... once your reload the plugin it reads once more the config(changes that you made) and starts the timers once more..
     
  20. That's not what I meant.

    I edit the config to my liking. I changed the once command and the repeater commands seconds to 60 and 90 as you can see below.
    Code:
    {
      "ConfigCode": "1",
      "EnableTimerOnceCommands": "true",
      "EnableTimerRepeatCommands": "true",
      "OnceCommands": [
        {
          "command": "say 'THIS IS JUST AN EXAMPLE'",
          "seconds": 60
        }
      ],
      "RepeaterCommands": [
        {
          "command": "server.save",
          "seconds": 60
        },
        {
          "command": "event.run",
          "seconds": 90
        }
      ]
    }
    
    Once I do oxide.reload p-TimedExecute, it reloads the plugin and says "ConfigCode has changed... Updating the configuration file!" and changes it back to the default config every time.

    The ONLY way I could get it to not revert back a default config is by literally editting the lua code and replacing the default config with my own config.