Solved 'Network.Server.maxConnections' not found (outdated Oxide)

Discussion in 'Rust Discussion' started by Timmy Burch, Feb 18, 2016.

  1. Timmy Burch

    Timmy Burch

    Hi all, what is the issue with the new update?
    MissingFieldException: Field 'Network.Server.maxConnections' not found.
     
    Timmy Burch, Feb 18, 2016
    #1
  2. Ne0squid

    Ne0squid

    hey guys i just recently updated my server and wiped it. and after i installed the oxide update my console is being spammed with "| MissingFieldException: Field 'Network.Server.maxConnections' not found." Every plugin i have on my server seems to be working fine so i was just wondering if anyone knew what could cause this?

    Thanks
    -Andrew
     
    Ne0squid, Feb 18, 2016
    #2
  3. Wulf

    Wulf Community Admin

    Make sure your plugins and Oxide are fully updated. That field was removed, so plugins will need to be updated. If you are getting it from a specific plugin, please report it in the plugin's support thread.
     
    Wulf, Feb 18, 2016
    #3
  4. Timmy Burch

    Timmy Burch

    I deleted all the plugins for the test, all the same!
     
    Timmy Burch, Feb 18, 2016
    #4
  5. Wulf

    Wulf Community Admin

    Then you're most likely using an outdated version of Oxide, as that error is not in the latest build, only the previous for the previous version of Rust.
     
    Wulf, Feb 18, 2016
    #5
  6. Timmy Burch

    Timmy Burch

    I updated by the updater is now once again updated for the test.
     
    Timmy Burch, Feb 18, 2016
    #6
  7. BegoRedSmith

    BegoRedSmith

    Same here, unloaded all plugins and get it again.
     
    BegoRedSmith, Feb 18, 2016
    #7
  8. AndreSpecker

    AndreSpecker

    AndreSpecker, Feb 18, 2016
    #8
  9. Wulf

    Wulf Community Admin

    I don't see the same error as what this thread is about.

    Oxide isn't fully updated on your server.

    What updater? I'm referring to Oxide, not Rust itself. The error is from an outdated version of Oxide being used, I know this as I literally just fixed the error. It's physically only possible to get that error if your server is using old Oxide files.
     
    Wulf, Feb 18, 2016
    #9
  10. Timmy Burch

    Timmy Burch

    My test server is started. I solved the problem. Updateoxide and offecial server now
     
    Timmy Burch, Feb 18, 2016
    #10
  11. mr.Varzhak

    mr.Varzhak

    Wulf, Hello, can you give me last OxidePatcher.exe ?
     
    mr.Varzhak, Feb 18, 2016
    #11
  12. Wulf

    Wulf Community Admin

    It's on our GitHub snapshots repo, hasn't changed.
     
    Wulf, Feb 18, 2016
    #12
  13. maxaki

    maxaki

    Same issue. Oxide is updated
     
    maxaki, Feb 18, 2016
    #13
  14. Wulf

    Wulf Community Admin

    Oxide is not updated if you are getting the error, please update again and make sure all files are updated.
     
    Wulf, Feb 18, 2016
    #14
  15. Hatemail

    Hatemail

    Ask your host to update to the latest snapshot if you are using a host.
     
    Hatemail, Feb 18, 2016
    #15
  16. maxaki

    maxaki

    Yes sorry. It was the host. You were right once again.

    Should trust you guys :)
     
    maxaki, Feb 18, 2016
    #16