If you can find tge unlisted shot delay on the PLC I'd appreciate it.

And please see if it's duplicated on any other weapon.

"m_ChargeInfo.m_ChargeDamageMultiplierCurve.curveIndex": 0
"m_ChargeInfo.m_ChargeDamageMultiplierCurve.m_fMultiplier": 1
"m_ChargeInfo.m_ChargeDamageMultiplierCurve.m_fOffset": 0
"m_ChargeInfo.m_ChargeDamageMultiplierCurve.maxInValue": 1
"m_ChargeInfo.m_ChargeDownCurve.curveIndex": 0
"m_ChargeInfo.m_ChargeDownCurve.m_fMultiplier": 1
"m_ChargeInfo.m_ChargeDownCurve.m_fOffset": 0
"m_ChargeInfo.m_ChargeDownCurve.maxInValue": 1
"m_ChargeInfo.m_ChargeUpCurve.curveIndex": 0
"m_ChargeInfo.m_ChargeUpCurve.m_fMultiplier": 1
"m_ChargeInfo.m_ChargeUpCurve.m_fOffset": 0
"m_ChargeInfo.m_ChargeUpCurve.maxInValue": 1
"m_ChargeInfo.m_bChargeOncePerTriggerPress": "False"
"m_ChargeInfo.m_bFireOnMinCharge": "True"
"m_ChargeInfo.m_eChargeStartType": 0
"m_ChargeInfo.m_fChargeDownTime": 0
"m_ChargeInfo.m_fChargeMoveSpeedMult": 0.7
"m_ChargeInfo.m_fChargeUpTime": 0.6
"m_ChargeInfo.m_fMaxChargeHeldTime": 0
"m_ChargeInfo.m_fMinChargeToFire": 1

Thundergroove:

The 0.5 second delay between shot fired and reload on the PLC. And if there is an iidentical trait on any other weapon.

Does that mean there's currently a system implemented that could be used to dial back the "Lock an, turn around and shoot in the air"-behavior of Swarms? And it's been there all the time? And could be patched in a hotfix?

Since you have access to some variables, do you also have access to some code also? I want to see if Breakin's homing theory is true.

To be specific what I'm looking for is a thread that updates the location which sleeps every 'X' milliseconds. And if it is possible to increase the number of iterations the loop structure would go through.

(UNSURE IF THIS IS HOW SWARMS WORK, DON'T QUOTE ME ON THAT*)

If that can't be seen/can't be posted (unsure if there'll be any legal problems) I understand.

^ if it cannot be seen, is it okay to ask a dev specific questions relating to the code?

* sorry for the caps, phone is dying and well i'm typing in quick reply *

Ah, it's in Python? Sadly I can't pinpoint what i'm looking for then (I've just started to learn Python so I can use Blender).

How about some variables? Anything relating to vehicle speed/location? Or Swarm location? I think that's a good place to start.

I expect some things to be serverside so I understand if it's an impossible find for some things i might ask for.

First understanding the mechanics might be a good starting point, from there i think we as a community can rebuild swarms accordingly...

-I know i'm asking for way too much with this one- is there anything like a JAVADOC there also? It could help us understand just what the variable is used for.

P.S. i have a good feeling for this topic..

A quick idea just came to mind.

Why not give small blasters a 77/63 (the old rails' damage profile against vehicles) profile against vehicles. It's damage is already too low to break recharge but, it can give better combat support in the sense of AV.

Rail = 90s/110a vehicle : 63s/77a infantry
Missile = 79s/119a
Blaster = 77s/63a vehicle : 110s/90a infantry

This will cause:

Rail - Superior AV capabilities, best at vehicle combat support. Some infantry support ability.
Missile - the bridge between AV and AI, equally effective.
Blaster - Superior AI capabilities, best at infantry combat support. Some vehicle support ability.

Well, after hit detection on infantry is fixed.
(Thunder that's your queue)

I know hit detection is dealt with serverside but can you show some blaster variables that we can analyze? I Appreciate it!!

"m_AccuracyProperties.m_fMaxOffsetAngle": 2,
"m_AccuracyProperties.m_fMaxShootAtTimeAccuracy": 1,
"m_AccuracyProperties.m_fMaxStationaryAccuracy": 2,
"m_AccuracyProperties.m_fMinOffsetAngle": 0.12,
"m_AccuracyProperties.m_fNewOffsetInterval": 2,
"m_AccuracyProperties.m_fNoiseConstant": 0.1,
"m_AccuracyProperties.m_fPitchOffsetScalar": 0.1,
"m_AccuracyProperties.m_fShotTimeTillAccurate": 8,
"m_AccuracyProperties.m_fStationaryDecay": 50,
"m_AccuracyProperties.m_fStationaryTimeTillAccurate": 8,

any chance you can find projectile velocities for Missile Turrets, Forge Guns, and Large Railguns? oh, and swarm launchers

more please?

"mEjectHorizontalAngle": 16384,
"mEjectVerticalAngle": 5000,

Opened DB with version debug
Name: 'prj_swarmlauncher_std' | 353038
{
"typeId": 353038,
"typeName": "prj_swarmlauncher_std",
"attributes": {
"NetCullDistanceSquared": 2.5e+09,
"mArcHeight.0": 1000,
"mArcHeight.1": 1000,
"mArmDelay": 0,
"mBounces": 0,
"mConstantTrackingTimer": 0.2,
"mDispertionAngle.0": 0,
"mDispertionAngle.1": 0,
"mEjectVelocity": 40,
"mFlightVfxParameter.floatValue": 0,
"mIgnitionTriggerDistance": 30000,
"mKillRange": 500,
"mLaunchLength.0": 10,
"mLaunchLength.1": 10,
"mMaxRotationSpeed": 12743,
"mMeshScale": 0.5,
"mMissileKillRange": 100,
"mPathMode.0": 1,
"mPathMode.1": 1,
"mProjProp.accelRate": 1200,
"mProjProp.damageDecay": 10,
"mProjProp.damageRadius": 100,
"mProjProp.damageType": 351771,
"mProjProp.directHitDamage": 260,
"mProjProp.explodeByTouch": "True",
"mProjProp.explosionMomentum": 500,
"mProjProp.explosionType": 354592,
"mProjProp.gravityScale": 0,
"mProjProp.initSpeed": 500,
"mProjProp.maxRange": 40000,
"mProjProp.maxSpeed": 6500,
"mProjProp.minimumDamage": 0,
"mProjProp.occludedSplashDamage": "True",
"mProjProp.projectileLifeSpan": 9,
"mProjProp.splashDamage": 19,
"mProjProp.splashDamageType": 351772,
"mRandomModPercent.0": 0.1,
"mRandomModPercent.1": 0.1,
"mSounds.0.isDummyOneShot": "False",
"mSounds.0.isLocal": "False",
"mSounds.1.isDummyOneShot": "False",
"mSounds.1.isLocal": "False",
"mSounds.2.isDummyOneShot": "False",
"mSounds.2.isLocal": "False",
"mSpeedAfterIgnition": 6000,
"mSpiralFactor.0": 0.5,
"mSpiralFactor.1": 0.1,
"mSplashDamage.curveIndex": 0,
"mSplashDamage.m_fMultiplier": 1,
"mSplashDamage.m_fOffset": 0,
"mSplashDamage.maxInValue": 1,
"mSpread.0": 1000,
"mSpread.1": 1000,
"mTeleportingTime": 5,
"mTracing": "True",
"mTrackDelay": 0.8,
"mTrackTurningSpeed.0": 800,
"mTrackTurningSpeed.1": 800,
"tag.0": 353512,
"tag.1": 354887
}
}

The assault swarm launcher is pointless, and should be given a different buff instead of locking on to multiple targets. There is never a need to half your DPS. Instead a faster lock on, or a longer lock on range would be appreciated.

my bad but that is still 360 dps without reload for the regular forge. there is still the option for the assault forge which has higher dps. this thing is still a beast considering the amount of shots per reload and range coupled with the alpha and AI capabilities.

imho this doesnt change the fact that swarms are not as powerful as the pilot wimps are claiming.

if you dont fit your ship properly, dont use your modules and dont react accordingly you die, who would guess.

beside that, if swarm would kill you in that "scrub pilot scenario" then a forge would too.

fun fact, the following fit survives 3 volleys from max skills proto swarm with 2 complex damage mods on a minmando
20GJ Particle Cannon
Basic 120mm Armor Plates
Enhanced Armor Hardener
Complex Light Armor Repairer
Basic Afterburner



the only thing I can agree with is that a dropship needs a lock on warning.

Casually swapping out instantly at a depot is a thing I feel needs to change.

I am that guy who will actually suicide a clone to load AV RIGHT NOW.