4 réponses à ce sujet

[GusJake]

Ok, so I just got done with a Gold match against Geth on Firebase Glacier playing as my Kroguard. I intended the match to be a solo run so I hosted a private lobby. After the 2nd wave I had a random player who wasn't on my friends list join my game.  I'm not even sure how that's possible, but stay tuned 'cuz it gets even better. About half way through the match, after various other random players filled out the remaining slots, I experienced a glitch that made my Krogan completely invulnerable to damage while periodic purple effects pulsated around him. It was like my barrier was recharging instantly and constantly. I have no idea how this happened and I am utterly perplexed at how random players I've never met before managed to join my private game, but it's a bit disturbing to say the very least. Anyone have an idea about what happened?

[GusJake]

Bump, because I'd like to know how people are able to join my private lobby without being my friend or receiving an invite.

Modifié par GusJake, 29 septembre 2012 - 01:46 .

[nanotm]

because you had it set to public and didnt exit multiplayer before starting the private run, the search function only knows what you selected last, next time you want ot randomly do a solo run on private you need to get to the host screen settings and leave it there for 5 minutes wiht your options selected before clicking through to the lobby, yes its a very annoying bug, yes it happens a lot, and experiance will educate you one how to avoid it, if your in a lobby and change options the search function completly ignors them and caries on dropping people into what you think is a private game, it hapopened all wekend durign the op when people were trying ot do the squad goals wiht none full pugs

[phillip100]

Added this into my bug list. If you guys have found any other bugs, please let me know in the following link: http://social.biowar...ndex/14212891/1

[GusJake]

Awesome. Thanks for the replies nanotm and philip100! Hadn't heard of or experienced this bug before, but thanks to your info I should be able to avoid it from now on.