1. When i write in the console oxide.load (StackSizes for example) the console say this:
    Code:
    [Oxide] 4:29 PM [Error] NullReferenceException while calling cmdLoad: (NullReferenceException: Object reference not set to an instance of an object)
    (Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebug.gen.cpp Line: 56)
    [Oxide] 4:29 PM [Debug] at Oxide.Rust.Plugins.RustCore.cmdLoad (.Arg arg) [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
    (Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebug.gen.cpp Line: 56)
    [Oxide] 4:29 PM [Info] StackSizes plugin failed to compile! Exit code: -1073741515
    Can you help me please?
    [DOUBLEPOST=1425142705][/DOUBLEPOST]I can't load .cs plugins.
     
    Last edited by a moderator: Feb 28, 2015
  2. Hello,

    did you install net framework 3.5 on your host - machine ?
     
  3. Wulf

    Wulf Community Admin

    Which Oxide version are you using? You can check by using the version command in the server console or via RCON.
     
  4. I'm using Oxide Version: 2.0.367
     
  5. Wulf

    Wulf Community Admin

    You don't need to use oxide.load for plugins, they are loaded automatically. The error you showed in the first post is when oxide.load is used with a plugin name that doesn't exist. Could you upload your full log please?
     
  6. oxmin.load doesn't work, oxide.load is it, but im assuming he (@Wulf ) wanted to know if you used "oxide.load pluginname" or fully rebooted your server.
     
  7. yes, I use oxide.load (pluginname), when I reboot server .cs plugins don't load (Kits.cs, StackSizes.cs, RemoverTools.cs...)
     
  8. Wulf

    Wulf Community Admin

    The build the OP is using doesn't use .NET Framework, it includes its own compiler (CSharpCompiler.exe.)
    [DOUBLEPOST=1425146439][/DOUBLEPOST]
    Please provide your full log.
     
  9. Here
     

    Attached Files:

  10. Wulf

    Wulf Community Admin

    Could you also upload the Oxide logs from the log folder?
     
  11. Yes
     

    Attached Files:

  12. Wulf

    Wulf Community Admin

    The Visual C++ 2013 x86 installation should fix the compilation error, not the cmdLoad error. I missed that Mono requires that. We may be able to get around that, but we'll see. The cmdLoad error we should have fixed later, just make sure to use the correct filename for now and you won't see that error. ;)
    [DOUBLEPOST=1425152639][/DOUBLEPOST]The cmdLoad error will be fixed in the latest snapshot.