Jump to content
Korean Random

Bartman

User
  • Posts

    52
  • Joined

  • Last visited

Everything posted by Bartman

  1. Seems to be offline again... "502 Bad Gateway"
  2. Did you prolong / activate it? https://modxvm.com/en/ -> settings on the top right (when logged in)
  3. Good point In addition, new branches also muddy the water when it comes to previously elited vehicles:
  4. Is this the XVM precise dots or grid quadrant clicks in general, or both? And I assume this is this an all out on/off switch? I think some of us are looking for a rate limiter, rather than completely disabling the system (which is useful not only between platoon mates and during SH and CW, but also in randoms if they're not spammed). There used to be an antispam mod (originally made by assassik if I'm not mistaken), but it's no longer maintained. And now that XVM has introduced the dots, that one would, even if updated, probably not rate limit those :)
  5. I assume you're not part of the dev team, you're just rearranging the elements of my question there... The anonymousColor value discussed is in colors.xc. Why would two different formats be used throughout XVM the first place?
  6. Thanks, finally got it to work! For some reason the colour specified has to be starting with # rather than the 0x used everywhere else in colors.xc. Is this a bug perhaps?
  7. That looks pretty useful... however adding "colors": { "anonymousColor": "0x1240AB", to colors.xc does not appear to do anything (regardless of using # or 0x in front of the colour code)... I'm guessing I'm missing something in playersPanel.xc and battleLoading.xc, but google translate seems to break their sentences a bit so I'm not quite sure. My playersPanel for example contains this line: "nickFormatLeft": "<font alpha='{{alive?#FF|#80}}'><font color='{{c:wn8}}'>{{name}}</font><font alpha='#A0'>{{clan}}</font></font>", I've defined a separate wn8 color scale in colors.xc, but I assume anonymousColor is a global colour variable and therefore the custom scale is not relevant, is this correct?
  8. What? I'll spell it out... I assume there's a value in colors.xc that defines the colour for players in battleLoading, battleLabels etc that currently makes them look grey, I'd like to change that.
  9. I'm using a custom colour scheme for WN8, and the standard grey for players without stats does not stand out much right now. Which colour value do I need to adjust to change this?
  10. Bump! We have a bunch of new vehicles coming up again, starting with the double barreled ones (and from what I heard, several other branches as well this year). Including re-grinders in this selection button would be very handy. We'll have to sometimes play existing elited tanks again in order to unlock those, after all
  11. That's unusual, the information displayed is very similar to the other two screens... Any particular reason that this is not possible right now?
  12. I have both the loading screen and player list pretty thoroughly configured (WN8, custom colour scheme, win rate per tank etc etc etc), however the battle report afterward has reverted to plain light grey numbering. I assumed I could add this to battleResults.xc, however that does not contain any kind of layout, nor a reference to a secondary file similar to battleLabelsTemplates.xc. How do I change the layout of the battle report? Example of the loading screen: Example of a plain battle report:
  13. The "Non Elite Vehicles" filter is one of my most used carousel options, however every time WG decides to change the branches or add new ones, and an 'elited' tank effectively is a grinder again (despite the elited flag), this is not included in the selection. Would it be possible to make this based on v.xpToEliteLeft (i.e. being greater than 0), instead of v.elite?
  14. Once you click anything on the top menu, like 'prolong', 'update statistics' or even 'login' (why can't we stay permanently logged in anyway? this is not a bank website), the language defaults back to russian, regardless of the /en/ in the url.
  15. Apologies, I meant that I have a colour scale configured for WN8, and I want that bar to use it as well :)
  16. I'm trying to change the color of the little blue bar on the left of the health bar to the non default scale I use myself, which setting influences this? I assume this is in one of the markers config files. Same question for the HP number when you press alt, seems to use the same color scale.
  17. It's only briefly visible, and you're missing the point here. The watermark is _not_ intended for the people who download nightlies and know what they're doing, but rather the large share who either just assume they're grabbing a 'working' xvm or don't even know it's a nightly because it's encapsulated in a mod pack.
  18. That's a bit over dramatic isn't it? Functionality is still that of a nightly build, it only adds a decal so the legions of people out there with no clue that the modpack they're using doesn't contain a stable XVM, know why functions might not work properly. And unless you're either actively finding and reporting bugs, or one of the devs mentioned fixing something important to you in the latest nightly, why would you exclusively use nightlies anyway?
  19. Also have a look in the res_mods\Mods\shared_resources\xvm\doc\ dir - macros.txt and macros-hangar.txt give an overview of which variables are available and where they work (garage or not for example).
  20. Nothing malicious in any of those responses tbh. And bear in mind that thousands will read these threads with various levels of grasp of english, answers need to be clear :)
  21. This might be an obvious one, but are you ending every line with a comma except for the last one? Otherwise you'll break the array. *EDIT* restriction apparently :)
  22. I'll spell it out: you're looking at the default WoT minimap right now. XVM needs a lot of work to make their improvements function again.
  23. You can find the format of the lines in hitLog.xc under "formatHistory". Not sure if you can limit the number of lines apart from grouping them per target ("groupHitsByPlayer"), which is already enabled by default. Easiest way to prevent it from overrunning your screen would be to move it back down so any overhead disappears under your screen, in battleLabelsTemplates.xc under "hitlog". Don't know if it's resolution dependent, but "y": 810 put it right where it was for me.
×
×
  • Create New...