Jump to content
Korean Random

nixxxie

User
  • Content Count

    335
  • Joined

  • Last visited

Everything posted by nixxxie

  1. Thanks, that will be interesting. Personally i think that gradients need a bit of getting used to, as steps are less pronounced and you can be lulled into fake feeling of safeness ;) .
  2. I wonder what is in your rating.xc file...
  3. Bug report (5.4.1.2): Some team battles are reported as 9 battle tier, idk why. Replay attached. 9tier_bug.wotreplay
  4. They promised, and they eventually will. Still, better to check what they say every time instead of believing them ;) . And there is the case of dead crewmember... Anyway, i linked this for you guys to be aware of.
  5. I wonder if formatting rules apply to clock and you should force leading zero too? {{H%2.2d}} - check if it works.
  6. No problem, i shared here with everyone :) . PS: below are standard values moved to separate files if you need them for automation convenience, with initial step added (seen in extreme cases, like exactly 0 wn8, below 35% rating or not so extreme 0 kbattles). Those are what i generated from. BTW: orignal colors.xc from wotlabs had something out of date, i don't remember now but probably dmg_kind? kb_xvm_7x1_standard.xc rating_wotlabs_11x1_standard.xc rating_xvm_7x1_standard.xc wn8_wotlabs_11x1_standard.xc wn8_xvm_7x1_standard.xc
  7. Another reason to have crew xp logged for every crewmember: http://ftr.wot-news.com/2014/11/18/premium-tank-xp-modifier-not-used-in-crew-training/
  8. Better check it yourself ingame, it's barely noticeable. Just a little tweak, not a gamechanger. Like eg. difference between 9k and 10k or 13k and 14k. Effi values are not gradiented, so you can compare their spread to wn8 and see how it works. Or check how close wn8 values are slightly different. Maybe it's not clear: base steps are the same as their respective original scales - these same values are used with the same colors. More were added "in between".
  9. LOL, if you haven't changed anything in your test config, that's why there's no change. With no config, XVM loads those default values... IDK why stats are still inactive, try a different browser and then maybe check your firewall? PS: try redownloading and reinstalling xvm, maybe package got broken?
  10. I generated a few color gradient schemes for abovementioned ratings - wn8 and % are both for default XVM and WotLabs scales (with starting color added) and kb is from XVM default (with steps every 1k to like 40k). Feel free to use them, every array has a different file because otherwise it would be to messy. You load it in colors.xc with eg. "kb": ${"kb_xvm_7x13_gradient.xc":"kb"}, adjust for other files. I did it out of curiosity and it was interesting, but not a gamechanger and it's not very noticeable during play. Have fun. PS: guys, i see downloads - please, write a post (anything) if you do so, otherwise this topic will fall into abyss and others won't have the opportunity to find it ;) . kb_xvm_7x13_gradient.xc rating_wotlabs_11x5_gradient.xc rating_xvm_7x8_gradient.xc wn8_wotlabs_11x5_gradient.xc wn8_xvm_7x8_gradient.xc
  11. Ocassionally, when digging through some old configs i meet a bunch of old constans - it seems to me that they aren't used anymore, because of absence in default? What were they for? "consts": { "AVG_BATTLES": 2000, "AVG_GWR": 48, "AVG_XVMSCALE": 30, "MAX_EBN": 200, "VM_COEFF_FC": 0.93, "VM_COEFF_MM_BASE": 0.8, "VM_COEFF_MM_PLAYER": 0.93, "VM_COEFF_VMM": 0.88, "VM_COEFF_VMM_DEAD": 0.5 },
  12. Congratulations on winning two prizes , you greedy bastards ! http://habrahabr.ru/company/wargaming/blog/243027/
  13. Not familiar with windows? Sorry for offtopic, but what is more user-friendly? Definitely not linux...?
  14. OMG, there is a changelog, you know... Both under download button or, if you prefer offline, in doc folder too. You don't want us all raging the same like you, do you?
  15. Maybe you forgot to load Jove's config with configs/xvm.xc? Refer to sample file.
  16. Hmmm, are you guys sure that it is latest release? I mean, download from modxvm.com and copy onto kodos (if you haven't already).
  17. There reason they say online editor is obsolete is because it IS indeed obsolete - it generates old config, without taking account recent (and even not very recent) changes; example being "major" circles, which is quite an old change. Don't use it, apart maybe for checking syntax, i.e. missing coma...
  18. Just out of curiosity, which one has higher priority: "squadman_alive" or "teamKiller_alive"? Is it ever possible for a platoon mate to turn blue when using this macro? Obviously, i won't test this on purpose ;) .
  19. Looks that it is missing in default indeed. But, fear not - in absence of a value it just gets default anyway - in this case null is a generic ingame name.
  20. http://www.koreanrandom.com/forum/topic/19515-
  21. OK, i'll try and if it still happens i'll post (it does very rarely and idk why, so it may take some time :P ). I use bothunter from the beginning - and now more out of habit. It is using vbaddict database indeed and upon reporting sends them one too. Since it's a simple mod, you can use it separately, it doesn't interfere with xvm, only uses it for showing extra clanicons for fake clantags it creates to display bots/wipes. And i would advise against implementing such as it would make xvm insta-ban on EU forum because of dumb NOT "naming and shaming" policy... Bothunter thread had been pulled down quite quickly.
  22. Change browser. Enable cookies. You know, the usual stuff...
×
×
  • Create New...