1. when i'm updating, under steamcmd, i use app_update 280550 validate

    correct?? or am i missing something?
     
  2. Wulf

    Wulf Community Admin

    Correct, same way that you installed it. For reference: Setting up a Rust server with Windows | Oxide.
     
  3. now i'm getting some kind of error....
    applicationmanager.cpp <1048> : Assertion Failed: Failed to write app state file
    Update state <0x0> unknown, progress: 0.00
    Error! App '258550" state is 0x202 after update job
     
  4. I do what wulf say and its works, i no get this error when i play, i can play fine... But if someone can try to join and check if its working would be nice, my server is UK SANDSTORM VANILLA, if someone can reply here
     
  5. nvm i fixed the issue with steam
     
  6. Glad to see that :)
     
  7. lol..i was like..what am i doing wrong..then i realized i messed up the directory path..RIP me
     
  8. Thanks for the quick oxide update wulf great job :D
     
  9. Updated server, updated Oxide (all 3x!!!) and still got the error:

    (08:39:30) | MissingMethodException: Method not found: 'PlayerTick.Deserialize'.
    (08:39:30) | Server Network Exception

    Version command -
    Protocol: 1368.117.1
    Build Version: 869.77
    Build Date: Thursday, April 28, 2016 7:27:25 PM
    Unity Version: 5.3.4f1
    Changeset: 14452
    Branch: /main

    oxide.version command -
    Oxide version: 2.0.1906, Rust version: 1368.117.1


    EDIT: Solved by reinstaling server. Saved all //server/ including all files - just deleted logs cause uploading a txt file with 30mb not worth it ;)
     
    Last edited by a moderator: Apr 29, 2016
  10. Wulf

    Wulf Community Admin

    FYI, the version and oxide.version commands will always show the version of the DLL you installed from Oxide. This doesn't mean your server is fully updated with Rust.
     
  11. I've done that and still no progress. Same error keeps showing up....
     
  12. Wulf

    Wulf Community Admin

    You're somehow still outdated then, try try again I guess.
     
  13. I got it fixed. Now just to update some plugins.