Project Reality Forums

alright, so we played Iron eagle Skrimish today on IDF, and the MEC has captured our South bridge while we were camping on the TV station,
after a while TONS of MEC has started swarming towards the TV Station roof, and we started taking them out, we got down and suddenly we spotted the MEC has a SPAWN Point Just next to the TV Station Right where the IDF's Spawn Point is.

we concluded that After the MEC are capturing the South bridge a Spawn point appears, therefor Three of our Squad were sent to Re capture South bridge while the other three Just laying down and aiming at the spawn point to spawn kill any MECs.

after we Captured the Spawn point we left the position and started to move up, except for our Sniper and designator, who after a while we went back suddenly shouted they're being attacked again, we ran back and noticed that they can still spawn on our TV Station Even though we Got Bijar neutral and South Bridge ours by that time.

where is the exact map location?
any screenshots?

please rename the thread like this:
[0966] iron eagle - spawnpointbug @ tv station

and next time use the bugreport template:
https://www.realitymod.com/forum/f26-pr ... -bugs.html

thank you

K4on wrote:where is the exact map location?
any screenshots?

please rename the thread like this:
[0966] iron eagle - spawnpointbug @ tv station

and next time use the bugreport template:
https://www.realitymod.com/forum/f26-pr ... -bugs.html

thank you

sorry for that, regarding the location : if you look towards the TV Station its on the most Right pole, if you Capture South bridge as MEC and go to the Spawn screen you should see it.


NOTE - I Havent tested if you Can spawn on the MEC base as IDF if you capture the Construction site - This should be looked at aswell.

I've Just RE Checked it and noticed one major thing -

THE MEC Can spawn on the TV station When they Capture Bijar! NOT south bridge

meanings - its enough they capture Bijar and they can spawn on IDF Base

anything?

thanks for reporting this bug. The bug is fixed for next version.