Creating proper command map markers?


(G0-Gerbil) #1

How do I set up a destructible objective so that both teams see an icon in the command map?
Haven’t found any permutation of TOI / misc_commandmap_marker / key / values that does anything remotely useful.

Bog standard is simply side that can destroy it gets dyno and other side gets nothing but that’s a bit crap really - ‘defending’ team should see a custom icon where they have to defend.

All the SD maps do this, so any chance on shedding a light on this (and if possible shed light on why you’ve made the whole command map thing so complicated? Looks to me like it underwent so many revisions that it’s all confused now :confused: ).

Cheers :wink:


(G0-Gerbil) #2

infoaxis
infoallies

these are redundant keys for the TOI right?
What about

override

It crops up on the truck on goldrush (possibly the tank too, didn’t check).

As for my command map thing, for some reason it’s now using the custom images when it’s marked as IS_OBJECTIVE, whereas for the last few days it wasn’t (I was getting corrupt graphics / icons flickering on and off - tres bizarre, fingers crossed it stays like it is :slight_smile: ).


(Danyboy) #3

infoallies + infoaxis are little bits of text written in info panel - next to the map news sound.

It gives little piece of info about the objective.


(chavo_one) #4

infoallies and infoaxis are not used. Evidently they were early development items that never got removed from the maps.

The game uses the information found in the .objdata file to fill in the info panel.


(Danyboy) #5

oh never knew that - oh well time to delete those keys from my objs - lol


(sock) #6

Yep it was an early idea which never got removed from all of the maps. In the end most of the stuff which needed to be constantly changed for regional language reason was moved to config files. The above 2 keys are talked about in the Level Designer Reference (LDR) guide as being worthless, not used, obsolete! :wink: (LDR Page: Construction system, new entities, trigger_objective_info, entity keys)

Sock
:moo:


(G0-Gerbil) #7

Since I started this thread, I might as well mention what I’m now doing (so you can tell me not to do it!).

I use a TOI which includes an origin brush (better safe than sorry!), and targets a misc_commandmap_marker.

None of the spawn flags are set in the MCM, and the TOI has the following:

FLAGS:

AXIS_OBJECTIVE
ALLIED_OBJECTIVE
IS_OBJECTIVE

KEYS / VALUES:

track / whatever (appears when you are in the TOI)
shortname / whatever (appears on command map when you click on icon)
spawnflags / 19 (this is set from the flags above)
customaxisimage / path to whatever (axis sees this)
customalliesimage / path to whatever (allies see this)

If you wish to toggle the command map marker on and off then make a note of the targetname of the MCM, and in script:

TO SHOW:

setstate <MCM targetname> default

TO HIDE

setstate <MCM targetname> invisible

Bear in mind if you want to use custom images (or use some of the ones already in ET) that they must be SQUARE (IE both sides same length), and should ideally be power of two.

Note that not all the SD ones follow the above rules, so be wary (eg if you use the CM_TRUCK in gfx/limbo as a normal icon it’ll be distorted cos it’s the ‘wrong’ size (it’s ‘not’, since it’s actually specifically used for a TANK type of marker, which for some silly reason has different rules about it’s aspect ratio). In cases like this make your own version and make the image square to avoid it looking all squashed on your command map :slight_smile:


(sock) #8

Certainly include an origin brushes in any TOI. Keep them small and not the same size as the trigger brush, it makes it easier to select them and move them if required.

Use the TOI instead of the MCM for toggling the command map marker on or off.

Sock
:moo:


(G0-Gerbil) #9

Cheers for that straightener :slight_smile:


(G0-Gerbil) #10

Use the TOI instead of the MCM for toggling the command map marker on or off.

Sock
:moo:[/quote]Hiya, just spent my time testing this and this doesn’t appear to work :confused:
setstating the TOI toggles the actual TOI on and off, AND toggles the MCM the occasionally FIRST time only :confused:
After this I need to setstate the MCM itself to remove and add it to the command map.
In other words, to be on the safe side, I’m setstating BOTH the TOI and MCM.

Hopefully that should work all the time \o/