You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: engine/Core/Blueprints/ProjectileBlueprint.lua
+3-2Lines changed: 3 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -66,7 +66,7 @@
66
66
---@fieldLeadTargetboolean
67
67
--- Whether projectiles should try to stay underwater. Applies only to tracking projectiles.
68
68
---@fieldStayUnderwaterboolean
69
-
--- if the projectile is initially affected by gravity
69
+
--- if the projectile is initially affected by gravity (-4.9 ogrids/second/second)
70
70
---@fieldUseGravityboolean
71
71
--- projectile will detonate when going above this height above ground
72
72
---@fieldDetonateAboveHeightnumber
@@ -133,7 +133,8 @@
133
133
---@fieldMaxZigZagnumber
134
134
--- frequency of zig-zag directional changes, in seconds
135
135
---@fieldZigZagFrequencynumber
136
-
--- realistic free fall ordinance type weapon
136
+
--- When true and weapon muzzle velocity is 0, the projectile's horizontal velocity is set in the direction of the target with the speed of the weapon firing the projectile.
137
+
--- Used for realistic free fall ordinance type weapons like bombs
-- If we are in the upgrading state, then it's the upgrade we want under normal circumstances.
169
+
-- We don't use different upgrades paths for coop, only that of the original SCFA (no Support Factory upgrade paths whatsoever)
170
+
-- If you decide to mess around with AI armies in cheat mode, and order a newly added upgrade path instead anyway, then any mishaps happening afterwards is on you!
--- Failsafe thread that will periodically loop through existing units that have been converted to lower tech level units so they can be built (ie. HQ factories)
1147
+
--- If their unit IDs don't match the one set in the save.lua file, a failsafe function will be called to check if they are idle, so an upgrade can be started
-- Structure upgrading should take priority, so the check for unit.UnitBeingBuilt is not needed. This check is a lot more reliable to get factories to upgrade
1091
-
ifunit.UnitId~=v.FinalUnitandnotunit:IsBeingBuilt() andnotunit:IsUnitState('Upgrading') then
1092
-
self:ForkThread(self.BaseManagerUpgrade, unit, v.UnitName)
1093
-
end
1155
+
-- Check if the structure exists, and needs to upgrade
0 commit comments