Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


IanHighlander last won the day on August 18

IanHighlander had the most liked content!

Community Reputation

308 Tribe Leader

About IanHighlander

  • Rank
    Hide Armor

Personal Information

  • ARK Platforms Owned

Recent Profile Visitors

3,279 profile views
  1. If you don't want to breed them but want them on wandering for paste/poly production, just spay them. I just did that with mine, back to normal now.
  2. May have no effect, but try re-mounting the dino and then running cheat walk.
  3. Bug reporting has changed for all platforms.
  4. @cad Another small bug I've noticed. If you edit any creature that has a cooldown/growing status, it doesn't carry that over to the edit page so when you save it, it loses the cooldown timer in the library for that creature. Edit: actually just double checked myself and it does seem to carry it to the edit page but doesn't carry it back to the library when you save.
  5. UseOptimizedHarvestingHealth=True Add that to your GameUserSettings.ini file with the server off then restart it.
  6. Yes, always do, I tend to have loads exported at once and just bulk import them. Many thanks for the quick update. Edit: can confirm since the last update, my latest batch bulk imported successfully imported the colours.
  7. Individual exports from creatures in game that are then imported using the normal "import exported data" option.
  8. Hi @cad not sure if this is me doing something daft or missing a setting (usually is lol) but for some reason when I import dinos the colours are no longer brought into ASB with all the other information as a result I now have quite a lot of holes in my colours lists for bred animals. This has been going on for quite a while I just kept forgetting to ask in here about it. Am I missing a setting somewhere that's been added or is this a bug?
  9. There's examples of the code you need to add in this thread and you'll find the spawn entry container classes for Rag here Hope this helps.
  10. Breeding is not the same as when you pick up a wild one. The parents may both be the same level but those levels are made up of various points in the stats. If those aren't identical in both parents you have a chance of getting the lower points on each stat and as such a lower level baby. The only way to guarantee a 232 from two parents of that level (and remember levels pumped in to parents do not affect the babies, only born levels/stats count), is for both parents to be identical in every way stat wise.
  11. You won't be able to see it in the server list while it's a major version out. You need to update it, I've always used ASM for this, but in theory it's just a standard steamcmd command like this (obviously change the username and password and the path to your installation): @echo off start "" steamcmd.exe +login USERNAME PASSWORD +force_install_dir "C:\Path_to_Ark" +app_update 376030 validate +quit Actually, looking at the way ASM does it you can just use anonymous instead of your own username and password.
  12. Unclear if you're on official or unofficial servers, but if on unofficial and using S+ we had an issue on ours where suddenly nothing would eat off the S+ tek troughs (possibly other S+ troughs too, but untested). Emptying the trough, picking it up and re-placing it saw everything suddenly eating normally again (and a huge amount of food get used in the troughs as they were catching up
  13. Just putting my pedant hat on for a moment, whilst if the servers are relatively quiet, it will run 8 or possibly even more Ark servers. Technically you should always leave a core free for the underlying operating system, if those Ark servers are going to be in the slightest bit busy, I wouldn't run more than 7 on them to be safe.
  14. So yes, it was a full rebuild I did, but (and it's a big but), if you use ASM as I do, you need to completely nuke ASM's cache and get it to re-download a fresh copy as re-building in ASM will just pull a new copy from its cache and put the problem straight back. So in order: Shut down server. Take FULL backups (your own fault if you don't do this properly). If using ASM, nuke the installation cache. Delete the old server files (except any configs of course). Reinstall fresh server (if using ASM, it will pull down a new fresh copy and then install if you use
  15. Honestly don't remember what I did at the time, but will go back through our discord groups chat history and see if I put the info in there (I usually spout just about everything else in there). If I can confirm what I did I'll post back.
  • Create New...