1. With the version 3.0.2???
     
  2. With the version right before the refund deployables fix, was it fixed in the next version?
     
  3. ??? Windows métal bars are déployables so fixed with 6.0.2
     
  4. The auto renew timer should work out better because if you are removing with your current timer now and someone attacks you the same thing applies just for longer which should theoretically be worse than my suggestion.
    Still have the ability to type /remove to turn it off manually like it is now as well.

    What I am trying to get at is the timer that now Auto disables after 30 seconds just changes to be Auto disable after about 10 seconds from last removal if remove is currently activated.
    That way it should be better as it will be able to auto disable sooner if you stop using it and the scenario you mentioned where someone starts a fight would be less likely to accidentally remove parts of your base than it does now.

    Another small suggestion if it is easy to implement also would be for Admins
    When Remove Admin or Remove All are on, a different message appears on the screen and stands out a bit more like "***ADMIN REMOVE ALL ON BE EXTRA CAREFUL***" or something like that.
    Currently the same message appears for all remove options.

    Thank you.
     
  5. I feel like that would cause unneeded lag, not only are you having the server removing items, which can lag the server, you are also having it destroy and create timers everytime something is removed. Now imagine that on a high population server where a lot of people could be using it at the same time.

    Just my thoughts
     
  6. There used to be diff messages, need to pût them again ^^
     
  7. Hi,

    Great Job!

    One question so far: what is the "flagsplugin_flag":"ban" entry in the cfg-file for?

    Cheers, Dieter.
     
  8. getting set-home errors after updating remover


    [Oxide] oxidecore: [string "r-sethome.lua"]:107: attempt to index field 'attacker' (a number value) (@)
    [Oxide] oxidecore: at NLua.Lua.ThrowExceptionFromError (Int32 oldTop) [0x00000] in <filename unknown>:0
    at NLua.Lua.CallFunction (System.Object function, System.Object[] args, System.Type[] returnTypes) [0x00000] in <filename unknown>:0
    at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (object,object[],System.Exception&)
    at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00000] in <filename unknown>:0
     
  9. it's 2 different plugins that don't interract.
     
  10. that's odd because i put the-old one back and the error stopped Oo
     
  11. i'll look into it later this afternoon
     
  12. It shouldn't cause any new timers as each time you do a remove it will just stop the existing timer and start a new 1.
    So always the same numbers of timers, the fact the timer could run for less time eg. 10 seconds, it should be an improvement if anything.
     
  13. Great plugin thanks , but after one of the updates /prod doesn't work it only tells the time till decay but doesn't show the structure owner .
    Is it a mistake I'm doing or will this be fixed in the future.
     
  14. Yes i guess i didn't explain enough how to use the prod ...
    to you the prod you either have to:
    1) use SteamAPIKEY
    2) DEACTIVATE SteamAPIKEY (usesteamapi) and have oxmin.[DOUBLEPOST=1409502005][/DOUBLEPOST]
    http://oxidemod.org/resources/sleepers-location.501/
     
  15. removes not working when you try to remove
     
  16. remove is working for me fine , only the prod thing and i tried to fix it and couldn't do anything for it . but remove is working .
     
  17. read the overview, i explained how to use prod.
     
  18. self.Config.prod.UseSteamAPI = false

    I did this and still didn't work , sorry for talking much of your time . thanks .