1. I would actually appreciate you could tell me the full ip in private, so I can check what the web request is getting and see what I can do about it.
     
  2. Sometimes the clock goes completely "off time" as seen in the example below.

    (17:28:31) | [Oxide] 5:28 PM [Info] [Notifier v2.16.6] The server time and date is 10/24/2015 17:28
    (17:40:31) | [Oxide] 5:40 PM [Info] [Notifier v2.16.6] The game time is 4/7/2025 2:40:43 PM
    (17:52:31) | [Oxide] 5:52 PM [Info] [Notifier v2.16.6] The server time and date is 10/24/2015 17:52
     
  3. The Server Time is the REAL time of your server's timezone location.
    The Game Time is the in-game time of your server.

    So it's about right as it is. :)
     
  4. Can the game time be disabled then? as it makes literally no sense to have it then
     
  5. Just remove the message from the adverts, that is option for you to use or not. It's there because because people requested it, some find it useful.
     
  6. cool thx, keep up the good work SkinN ;)
     
  7. Code:
     [Debug]   at Oxide.Core.Libraries.WebRequests+WebRequest.<WaitForResponse>m__0 (IAsyncResult res) [0x00000] in <filename unknown>:0
    (09:40:16) | [Oxide] 9:40 AM [Error] Web request produced exception (Url: http://ip-api.com/json/155.143.22.49?fields=country,countryCode) in 'notifier v2.16.6' plugin (NullReferenceException: Object reference not set to an instance of an object)
    Got this when loaded up latest version.
     
  8. Hmm, I gotta see what else I can do about this. I may have to change the api provider again.
     
  9. what are adverts?
     
  10. Adverts are messages that appear randomly in the chat and every X minutes, you may change the adverts interval in the Settings section, and your messages in the Adverts section in the config of Notifier under the config folder of your server.
     
  11. SkinN õ.Õ'.|. updated Notifier with a new update entry:

    Notifier | Minor Change


    [DOUBLEPOST=1445748320][/DOUBLEPOST]
    Hopefully this one will work. Let me know about it.
     
  12. I
    I have a problem /players dosent work theres no console errors
     
  13. As I mentioned before I do not want Notifier requiring dependencies. But though thanks for suggesting.
     
  14. Well you are already depending on webrequests who aren't reliable enought when api limit is reached.
     
  15. Newest version works fine with no errors here.

    Dropped testing Notifications because of the need of GeoIP as players were almost never listed with their country tag, or even listed wrong.
     

  16. Seems to be running fine now :)
     
  17. The dependencies that I am talking about is that "your plugin users" have to download and install a second plugin to make 1 feature to work, I rather have things packed up and simple. And if it's not for webrequests (which is implanted in Oxide already) how else I'm I suppose to grab data from the web?
    [DOUBLEPOST=1445809429][/DOUBLEPOST]
    I tested GeoIP plugin on Notifier before and did not work for me most of the times.
    [DOUBLEPOST=1445809492][/DOUBLEPOST]
    Well ye but I got somebody else repoting the same issue with the new API Provider, I can't figure why this happens, I will see what the Oxide devs say about this.
     
  18. Have noticed after a restart sometimes, all people joining it goes to "Unknown" but a simple reload fixes it somehow. But not an issue for me.