Open Source Realtime Strategy Game Engine
https://springrts.com/phpbb/
toairweapon= 1, its set on weapon and target VTOL , even forcing the onlytargetcategory to land it will not shot on land units, cuz weapon has values over unit fbismoth wrote:target category is not done on a weapon level it is done on a unit level senna. You need to name the units in question
Again, name the units.Senna wrote:Did u tested that torpedo, ignores categorys? because ive tested them, and seems like torpedos keeps ignoring the forcing onlytargetcategory, or maybe a missing command in torpedo wich i didnt found on wiki
what? onlyTargetCategory is per weapon, how else would you have, say a unit with one anti-ground weapon and one anti-air weapon.smoth wrote:target category is not done on a weapon level it is done on a unit level senna. You need to name the units in question
SanadaUjiosan wrote:I think he means it is in the unit def, not the weapon def.
toairweapon was necessary because it did not allow AA units to be fpsed and then force fired at anything the controller wanted. Tag has been replaced with.... ehh lemmie look it up...smoth wrote:good, that tag needed to go.
yeah it has no sense, but its an esample to smothknorke wrote:what? onlyTargetCategory is per weapon, how else would you have, say a unit with one anti-ground weapon and one anti-air weapon.smoth wrote:target category is not done on a weapon level it is done on a unit level senna. You need to name the units in question
http://springrts.com/wiki/Units-UnitDefs
btw, looking at the commit that removed toairweapon, and noting the lack of results from grepping the source otherwise, I'm not sure if toairweapon doing part 2 hasn't been gone for some time.CarRepairer wrote:Forb is right. I will try to explain using a list.
Toairweapon did two things:
1) make onlytargetcategory=flying units
2) make canattackground=false
Both those defs are available separately now, so toairweapon is not needed.
.How I read the postKloot wrote:FYI, toAirWeapon has never had anything to do with canAttackGround between the latter's introduction (github.com/spring/spring/commit/4f00af09a8ca6978cdb30e2d00521bee9aec0d7a for 0.75b1) and the former's removal.
(this here be a fine example of conflation, like the persistent "negative sun directions caused crashes" claim...)
Now given what toAirWeapon did (set a weapon's onlyTargetCategory to VTOL), it would have been true that "toAirWeapon made firing of weapons at ground units" impossible (if those units happened to be in a category other than VTOL, which would be expected), whether in FPS mode or not. I would not expect toAirWeapon=true to have also blocked "firing of weapons at ground", but looking at the code today that was probably true also: any weapon with a non-default onlyTargetCategory (or canAttackGround=false, for which a check was obviously added later) can not attack the ground, again whether in FPS mode or not."The main feature of toairweapon was that it made fps firing of weapons at ground and ground units impossible."
(and toAirWeapon did not literally "make canAttackGround=false" as CR's post might lead to you believe, but it had the same effect before canAttackGround existed)"toAirWeapon=true made firing of weapons at ground and ground units with category=VTOL impossible. the more recent canAttackGround tag lifted the inability of such weapons to fire at ground."
Kloot wrote:any weapon with a non-default onlyTargetCategory (or canAttackGround=false, for which a check was obviously added later) can not attack the ground, again whether in FPS mode or not.
