1. Wulf

    Wulf Community Admin

    One of the largest steps toward cleaning up our projects was getting each game and extension split into their own repositories and building independently.

    Part of the reason for doing this was to provide a Oxide extensions and its core separately and free from any game-related code. Having these projects separate would allow game developer and plugin developers to grab and use what they need, without having to haul around every other game they may not need or have interest in. This new setup also provides for faster builds as the build server won't have to create a new build for each and every project, only those that have had changes made to them.

    While not entirely recent, you may have also noticed that we no longer store game DLLs in our GitHub repositories, but instead download those on-demand from Steam based on if you own the game or not. For most games, the dedicated servers are freely available and do not require a login, but it's best that we keep any copyrighted game code out of the repositories, just to be safe!

    You can see the various new repositories at Oxide · GitHub. If you're looking for builds for a particular game, you can find those under the Releases tab of the extension's repo (ie. Oxide.Rust). We're also still providing the "latest" URL at Release Latest · OxideMod/Oxide · GitHub.
  2. Wulf

    Wulf Community Admin

  3. Alright, thank you!
  4. Sorry for being such a lay-person Wulf.......put just so I am clear, I/We.....need to now download both this repository as well as the new build file?
    You have just separated the extensions from the main Oxide build, such as Rust:io and the like?

  5. Wulf

    Wulf Community Admin

    No, we still make bundles for each game that contain the extensions and necessary files, same location to download for the "latest" link, but a new link added as well.
  6. Wulf

    Wulf Community Admin

  7. Oh...ok.....Thanks Wulf!
  8. When will this take effect?
  9. Wulf

    Wulf Community Admin

    It already has, been working on it for the past week.
  10. For everyone that needs to get the latest release for their Auto Update Scripts, you can get it without the latest tag via the GitHub API:


    Take a look at the browser_download_url, that will always point to the latest release

    curl -s https://api.github.com/repos/OxideMod/Oxide.Rust/releases/latest | jq -r ".assets[] | select(.name | test(\"${spruce_type}\")) | .browser_download_url" 
    Will give you "https://github.com/OxideMod/Oxide.Rust/releases/download/2.0.3748/Oxide.Rust.zip"

    Source: How to download the latest release from Github
  11. Thanks, i hope, that we will have the static link in the future, for our update scripts!
  12. @Captian Cock That wouldn't work for upgrade scripts as you would have to manually change the version number every time. The correct repository would be something like
    It doesn't seem to be available atm.
  13. Wulf

    Wulf Community Admin

    The script they posted pulls the version from the API, which would always be the latest. The GitHub API is great for this sort of thing, the "latest" links would mainly be for those who aren't familiar with that and to make it a little easier. The API is the better approach though, as you aren't blindly updating and not updating unnecessarily.
  14. I check the OxideMod release version number against my last known local download to see if there has been an update. After today's changes, I use this version of the command-line Captian Cock posted to get the isolated version number

    curl -s https://api.github.com/repos/OxideMod/Oxide.Rust/releases/latest | jq -r ".tag_name"
  15. which link can I use to download the update in rustide?
  16. I have been checking the api against the Rust plugin version generated in the oxide logs. I noticed the last update the version that displays in the logs is not the same as the version listed on the Git latest api.

    Is this just a bug from all the recent changes, or should I change the way my script compares versions? Is the version listed on GitHub more accurate than the version generated in the logs?

  17. Wulf

    Wulf Community Admin

    Same one that you have been using I believe, but you can update to the newer one if you'd like.

    The command oxide.version was showing the version from Oxide.Core, which is built separately now. The version output is updated in the last snapshot though to fix this, so now it'll show the version for Oxide.Rust.
    Last edited: Nov 17, 2017