Notifier [Unmaintained]

Just upload your configuration file please.

 

Votre fichier .json est version incorrecte. Besoin de 5,5. Charger le fichier par défaut, puis sur modifier qui.
Your .json file is the wrong version. You need 5.5. Load the default file, and then edit that.

 

i can but mine is technically wrong atm, since i took out the map advert bit.
but if u can look at mine and send me a fixed copy of my altered config but with a working map thatd be great...
[DOUBLEPOST=1443563752][/DOUBLEPOST]

because map wasnt working i took out the map advert and made it false.
[DOUBLEPOST=1443567159][/DOUBLEPOST]also can you give an example for the scheduler?

like id use it to announce heli arenas, zombie arenas, and server restarts.
how would that translate?

 

So I tested Notifier with your configuration file, and there is actually an issue related to the default config file, I will release an update fixing this issue in a few minutes. So don't worry because the update will fix your issue automatically.

Now the Message Scheduler is quite simple to use, here is the default messages, and each scheduled for different timings:

Code:

"SCHEDULED MESSAGES": {
  "00:00": [
    "It is now <lime>{localtime}<end> of <lime>{localdate}<end>"
  ],
  "12:00": [
    "It is now <lime>{localtime}<end> of <lime>{localdate}<end>"
  ]
},

Here is a logic example:

Code:

"SCHEDULED MESSAGES": {
  "hours:minutes": [
    "MESSAGE 1",
    "MESSAGE 2",
    "MESSAGE 3"
  ],
},

Now lets say you want to have a message that announces an arena event at 16:30:

Code:

"SCHEDULED MESSAGES": {
  "16:30": [
    "THE ARENA EVENT IS JUST STARTING!!!",
  ],
},

Now lets add another message announcing a server restart at 01:00 with multiple messages:

Code:

"SCHEDULED MESSAGES": {
  "16:30": [
    "THE ARENA EVENT IS JUST STARTING!!!",
  ],
  "01:00": [
    "<red>THE SERVER WILL RESTART AT ANY MOMENT!<end>",
    "<red>THE SERVER WILL RESTART AT ANY MOMENT!<end>",
    "We are sorry for the inconvenience!"
  ],
},

And so on and so forth, I hope the examples are helpful.

 

SkinN õ.Õ'.|. updated Notifier with a new update entry:

Notifier | Minor Fix

 

Is there a way to remove the numbers inserted before the server rules? I want to format the numbers "1." "2." etc the color I want, and I put them in the rules text, so now my rules show up as "1. 1. BLAH BLAH BLAH". Somewhere it's adding in that first number and I'd like to remove it. Thanks for anyone's help in advance

 

Well that is actually in the plugin code, I made that the code enumerates the rules when listing each line. But I can make it so you can change enumerate them your selves.

 

Gah - so I'd have to SERIOUSLY know what I'm doing to change it and not eff it up. Haha. Yeah man, that'd be really cool if you're able to. This plugin keeps getting better and better, thanks for making it. Cheers!

 

Though I will not release anymore updates unless it's really necessary, so meanwhile I've attached a modified version for you so you can have it as you want until the update that adds the change, and don't worry because even on the next update you won't notice any difference, all will be the same as you have.

Thanks for the appreciation and let me know anything else you may need. Have a nice one.

 

Thanks a ton!

 

Hi SkinN,

The latest update is throwing the following error;

Code:

[Oxide] 8:35 AM [Info] Loaded plugin Notifier v2.14.1 by SkinN
[Oxide] 8:35 AM [Info] [Notifier v2.14.1] :: --------------------------------------------------
[Oxide] 8:35 AM [Info] [Notifier v2.14.1] :: * Configuration file is up to date
[Oxide] 8:35 AM [Error] Failed to initialize plugin 'notifier v2.14.1'
Traceback (most recent call last):
  File "notifier.py", line 300, in Init
RuntimeError: Failed to call Init (KeyNotFoundException: SCHEDULED MESSAGES)
at IronPython.Runtime.PythonDictionary.GetItem (object) <0x0006c>
at IronPython.Runtime.PythonDictionary.get_Item (object) <0x00024>
at (wrapper dynamic-method) object.CallSite.Target (System.Runtime.CompilerServices.Closure,System.Runtime.CompilerServices.CallSite,object,object) <0x000a2>
at Microsoft.Scripting.Interpreter.DynamicInstruction`3<object, object, object>.Run (Microsoft.Scripting.Interpreter.InterpretedFrame) <0x00113>
at Microsoft.Scripting.Interpreter.Interpreter.Run (Microsoft.Scripting.Interpreter.InterpretedFrame) <0x000c8>

I take it that it may require a config reset?

 

I managed to salvage my config and start a fresh one. Not 100% sure what caused the initial issue though.

 

Im always here ready to help, I always recommend you guys report the issue and upload the config file right away so I can get the issues from you.

 

Hey SkinN, not sure if you can see my original post as it is "awaiting moderator approval" so I will post it again. I will also link to the config that was at fault as I kept it.

Error:

[Oxide] 8:35 AM [Info] Loaded plugin Notifier v2.14.1 by SkinN
[Oxide] 8:35 AM [Info] [Notifier v2.14.1] :: --------------------------------------------------
[Oxide] 8:35 AM [Info] [Notifier v2.14.1] :: * Configuration file is up to date
[Oxide] 8:35 AM [Error] Failed to initialize plugin 'notifier v2.14.1'
Traceback (most recent call last):
File "notifier.py", line 300, in Init
RuntimeError: Failed to call Init (KeyNotFoundException: SCHEDULED MESSAGES)
at IronPython.Runtime.PythonDictionary.GetItem (object) <0x0006c>
at IronPython.Runtime.PythonDictionary.get_Item (object) <0x00024>
at (wrapper dynamic-method) object.CallSite.Target (System.Runtime.CompilerServices.Closure,System.Runtime.CompilerServices.CallSite,object,object) <0x000a2>
at Microsoft.Scripting.Interpreter.DynamicInstruction`3<object, object, object>.Run (Microsoft.Scripting.Interpreter.InterpretedFrame) <0x00113>
at Microsoft.Scripting.Interpreter.Interpreter.Run (Microsoft.Scripting.Interpreter.InterpretedFrame) <0x000c8>

Config:

rust-wd40.co.uk/notifier.json


As previously mentioned, a wipe of the config and having a fresh one fixed it. Hopefully it will give you an idea as to what caused it to begin with .

 

The config file is not complete. Upload here on the Oxide posts, theres an upload file option,

 

Here you go SkinN. If this is incomplete too then something happened when it tried to add the new bits of the config file. Looking back through the versions I had installed it may be the case that I missed the initial update when you implemented scheduled messages and tried to update with the latest version.

 

I know now what the issue was, and it's actually my fault when coded the last update, so sorry about that.
I have fixed and attached your config to this post, replace it to the on your server and restart the plugin, it should work.

Let me know anything else you need.

 

Use this config

 

Has you might see just above your post I have already provided a fix. Thank you though.

 

I uploaded the default config