Static Object coalition mismatch

[kira_mikamy]

Hi,
I may be missing something here, but I noticed what seems to be a coalition inconsistency affecting some static objects.

If certain static objects (for example an Oil Rig or a FARP (helipad) ) are placed under the Red coalition in the Mission Editor, they appear red at mission start. However, if any Blue unit approaches them during gameplay, their F10 map icon switches to Blue, as if the object had been captured.

The issue:
In the detailed info panel, the object’s coalition remains Red, even though the icon visually shows it as Blue.
This means scripts relying on coalition checks (e.g., Object.getCoalition() or similar) still see the object as Red, making capture detection unreliable.

This behavior occurs with at least the Oil Rig and FARP (helipad) , and it’s possible other static or capturable objects may behave the same way. I’m not sure if this is already known, but it seemed worth reporting.

 

Edited Wednesday at 12:38 AM by kira_mikamy
typo

[DJOGOO]

18 ore fa, kira_mikamy ha scritto:

Hi,
I may be missing something here, but I noticed what seems to be a coalition inconsistency affecting some static objects.

If certain static objects (for example an Oil Rig or a FARP (helipad) ) are placed under the Red coalition in the Mission Editor, they appear red at mission start. However, if any Blue unit approaches them during gameplay, their F10 map icon switches to Blue, as if the object had been captured.

The issue:
In the detailed info panel, the object’s coalition remains Red, even though the icon visually shows it as Blue.
This means scripts relying on coalition checks (e.g., Object.getCoalition() or similar) still see the object as Red, making capture detection unreliable.

This behavior occurs with at least the Oil Rig and FARP (helipad) , and it’s possible other static or capturable objects may behave the same way. I’m not sure if this is already known, but it seemed worth reporting.

 

+1

[Spooky_555]

18 ore fa, kira_mikamy ha scritto:

Ciao,
forse mi sfugge qualcosa, ma ho notato quella che sembra essere un'incoerenza nella coalizione che interessa alcuni oggetti statici.

Se determinati oggetti statici (ad esempio una piattaforma petrolifera o un FARP (eliporto)) vengono posizionati sotto la coalizione rossa nell'editor di missioni, appariranno rossi all'inizio della missione. Tuttavia, se un'unità blu si avvicina durante il gioco, la sua icona sulla mappa F10 diventerà blu, come se l'oggetto fosse stato catturato.

Il problema:
nel pannello informativo dettagliato, la coalizione dell'oggetto rimane rossa, anche se l'icona la mostra visivamente come blu.
Ciò significa che gli script che si basano sui controlli di coalizione (ad esempio, Object.getCoalition() o simili) vedono ancora l'oggetto come rosso, rendendo inaffidabile il rilevamento della cattura.

Questo comportamento si verifica almeno con la piattaforma petrolifera e il FARP (eliporto), ed è possibile che altri oggetti statici o catturabili si comportino allo stesso modo. Non so se questo sia già noto, ma mi è sembrato opportuno segnalarlo.

 

+1

 

[AlessandroFuBu]

18 ore fa, kira_mikamy ha scritto:

Hi,
I may be missing something here, but I noticed what seems to be a coalition inconsistency affecting some static objects.

If certain static objects (for example an Oil Rig or a FARP (helipad) ) are placed under the Red coalition in the Mission Editor, they appear red at mission start. However, if any Blue unit approaches them during gameplay, their F10 map icon switches to Blue, as if the object had been captured.

The issue:
In the detailed info panel, the object’s coalition remains Red, even though the icon visually shows it as Blue.
This means scripts relying on coalition checks (e.g., Object.getCoalition() or similar) still see the object as Red, making capture detection unreliable.

This behavior occurs with at least the Oil Rig and FARP (helipad) , and it’s possible other static or capturable objects may behave the same way. I’m not sure if this is already known, but it seemed worth reporting.

 

+1

[- Sonic -]

+1 absolutely

[Teuzzracer]

I confirm the reports expressed above