1. Hm.. What is default time of day and night?!
     
  2. Default length of a day (day + night) is 30 minutes which results in 15 minutes of day and 15 minutes of night without the usage of the timecurve and about 18 minutes of day and 12 minutes of night with the timecurve if I recall correctly.
     
  3. Thank you! :p
    [DOUBLEPOST=1426096849][/DOUBLEPOST]If so... 30mins 1 day cycle... Why /settime only 24 ?
    [DOUBLEPOST=1426097254][/DOUBLEPOST]So... To do the smallest night cycle - i need to do 5m night and 25 day? Thanks.
     
  4. Anyone else have a problem with the timer breaking and it returning to normal day and night lengths after a few hours?
     
  5. The /settime sets it to the in-game hour so /settime 12 is noon where /settime 24 is midnight and you can increase the length of a day even past 25 minutes if you want.
    This shouldn't really be happening but as all my other lua plugins I'm in the process of rewriting it to C#, however due to a lack of time this is taking a lot longer than originally expected.
     
  6. Well, personally believe it is more than likely a problem with Oxide, as pretty much any other plugin using timer.repeat has the timer die after 7+ hours.
     
  7. Wulf

    Wulf Community Admin

    The problem though is that if for some reason a timer doesn't get destroyed and the user reloads it, it makes new instances without killing the old. This can stack up quickly if the owner rarely stops their server.
     
  8. If the timer is destroyed when the plugin is unloaded through the Unload() hook this should normally not be an issue though.
     
  9. Wulf

    Wulf Community Admin

    Right, which is what I said in the other thread discussing this. ;) It shouldn't be an issue of they do actually get destroyed in Unload.
     
  10. After trying it with the self.plugin fix you suggested Wulf, all repeat timers are still getting randomly killed about 6-8 hours in. Don't think that is the issue. Also want to point out that this problem happens after a clean restart without doing any plugin reloads. The only thing that might be happening regarding that is if Oxide isn't shutting down the previous timer.repeat when its ran again.
     
  11. gd,

    not working with latest oxide b519

    only /time command working for show exact time

    you can not change time and day/night length

    interesting thing is no error getting
     
  12. I'll have to look into it, but currently trying to fix something else so it might take me a while to get to it.
     
  13. Thanks for your attention - awaiting
     
  14. Strange, its working fine on my end.
     
  15. may be need to be reload after server restart I will check now
    [DOUBLEPOST=1426841163][/DOUBLEPOST]
    nope it's even not able to load as oxide.reload m-Time
    say namely not working in my server
    [DOUBLEPOST=1426874219,1426841006][/DOUBLEPOST]getting below errors then server crash that's why I removed plugin until fixed

    [Oxide] 6:34 PM [Warning] Clock is 1535.01 seconds late! Timers have been delayed. Maybe the server froze for a long time.
    TimeWarning: AIHandler.Cycle took 7.76 seconds (7758ms)
    TimeWarning: AIHandler.Cycle took 1.13 seconds (1130ms)
    TimeWarning: AIHandler.Cycle took 3.51 seconds (3507ms)
    TimeWarning: AIHandler.Cycle took 2.12 seconds (2116ms)
    TimeWarning: AIHandler.Cycle took 2.55 seconds (2554ms)
    TimeWarning: AIHandler.Cycle took 1.32 seconds (1320ms)
    TimeWarning: AIHandler.Cycle took 0.75 seconds (999ms)
    TimeWarning: AIHandler.Cycle took 1.26 seconds (1259ms)
    TimeWarning: AIHandler.Cycle took 1.74 seconds (1744ms)
    TimeWarning: AIHandler.Cycle took 1.87 seconds (1870ms)
    TimeWarning: AIHandler.Cycle took 0.95 seconds (948ms)
    TimeWarning: AIHandler.Cycle took 0.61 seconds (608ms)
    TimeWarning: AIHandler.Cycle took 6.67 seconds (6666ms)
     
  16. Are you on the latest oxide version?

    Also, if oxide.reload isn't working, try opening the plugin while its running, adding a space and then removing the space, saving it, and then uploading it back while the server is still running. That should force oxide to reload it.
     
  17. Hmm, the plugin doesn't do anything involving AI and these are warning from rust that have nothing to do with the plugin
     
  18. yes probably it was not related with this plugin
    I just wipe the server and reload all plugins/data
    Currently server working well without error
    all commands working about the day/time system
    [DOUBLEPOST=1426881288][/DOUBLEPOST]
    Today morning I try that and finally I wipe the server and now everything is okay