Move armordefs to unitdefs

[smoth]

Interesting. it looks like i don't even USE armor.txt.

I am not sure what the hub-bub was about. Do other projects actually use this thing? or does it somehow have a use? I don't even remember when I stopped using it.

[FLOZi]

Of course it has a use and of course other projects use it.

Gundam used it.

Just noone uses the tdf version (incorrectly called armor.txt by whichever dev implemented it) anymore, only gamedata/armordefs.lua.

It's also extremely flexible (as all lua defs are) as knorke has pointed out.

[smoth]

does it? I don't have the armor.txt file in my folder.

[FLOZi]

does it? I don't have the armor.txt file in my folder.

Either everyone in this community fails at reading comprehension or I speak in riddles.

Just noone uses the tdf version (incorrectly called armor.txt by whichever dev implemented it) anymore, only gamedata/armordefs.lua.

noone uses the tdf version called armor.txt

only gamedata/armordefs.lua.

[code_man]

Code_man, you aren't getting it. It has already been done. I can help you out if you like whenever I have a chance.

You mean making it read from unitdefs trough lua? If thats the case then no thanks, i think i give it a shot myself.

[smoth]

You mean making it read from unitdefs trough lua? If that's the case then no thanks, i think i give it a shot myself.

What is the problem with that? what is your aversion to lua?

[Forboding Angel]

Code_man, you aren't getting it. It has already been done. I can help you out if you like whenever I have a chance.

You mean making it read from unitdefs trough lua? If thats the case then no thanks, i think i give it a shot myself.

No dude, it's a replacement for the crappy system that spring uses via some magics in weapondefs post and configs. Evo uses it pretty extensively.

[PicassoCT]

Could we have some abstract armorunits, and have unitdefs inherit from them?

I mean FLOZi allready did that..
we (discincluding me ) could make it work by synchronizing in both directions.. a global armourdef (which is really really the better thing when it comes to finetuning)

and a local one via inheritance, and each is updated once the other one is changed

Work is like dogshit, it best piles on somebody elses lawn and you hope he steps on it, distributing it further, so that everybody is having one tiny bit of it on its shoe and.. the analogon goes nowhere.

[FLOZi]

Code_man, you aren't getting it. It has already been done. I can help you out if you like whenever I have a chance.

You mean making it read from unitdefs trough lua? If thats the case then no thanks, i think i give it a shot myself.

No dude, it's a replacement for the crappy system that spring uses via some magics in weapondefs post and configs. Evo uses it pretty extensively.

Evo's system isn't really relevant to the question afaics.

[PicassoCT]

Thats absolutly right FLOZI - we were talking about Journeywar Forb, start accepting it.

[raaar]

i use armor.txt and i'd miss it a little.

breaking backward compatibility annoys both players and devs, don't do it unless you have good reasons to.

Currently, move defs have their pathfinding-related attributes, but armor type does not....unless you also create weapon damage types:

armorTypes={
ARMOR_HEAVY={
DMG_LIGHT=0.25,
DMG_MEDIUM=0.5,
DMG_HEAVY=1.0,
DMG_INSTAKILL=9999999.0,
}
,
...
}

- each sub-table defines an armor type and the damage modifier for that weapon damage type against that armor type, default is 1.0.

- units would have an armorType unit def (that would override the one from armor.txt or armorDefs.lua, if any) and weapons would have a damageType weapon def (that could be overriden by adding the list of damage vs each armor type as currently done).

i think this wouldn't break backwards compatibility.

[smoth]

Or he could just manipulate it via lua. I really don't see the issue.