Renegade
18.07.2010, 21:20:11
Fight 1
I concur with Worm's, Beowulf's and Striker's argumentations here.
While, yes, particularly the example with the wood "walls" and flame throwers is a good one, ultimately, what Beo said stands: If you want to change a wall's resistance, just change the Strength value. Yes, it's primitive, but it has worked for almost a decade by now, and unit stances will enable far greater tactical variety than slightly changed walls will.
Kill #773
Support #461
Fight 2
TurretAnim= on tanks is pure laziness. While it may be a valid request, investing hours of coding just so somebody doesn't have to copy & rename 4 files in less than a minute seems disproportionate.
Multiple turret voxels is a pretty silly request...multiple turret voxels for use with what? In order to make use of those, you need support for multiple turrets in the first place. We don't have that. That's request #510, to be discussed next week. Therefore, this part of this request is worthless.
Damaged voxel...a nice idea, and practical for a quick overview of the state of the force.
Spawn-dependent turret...neat little thing, but nothing more.
So yeah...half of the request is worthless from the start, and while the last part is kinda neat, it's not exactly a game-changing über-feature.
I would be interested in having this for the damaged voxels, since I do think that would add a lot to the atmosphere of the game - especially considering buildings already have a damaged state, and that damaged vehicles smoke anyway. Given that there must be an existing check to trigger the latter, it should be easy enough to hook into that and add voxel-changing code.
Unfortunately, it has the same problem any graphics issue has: It would need new voxels, and those are hard to come by for such a specific case. It's also not just damage voxels - there are a bunch of other issues mashed into the request.
Unhardcoding of drain weapons, on the other hand, is a clear, simple, small change that has direct effects on gameplay and can be used by all modders without further prerequisites.
Given that Alex specifically mentioned damaged voxels as well, I will vote to kill the crappy voxel mashup request, but spin off of the good parts as low-priority issues to be done in the undetermined future.
Kill #295
Support #556
I concur with Worm's, Beowulf's and Striker's argumentations here.
While, yes, particularly the example with the wood "walls" and flame throwers is a good one, ultimately, what Beo said stands: If you want to change a wall's resistance, just change the Strength value. Yes, it's primitive, but it has worked for almost a decade by now, and unit stances will enable far greater tactical variety than slightly changed walls will.
Kill #773
Support #461
Fight 2
TurretAnim= on tanks is pure laziness. While it may be a valid request, investing hours of coding just so somebody doesn't have to copy & rename 4 files in less than a minute seems disproportionate.
Multiple turret voxels is a pretty silly request...multiple turret voxels for use with what? In order to make use of those, you need support for multiple turrets in the first place. We don't have that. That's request #510, to be discussed next week. Therefore, this part of this request is worthless.
Damaged voxel...a nice idea, and practical for a quick overview of the state of the force.
Spawn-dependent turret...neat little thing, but nothing more.
So yeah...half of the request is worthless from the start, and while the last part is kinda neat, it's not exactly a game-changing über-feature.
I would be interested in having this for the damaged voxels, since I do think that would add a lot to the atmosphere of the game - especially considering buildings already have a damaged state, and that damaged vehicles smoke anyway. Given that there must be an existing check to trigger the latter, it should be easy enough to hook into that and add voxel-changing code.
Unfortunately, it has the same problem any graphics issue has: It would need new voxels, and those are hard to come by for such a specific case. It's also not just damage voxels - there are a bunch of other issues mashed into the request.
Unhardcoding of drain weapons, on the other hand, is a clear, simple, small change that has direct effects on gameplay and can be used by all modders without further prerequisites.
Given that Alex specifically mentioned damaged voxels as well, I will vote to kill the crappy voxel mashup request, but spin off of the good parts as low-priority issues to be done in the undetermined future.
Kill #295
Support #556
Forum Rules
(01.06.2011, 05:43:25)kenosis Wrote: Oh damn don't be disgraced again!
(25.06.2011, 20:42:59)Nighthawk Wrote: The proverbial bearded omni-bug may be dead, but the containment campaign is still being waged in the desert.