Jump to content
Korean Random

konrad509

User
  • Content Count

    1610
  • Joined

  • Last visited

  • Days Won

    7

konrad509 last won the day on September 29 2018

konrad509 had the most liked content!

Community Reputation

445 ⭐⭐⭐

1 Follower

About konrad509

  • Birthday 03/06/1988

Basic information

  • Gender
    Мужчина

Contacts

  • Nick
    konrad509

Recent Profile Visitors

8121 profile views
  1. Это довольно старый конфиг. Даже не стоит его исправлять. Возьмите новый дефолтной конфиг и настройте снова.
  2. I'm not a part of the dev team and I'm not "rearranging elements" of your question. I explained to you (more or less) why a different format is used and that it's not related to how colors are defined in colors.xc in general, because as I also explained to you earlier, you can define that value pretty much anywhere in the config. Why are there different formats used throughout the XVM config is a different question and that I can't answer, because I'm not sure myself. Generally, wherever HTML code appears, the #RRGGBB format is used. Elsewhere the other one is used. I believe it was discussed somewhere on the forum before.
  3. Not a bug. You want to use that color in a place that uses #RRGGBB format, so it needs to be defined in that format. It's completely unrelated to the fact that all colors defined in colors.xc are in 0xRRGGBB format.
  4. It's not really a variable, but yeah, the color scale is irrelevant here. The idea here is using a special macro {{.}} that lets you use a value defined somewhere else in the config. You can pretty much call it however you want and place it wherever you want. Then if you want to use that value, you just need to give a path to it, as in the above night_dragon_on's example.
  5. Just try default. Then if you decide you want to turn off something, edit the config, and if you don't know how, ask here on the forum.
  6. Generally, this info is located in res_mods\mods\xfw_packages\xvm_main\python\svcmsg.py, but I'm sure there's easier way to turn it off than by removing it from that file. It's just my guess, but maybe changing the value of __development__ in __version__.py to false does the trick.
  7. The XVM clearly IS working, but the stats are disabled. Also 2019-11-05 07:40:55: xvm_integrity results: incorrect!
  8. My bad. Didn't notice you're talking about the nighlty build. Anyway, it seems to be messed up a bit, but not as much as in your screenshots. .
  9. I've just loaded your file and everything seems to be fine for me.
  10. It is possible to make XVM markers look like vanilla ones, but I'm not sure to what extent. I haven't play around with XVM for a while.
×
×
  • Create New...