Open ante185 opened 1 year ago
IIRC this happens when the specops marker is within ~1km of a rebel marker when spawned. It's a bit tricky to completely fix because the spawning decision & timing is entirely separate from the mission, although the vast majority of situations would be solved by not including currently-unspawnable specops markers when selecting the mission.
Alternatively we could flip the specops markers to rebel when HQ is moved near or a marker within 1km is captured, but I think it's supposed to be doing that already...
Huh, it does already check the 1km rebel marker case when requesting the mission. The only holes I can see:
Seems fairly unlikely although we can probably work around both. Force-spawning the specops marker for the mission duration for #1, triggering mission completion regardless of side switch for #2.
Ugh, misreading this shit again. Need more sleep to deal with this one.
It's worse than I thought anyway. There's currently no way of detecting whether a spawned specops marker already has specops on it or not. That information is entirely transient. Might be best to just finish rewriting the garrison system first.
Describe the bug
SpecOps are either just not being spawned in the areas they are supposed to spawn in, and/or the assassination mission does not proc a squad to spawn. When the time runs out to achieve it the mission is counted as a success.
How to reproduce
Get an assassination mission from Petros (Dynamically/requested) Arrive to the AO - look around for way too long Get frustrated - enter spectator mode and find that the only enemies within miles are the ones guarding the nearby resources
Version
3.2.0
Have you altered the code?
Yes
What i have changed
Map
Altis
What server?
LAN Hosted
Time bug occured (Server time/UTC)
No response
Mods
Additional context
No response