Page 1 of 1

2 issues about unitdef resource tags

Posted: 14 Jun 2014, 20:03
by code_man
I noticed that extractsMetal doesnt work unless yardmap is explictly provided.
Now im a bit new to spring and am not sure if this isnt a glitch, so i didnt report it on the bug tracker, tough it seems like one.
Unless there is a reason for this that im not aware of. I thought i should let people know of this and ask if i should next time just put it up right on the bug tracker.

Also makesMetal tag seems to be completly redundant give you could use metalMake and energyMake.
Again i wasnt sure if i should have put this in "engine requests instead", i mean this is a kinda stupid tag.
Then again the wiki could have not mentioned something, wouldnt be the first time.

I hope im not comming across as a bother, but i just thought i should let people know about this, wasnt sure where else to put this.

Re: 2 issues about unitdef resource tags

Posted: 14 Jun 2014, 20:31
by Beherith
A yardmap one of the things that makes a unit a building. Might be needed to extract metal (afaik only buildings can extract M).

float metalMake Default: 0.0
The amount of the metal resource the unit generates unconditionally per game 'tick'.

VS

float makesMetal Default: 0.0
The amount of the energy resource the unit turns into the metal resource per game 'tick'.

Re: 2 issues about unitdef resource tags

Posted: 14 Jun 2014, 20:38
by code_man
Hmm, yes this connection does make sense now that you say it. Tough i assumed a unit is distingushed by a structure by its ability to canMove and not its yardmap, while the yardmap would be defaulted to "o" * footprintx * footprintz.

Ah ok i see how things relate now, il try to pay better attention to texts next time.

Re: 2 issues about unitdef resource tags

Posted: 14 Jun 2014, 22:35
by FLOZi
Indeed yardmap defines a structure (canMove determines mobile or immobile - you can have immobile 'units' that are not structures) and only structures can be extractors.