nixxxie

I'd prefer {{c:spotted}} macro (and maybe {{a:spotted}} if someone wants it). They do, there are even examples of that on forum. And you can check my config if you want, i used some. (EU forums). PS: mind that elements are like a woman having PMS and not everything always works the way you meant it or even at all ;) .

Because i already lost my patience: i explained politely several times, both there and here. I very well know and understand how game mechanics work in detail and i want to play it MY way and use what I want, whereas i repeteadly met with post stating that you guys better know what i want, after explaining on my part again and again. I never said "do it my way ONLY", it was "do it my way ALSO" - that's the difference, and that's when unavoidably it gets political if i can't get the same treatment. Would you forbid me put pink skins on tanks if i want to? Enforce some anti-gay laws, maybe ;) ? Anyway, this case is already solved, so leave it as it is and stop beating the dead horse... PS: on technical side: i thought it would be easier to implement 50<r<445 saturation on DRAWING part instead of doubling amount of macros. But, do it whichever way you want, as long as it works. I think we met a laguage barrier here... As you said it yourself, it is already implemented with blindarea macros - only on value part instead of drawing part. Since i can use it the way i wanted, i don't care anymore ;) . PS: the original switch in tankrange.xc was: "spotting_limit": true but, judging by the rest of the file, it was on value calculation too.

Nope, doesn't work. Doesn't matter if x value is zero, positive or negative, field with src just disappears (or, is placed gods know where?). I also just tried as a last resort (after some crazy others) "x" : "{{vehicle.x}} + 20" And it seems to WORK :) . PS: i was a bit overentusiastic. extraFields seem not to handle arithmetic operations the way elements do. Both {{vehicle.x}} and {{vehicle._x}} work as a coordinate value but you can't do antyhing else with it. Or, at least i couldn't find a way.

Sorry, my mistake. I reviewed the screenshot i made and i noticed that beside optics i missed getting my commander dead :\ . So, everything is ok. I'm getting too helpful...

Bug report: after having my optics red and repaired back to yellow circles still stayed on damage half-distance: standing, motion and blindarea (the ones i have on). Yellow optics gives no viewrange penalty.

Thanks :) . Now, since i like vanilla panels and want to spare effort on rewriting them to "none" is there a way to: (1) attach extraFields "x" cooridinate to tank icon? or (2) force name and tank fields fixed width - you can set minimal value now, but maximal? I know about name formatting but it's not the same (especially with proportional fonts) and it's hard to hit exact value. The problem i observed it that sometimes vanilla panels go slightly over my hp bars and markers. PS: seems to me that with (1) i would have to include this coordinate difference into "w" too, so bars won't get distort in those special cases. Or, probably not, as width is relative...

Is glass half full or half empty? Wait, this is NOT my glass! Mine was bigger! And FULL!!! To be honest, blindarea would be redundant if you implement saturation switch on drawing part. Blindarea is exactly dynamic with saturation. Although, "dynamic" is also kind of not clear, maybe change it to "current"?

Like in topic, what more to add ;) ?

Well, kind of, since experienced players can do without it... Still, it was a nice feature adding symmetry to playersPanel ;) . Maybe you could move enemy classes to Fields too and rework whole spotting indication mechanism as generic, not ally/enemy dependent? I haven't tested yet how spotting markers work with "none" (since it's attached to tank icon?) - and i'm thinking of rewriting my whole playersPanel to "none" instead of "large" ("large" sometimes behaves strange, variable width with longer names?). BTW: i raise the question somebody asked: is it possible to disable certain playersPanel modes completely? So, they are not accessible, ever? I hate to leave mess in my config with options i never use or test - somebody else may try switching them and get strange results. PS: enemy artillery class is useless and obsolete too ;) , because (1) you can do this like me and (2) arty after nerf is much less dangerous. PS2: wait, silly me - it WILL work in fields if {{c:system}} macro works on them. Only, it doesn't now ;) . So, whole enemy spotting marker can be removed in future, too... PS3: or {{c:spotted}}, as {{c:system}} seems not to return different values for spotted/unspotted/never_spotted

That's a pity, my spotting markers serve dual-purpose, as tank-class indicators too. And allySpottingMarker would be somewhat useful in low tier battles. This is how it looks in my config.

This is my minimalistic version Unfortunately for now colors are static - {{c:system}} macro does NOT work. I'd like to change color for squad members and maybe TKers. http://www.koreanrandom.com/forum/topic/15977-csystem/?p=188504

Since allySpottedMarker was removed, how to call ally spotting event in extraTextFields now? I'd like to keep this functionality somehow.

So, we have to wait? I will try to be seen in those topics ;) . Thanks, guys :) . I do indeed understand the text. This is old Constructivism poster and i like the way it looks. The message, well - i think Rodchenko missed the point what a pacifier is and to me this poster is agressive as hell - this is funny all by itself.

"extraFieldsRight": [ { "x": 310, "y": 2, "valign": "center", "h": 21, "w": "{{hp-max:70}}", "bgColor": 0, "alpha": "{{alive?20|0}}" }, { "x": 310, "y": 2, "valign": "center", "h": 21, "w": "{{hp:70}}", "bgColor": "{{c:system}}", "alpha": "{{alive?35|0}}" }, // { "x": 310, "y": 2, "valign": "center", "h": 21, "w": "{{hp:70}}", "bgColor": ${"def.c2"}, "alpha": "{{alive?35|0}}" }, { "x": 320, "y": 3, "format": "<font size='12' color='#DDDDDD'>{{hp%4.4d|____}}</font>", "alpha": "{{alive?100|0}}" }, {} ] What am i doing wrong? Bars are black - macro apparently returns zeroes (or returns nothing, so zeroes are substituted). PS: it seems to me that i have to call a certain player somehow, apparently playersPanel position is not enough? PS2: it occured to me to add: my colors.xc are copied from default config, so no error there.

Thanks, i checked colors file and missed this :\ ...

Great :) , now we reach an understanding ;) . That camo circles are still interesting though, i have to think how to use and try them...

No, it isn't because it changes dynamically, while i want static values displayed all the time - saturated. Stranik, i understand that some players may want to have unchanged values returned for standing/motion returned - although i'd rather used them with scale parameter (1/2, 1/3, 1/4 - i may even try this in future, but it still seems not enough gain compared to mess they will make on map). Having a circle DRAWN outside 445m radius still is beyond and i want a way to saturate them on this value - if you can suggest me simple condition in drawing macro, then OK, i use it. That visual guesstimating is plain stupid :) - draw them scaled from the very beginning.

Or name it any way you want ;) . It would be great to have a macro that would return color value depending on enemy/ally/squad/teamkiller/etc. Maybe also colors for unspotted/neverdetected too? Just occured to me as i tinker with HP bars now :P .

http://i.imgur.com/iGsmVL0.jpg "extraFieldsRight": [ { "x": 310, "y": 2, "valign": "center", "h": 21, "w": "{{hp-max:70}}", "bgColor": 0, "alpha": "{{alive?20|0}}" }, { "x": 310, "y": 2, "valign": "center", "h": 21, "w": "{{hp:70}}", "bgColor": ${"def.c2"}, "alpha": "{{alive?35|0}}" }, { "x": 320, "y": 3, "format": "<font size='12' color='#DDDDDD'>{{hp%4.4d|____}}</font>", "alpha": "{{alive?100|0}}" }, {} ] For the purpose of width parameter, showing full value, but for the purpose of number - empty (underscores). Watch enemy tanks with black markers - unspotted.

I know, but how to hook on ally spotting event? I used this already for HP bars, sirmax-alike http://forum.worldoftanks.eu/index.php?/topic/397621-090xxx-almost-vanilla-modpack-xvm-config-with-hp-bars/

Both markers? Enemys' too? How to use spottingMarkers in fields?

Awww, was working in test3? Why, then? They are still useful on low tiers and were perfect field for me to put tank class indicator :( - dual purpose.

Since last update they disappeared on my panel... And everything in config seems to work, enemySpottedMarker is ok.

I don't. What if he sits behind two bushes? Three bushes? Which bushes to consider? How good his camo really is? There are too many different situations on battlefield to rely purely on calculation. And, with your example it would be much better to draw 1/2xviewrange circle - but now i kind of understand "scale" parameter... PS: i have tanks on which i can really abuse camo myself and with good bush+net i can only be proximity-spotted.

I know where i can NOT spot them. And where i CAN potentially spot them, if their camo is bad enough - eg. they do sth. dumb. It worked for me for more than half a year.