1. Reneb submitted a new resource:

    R-AntiGlitch - Blocks multiple glitchs: Pillar-Barricade, Pillar-Stash, Box-SleepingBag Foundation

    Read more about this resource...
     
  2. Pillar barricade is not working by the looks, had a player attempt and myself attempt and we could both place barricades on pillars
     
  3. you can place a barricade on pillars, but not a pillar on a barricade.
     
  4. Great plugin.
    I did a test on the barricade and I could pillar, then barricade then pillar again.
    Might not be detecting the barricade before you place a pillar
     
  5. Ah not normal, you shouldnt be able to place à pillar on a barricadé (the opposite you can).
    I'll test it again, should be an easy fix
     
  6. in clanforge, most of plugins crashed eachother...

    why does this happen?[DOUBLEPOST=1409906914][/DOUBLEPOST]i mean they conflicts with some plugins what i want to add.
     

    Attached Files:

  7. You need to send them à support ticket, telling them which plugins do NOT conflict.
    Hère all the plugins are compatible.
     
  8. Reneb updated R-AntiGlitch with a new update entry:

    added anti bear/wolf glitch

     
  9. Hi Reneb,
    Love the addition of the Anti Bear/Wolf Glitch, just 1 small issue that I think should have the ability to get around.
    As soon as the Bear/Wolf dies the very next bullet will make it disappear, which makes farming animals a bit harder as if you shoot an accidental 1 extra bullet animal disappears.

    My suggestion if possible would be to add a slight delay between killing the animal and allowing a bullet to make it disappear.
    Say about 1-2 seconds or a configurable time as a variable.
    I think 1 second would be enough to stop accidentally shooting the corpse away.
    I can see people shooting your farming bears as well for their enjoyment. LOL

    Another (But more complex) way to look at it might be if it is possible to check if the location of the corpse being shot and only disappear if a player is in the same location.

    Stag and Boar are also able to be hidden inside the same way a bear or wolf does as well.
     
    Last edited by a moderator: Sep 8, 2014
  10. i'll see what i can do.
     
  11. Hi guys,
    i have this error when use the plugin
    [Oxide] oxidecore: A .NET exception occured in user-code (@)
    [Oxide] oxidecore: nil
    [Oxide] oxidecore: [string "r-AntiGlitch.lua"]:76: attempt to call method 'GetComponent' (a nil 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


    some idea ?
     
  12. oxide version 1.7.3?
     
  13. I look.
     
  14. Is there a way to make it so that we can edit the number of shots after a hostile animal has been killed it takes to make the animal's carcass disappear? I personally go hunting animals with a bow and arrow, so it's not a big deal for me, but a lot of people unload M4 magazines into animals and whatnot, they don't seem to know how many shots it takes to kill them, and then as a result, if they kill it, but get two extra shots on the dead animal, it disappears and they can't collect the resources from it. If I were able, I would personally up this number to three or four, that way it ensures that trigger-happy hunters might get a couple extra rounds into the animal once its dead but still get the resources, but also, someone shooting at a player trying to bear-glitch would be able to get rid of the bear's carcass as cover pretty easily.
     
    Last edited by a moderator: Sep 9, 2014
  15. Hi, i get exactly the same Errors like he. Yes i use Oxide 1.7.3

     
  16. doesnt work with 1.7.3