View Issue Details

IDProjectCategoryView StatusLast Update
0006015Spring engineGeneralpublic2018-09-22 17:25
ReporterDoo Assigned To 
PrioritynoneSeverityfeatureReproducibilityN/A
Status closedResolutionwon't fix 
Summary0006015: Feature Request - HighTracjectory functionalities
DescriptionHello!
Our thuds/hammers use a pretty annoying script + weaponDefs setup to try and get some kind of High/Low traj capabilities since BA 10.00.
What I wanted to request here are 2 new possibilities for the "highTrajectory" weaponDefs key.
current is:
0 = Low Trajectory
1 = High Trajectory
2 = Low/high Traj via button (manually)

I would like to propose adding:
3 = Low/High capable, low priority
4 = Low/high capable, high priority

What it would acheive: A weapon set to Low/High traj capable/low priority would be able to shoot at both low and high trajectories depending on the situation. Whenever the target is in range but the unit can't fire in low trajectory, it would attempt to use the high trajectory.

This is currently (poorly) implemented in BA (on thuds and hammers) via two weapons (high traj/lowtraj), a gadget checking for targets and setting up a cob value, and a cob script blocking either weapon 1 or 2 depending on that value. The setup being sometimes glitchy, (firing both weapons at once ocasionnally), i'm asking for this feature to be formally integrated to the engine.
Additional Informationarmham unitDefs/weaponDefs: https://github.com/Balanced-Annihilation/Balanced-Annihilation/blob/master/units/ArmKbots/armham.lua
armham bos: https://github.com/Balanced-Annihilation/Balanced-Annihilation/blob/master/scripts/armham.bos
gadget that switches from high to low traj weapons: https://github.com/Balanced-Annihilation/Balanced-Annihilation/blob/master/luarules/gadgets/unit_plasma_auto_hightraj.lua
TagsNo tags attached.
Checked infolog.txt for Errors

Activities

Kloot

2018-09-19 20:25

developer   ~0019360

the overwhelming majority of games played in BA's community have been running on 103.0 for months now, and I don't see much willingness (from say autohost owners) to move away from it.

if you want engine development to continue at all on BA's behalf, this status quo has to end soon. if not, all I can do is close your request.

Issue History

Date Modified Username Field Change
2018-07-17 18:28 Doo New Issue
2018-09-19 20:25 Kloot Note Added: 0019360
2018-09-22 17:25 Kloot Status new => closed
2018-09-22 17:25 Kloot Resolution open => won't fix