Jump to content
Orrie

XVM Config Support and Stuff - All mods with a config welcomed!

Recommended Posts

I don't know how many people actually do their own XVM config instead of using modpacks, but I thought we could have a dedicated thread for people that actually does this and/or just general questions or support.

Kinda the same principle as the Quick Questions thread, just mainly focused towards XVM, but other mods with configs could relate.

 

I myself have been doing this for a year, so I kinda have some experience with the config structure and what not.

 

 

XVM Related Links:

Site: http://www.modxvm.com/en/

Forum: [EN] - [RU]

 

Dev Builds: [Nightly] - [Change Log] - [Commit Log]

Documentation: [Readme] - [Macros] - [Macros-Hangar]

 

 

Recommended Editors:

Notepad++ - Probably the best text editor for Windows

XCTuner - Editor for .XC files that assists in editing your config - Doesn't support advanced coding features
- Recommend for newbies, tho it wont really teach you anything.

XCPad - Text editor tailored towards .XC file editing

 

 

Need somewhere to post your xboxhueg config?

http://pastebin.com/ or http://privatepaste.com/

 

 

Fire away.

Share this post


Link to post
Share on other sites

What the fuck have they changed the {{spotted}} category to? I have yet to be able to get a simple {{spotted}} asterisk that doesn't want to pop some molly and strobe colours with this latest change, and I've played with a few different ways to deal with the new change.

Share this post


Link to post
Share on other sites

They've changed the spotting thingy to be useable with the extra fields features, and moved the "localization" to the texts property, which is located in texts.xc, when using the default config structure layout.

 

Default text.xc looks like this:

/**
 * Text substitutions.
 */
{
	"texts": {
		// Text for {{vtype}} macro.
		"vtype": {
			// Text for light tanks
			"LT":  "{{l10n:LT}}",
			// Text for medium tanks
			"MT":  "{{l10n:MT}}",
			// Text for heavy tanks
			"HT":  "{{l10n:HT}}",
			// Text for arty
			"SPG": "{{l10n:SPG}}",
			// Text for tank destroyers
			"TD":  "{{l10n:TD}}"
		},
		// Text for {{marksOnGun}}, {{v.marksOnGun}} macros.
		"marksOnGun": {
			"_0": "0",
			"_1": "1",
			"_2": "2",
			"_3": "3"
		},
		// Text for {{spotted}} macro.
		"spotted": {
			"neverSeen": "",
			"lost": "<font face='$FieldFont' size='24' color='#999999'>*</font>",
			"revealed": "<font face='$FieldFont' size='24' color='#00DE00'>*</font>",
			"dead": "",
			"neverSeen_arty": "",
			"lost_arty": "<font face='$FieldFont' size='24' color='#999999'>*</font>",
			"revealed_arty": "<font face='$FieldFont' size='24' color='#DE0000'>*</font>",
			"dead_arty": ""
		}
	}
}

 

 

If you use an incremental config structure, like I do in my modpack, you can add the modified spotted text like this:

"texts": {
// Text for {{spotted}} macro.
    "spotted": {
        "neverSeen": "<font face='$FieldFont' size='24' color='#5B5B5B'>•</font>",
        "lost": "<font face='$FieldFont' size='24' color='#DDDDDD'>•</font>",
        "revealed": "<font face='$FieldFont' size='24' color='#00DE00'>•</font>",
        "dead": "<font face='$FieldFont' size='24' color='#222222'>•</font>",
        "neverSeen_arty": "<font face='$FieldFont' size='24' color='#5B5B5B'>•</font>",
        "lost_arty": "<font face='$FieldFont' size='24' color='#DDDDDD'>•</font>",
        "revealed_arty": "<font face='$FieldFont' size='24' color='#DE0000'>•</font>",
        "dead_arty": "<font face='$FieldFont' size='24' color='#222222'>•</font>"
    }
}

There is also support for colour and alpha for the {{spotting}} macro, but ehh, not really required imo.

 

 

For displaying the {{spotting}} macro, I've used the reference technique, that Sirmax uses in his config.

Then calling that reference for every panel mode that I want the macro to be used.

 

Showing only large mode as an example, with stripped code:

/**
 * Parameters of the Players Panels ("ears").
 */
{
	// Enemy spotted status marker format for substitutions in extra fields.
	"enemySpottedMarker": {
		// Opacity percentage of spotted markers in the panels. 0 - transparent (disabled) ... 100 - opaque.
		"alpha": 100,
		// x position.
		"x": -95,
		// y position.
		"y": -5,
		// true - x position is binded to vehicle icon, false - binded to edge of the screen.
		"bindToIcon": true,
		// enemy spotted status marker format.
		"format": "{{spotted}}",
		// shadow (see below).
		"shadow": {}
	},
	// Parameters of the Players Panels ("ears").
	"playersPanel": {
		// Options for the "large" panels - the widest panels.
		"large": {
			// Set of formats for right panel (extended format supported, see above)
			"extraFieldsRight": [
				// enemy spotted status marker (see above).
				${"enemySpottedMarker"}
			]
		}
	}
}

 

 

Just look at my config, or Sirmax's config that is included with XVM.

 

 

 

Hope this guides you towards your goal.

Share this post


Link to post
Share on other sites

I've tried clearing out the 

"lost": "<font face='$FieldFont' size='24' color='#999999'>*</font>",

            

"revealed": "<font face='$FieldFont' size='24' color='#00DE00'>*</font>",
            

"dead": "",

 

to just leave

 

"neverseen": <font face='$FieldFont' size='24' >*</font>"  

 

"lost": "",

            

"revealed": "",
            

"dead": "",

 

 

but for some reason it won't process with either XCTuner or manually. off either default or someone else's config. I can't figure out where something is over-riding it.

Share this post


Link to post
Share on other sites

XCTuner doesn't support features that are still in development.

Its works around a library that requires frequent updates.

 

 

Upload your config, let me take a look. :3

Share this post


Link to post
Share on other sites

Also, a new feature that will arrive soon in the next version of XVM is a macro that tells you if a guy has XVMstats activated or not.
The macro is {{xvm-user}}, and can be used in the playerpanels or in the battle statistics screen

 

For playerpanels, the extra fields feature should be used for best results.

Example:

"extraFieldsRight": [
    { "x": -75, "y": 5, "bindToIcon": true, "src": "xvm://res/icons/xvm/xvm-user-{{xvm-user|none}}.png" }
]

This will result it this:

4da505ce97.jpg

(Dots are my spotting indicators)

 

Might help detecting xvm-snipers :)

 

 

The .png file is in the default XVM config.

Share this post


Link to post
Share on other sites

Also, a new feature that will arrive soon in the next version of XVM is a macro that tells you if a guys has XVMstats activated or not.

The macro is {{xvm-user}}, and can be used in the playerpanels or in the battle statistics screen

 

For playerpanels, the extra fields feature should be used for best results.

Example:

"extraFieldsRight": [
    { "x": -75, "y": 5, "bindToIcon": true, "src": "xvm://res/icons/xvm/xvm-user-{{xvm-user|none}}.png" }
]

This will result it this:

4da505ce97.jpg

 

Might help detecting xvm-snipers :)

 

 

The .png file is in the default XVM config.

 

 

Damn, this is nice to see if I'm just imagining that 60wn8 arta is aiming at me because of me thinking it's XVM or they just hate me. Kappa

 

Any ETA on this?

Share this post


Link to post
Share on other sites

Dunno when it'll be in the stable version, but you can get it in the latest nightly.

 

Not aware of any minimap bugs with the latest one. I've been using it for a few days, and no problems whatsoever.

Share this post


Link to post
Share on other sites

New nightly build released, minimap back to working fine. {{xvm-user}} has 3 values, I got it linked to an image; <img src='xvm://configs/EpicFale/img/xvm-user-{{xvm-user|none}}.png'>

- no xvm / grey - xvm-user-none.png

- xwm with stats / red - xvm-user-off.png

- xvm without stats /green - xvm-user-on.png

 

Indeed good to see if that clicker will be aiming for you! :3

Share this post


Link to post
Share on other sites

I've tried clearing out the 

"lost": "<font face='$FieldFont' size='24' color='#999999'>*</font>",

            

"revealed": "<font face='$FieldFont' size='24' color='#00DE00'>*</font>",

            

"dead": "",

 

to just leave

 

"neverseen": <font face='$FieldFont' size='24' >*</font>"  

 

"lost": "",

            

"revealed": "",

            

"dead": "",

 

 

but for some reason it won't process with either XCTuner or manually. off either default or someone else's config. I can't figure out where something is over-riding it.

 

You're missing a " in the neverSeen item.

 

Mine:

    "spotted": {
      "neverSeen": "<font face='Wingdings' size='20' color='#FF1900'><b>L</b></font>",
      "lost": "<font face='Wingdings' size='20' color='#FFFF33'><b>K</b></font>",
      "revealed": "<font face='Wingdings' size='20' color='#66FF00'><b>J</b></font>",
      "dead": "",
      "neverSeen_arty": "<font face='Wingdings' size='20' color='#FF1900'><b>L</b></font>",
      "lost_arty": "<font face='Wingdings' size='20' color='#FFFF33'><b>K</b></font>",
      "revealed_arty": "<font face='Wingdings' size='20' color='#66FF00'><b>J</b></font>",
      "dead_arty": ""
    }

 

The line should read like this:

"neverSeen": "<font face='$FieldFont' size='24' >*</font>",

Share this post


Link to post
Share on other sites

Great thread idea.  Configuring XVM for yourself got a little more difficult since they stopped supporting the online configuration editor.   Btw, can't recommend Notepad++ enough for editing text files such as the .xc files XVM configuration and the various .xml and other configuration files various mods use.

Share this post


Link to post
Share on other sites

Ok, so I'm on the latest XVM release (from Aslain's pack) and I'm trying out the xvm-user macro.  I added the line from Orrie's post:

    { "x": -75, "y": 5, "bindToIcon": true, "src": "xvm://res/icons/xvm/xvm-user-{{xvm-user|none}}.png" }

into my playerpanel.xc

 

I get the XVM user icon on players from my own team, but I'm not getting anything for the enemy team.  How would I fix it so I get the enemy team also (which is arguably more useful than knowing who uses it on my own team).  

Share this post


Link to post
Share on other sites
own:
"extraFieldsLeft": [
 { "x": -8, "y": 5, "bindToIcon": true, "src": "xvm://res/icons/xvm/xvm-user-{{xvm-user|none}}.png" },
 {}
],
 
enemy:
"extraFieldsRight": [
  { "x": -75, "y": 5, "bindToIcon": true, "src": "xvm://res/icons/xvm/xvm-user-{{xvm-user|none}}.png" },
  {}
],
 
you might have to adjust the arrays

Share this post


Link to post
Share on other sites

I was able to solve the issue, thanks Orrie and Sela. Turns out it was in player-panel that I had a parenthesis on the wrong side of a coma. Caused it to fuck the PP to another mode, which switched the extra field. 

 

 

New XVM user marker is dope. Though it doesn't say if the person has it active 'per se', only that they've had it active ever, and if they have it active at that point. IE if I play the same account on a vanilla client, someone will still see XVM user. 

Share this post


Link to post
Share on other sites

I was able to solve the issue, thanks Orrie and Sela. Turns out it was in player-panel that I had a parenthesis on the wrong side of a coma. Caused it to fuck the PP to another mode, which switched the extra field. 

 

 

New XVM user marker is dope. Though it doesn't say if the person has it active 'per se', only that they've had it active ever, and if they have it active at that point. IE if I play the same account on a vanilla client, someone will still see XVM user. 

 

As long as your 'token' is active it will show you as an XVM user

Share this post


Link to post
Share on other sites

Is there any way to use WN8 colors in minimap? I tried to get minimap to show tank labels colored according to players WN8 rating when pushing alt but no success. It only shows labels black. I was editing MinimapLabelsAlt.xc

 

original:

"css": {

          "ally": ".mm_a{font-family:$FieldFont; font-size:8px; color:#C8FFA6;}",
 
to this:
 
"css": {
          "ally": ".mm_a{font-family:$FieldFont; font-size:8px; color: {{c:wn8}};}",
 
(just that one line to test first)

 

I guess xvm macros don't work with css? 

Share this post


Link to post
Share on other sites

Also, a new feature that will arrive soon in the next version of XVM is a macro that tells you if a guy has XVMstats activated or not.

The macro is {{xvm-user}}, and can be used in the playerpanels or in the battle statistics screen

For playerpanels, the extra fields feature should be used for best results.

Example:

"extraFieldsRight": [
    { "x": -75, "y": 5, "bindToIcon": true, "src": "xvm://res/icons/xvm/xvm-user-{{xvm-user|none}}.png" }
]
This will result it this:

4da505ce97.jpg

(Dots are my spotting indicators)

Might help detecting xvm-snipers :)

The .png file is in the default XVM config.

Gg. I have mine activated but disabled the wr and colors in-game. Enabled colors out of game in garage and stuff so purple are bound to call me an xvm sniper now, I think that's gonna be the new thing.

Share this post


Link to post
Share on other sites

Is there any way to use WN8 colors in minimap? I tried to get minimap to show tank labels colored according to players WN8 rating when pushing alt but no success. It only shows labels black. I was editing MinimapLabelsAlt.xc

 

original:

"css": {

          "ally": ".mm_a{font-family:$FieldFont; font-size:8px; color:#C8FFA6;}",
 
to this:
 
"css": {
          "ally": ".mm_a{font-family:$FieldFont; font-size:8px; color: {{c:wn8}};}",
 
(just that one line to test first)

 

I guess xvm macros don't work with css? 

 

 

I haven't tried changing the CSS style itself, but changing the label formats code itself should work:

"format": {
	"ally": "<span class='mm_a'><font color='{{c:xwn8}}'>{{vehicle}}</font></span>",
	// etc etc etc...
}

 

 

 

EDIT: Oh wait, you're missing the # symbol before the {{c:wn8}} macro.

"css": {
          "ally": ".mm_a{font-family:$FieldFont; font-size:8px; color:#{{c:wn8}};}",

Share this post


Link to post
Share on other sites

Actually the CSS thing raises a couple of good questions, does anyone know if it supports alpha too? 

 

"ally": ".mm_a{font-family:$FieldFont; font-size:8px; color:#C8FFA6; alpha:#FF;}",

 

That way rather than having multiple colours for enemy and enemy_lost you could simply control it using alpha rather than 'shade'

 

(All about efficiency as they you can define colours elsewhere and control the lot in one go kind of thing) - I'm not able to test this myself over at least the next 26ish hours :(

Share this post


Link to post
Share on other sites

It doesn't work that way.

Alpha = Transparency, which in CSS is correctly applied with the Opacity parameter.

 

Example with 50% transparency.

"ally": ".mm_a{font-family:$FieldFont; font-size:8px; color:#C8FFA6; opacity:0.5;}",

I don't really see the usage tho.

Share this post


Link to post
Share on other sites

 

I haven't tried changing the CSS style itself, but changing the label formats code itself should work:

"format": {
	"ally": "<span class='mm_a'><font color='{{c:xwn8}}'>{{vehicle}}</font></span>",
	// etc etc etc...
}

 

 

 

EDIT: Oh wait, you're missing the # symbol before the {{c:wn8}} macro.

"css": {
          "ally": ".mm_a{font-family:$FieldFont; font-size:8px; color:#{{c:wn8}};}",

 

Thanks, changing format code did what I was looking for. I also tried adding # to css part but it didn't help, it was still just black.

Share this post


Link to post
Share on other sites

 

 

EDIT: Oh wait, you're missing the # symbol before the {{c:wn8}} macro.

"css": {
          "ally": ".mm_a{font-family:$FieldFont; font-size:8px; color:#{{c:wn8}};}",

 

I'm still looking into this and realised that the # would not be needed and could cause issues, as effectively you would be saying

 

colour:#0x60FF00

 

which just wouldn't work anyway. I don't have a any real CSS experience so I don't know how picky it is with hex defines for colours, whether it has to be define by a # or will accept 0x too (I'd imagine it's an either/or scenario but I don't know). If it were picky then you'd have to edit the colors.xc to suit.

 

I'll try and have a browse through the source code later today to see about macro support fully

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...