Crassius

Members
  • Content Count

    2
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Crassius

  • Rank
    Settler
  1. 2019/08/09 14:42:01.280 > Error > > Something went wrong! > Existing CreatureColorEntity with Id: Black is flagged ReadOnly. I did receive this message while smilexamining. I'm running Windows stable version (win 7-64), just started using Granger, and a few horses would be correctly examined. The third horse created this error. After that error smilexamining stopped working completely. It just doesn't respond. I restart Assistant and I can examine one horse but the next one creates this error. Next I tried the beta version but that just plain doesn't work at all. Can't get smilexamine to do anything. The herd is active and the character is listed. I went back to stable version and tested some more. It seems the colours that cause the problem are the old ones - gold, black, brown. All of them caused the error and none of the newer colours caused it. I didn't have all the colours to test but at least a few each of appaloosa, black silver, both pintos and ebony worked fine. Edit: I managed to fix the issue by editing colours and creating a colour with a unique ID name, like "blacks", and naming it black and tying it to the horse colour black. I couldn't edit the actual "black" tag since it's write protected.
  2. I can only second, or third, that this is the best map I've seen. I love the diversity and the islands that actually make seafaring necessary until those pesky bridge builders get to it. 9/10 maps are just one big boring continent where one place is like any other place. Also kudos for not removing priest restrictions. The only thing I would do differently is to set aggressive mobs to about 50% and maybe increase the total. Nice lore. I would definitely have picked this server if I weren't heavily invested in another one already, but who knows, if that one turns sour again, maybe...