7 replies to this topic

[rodanoS]

Ok, I know bring collision back is a tough job. Fixing netcode, hitbox, and all other to-do-list... I am not suprised by it takes long time.


But it has low priority than CW? For ****'s sake, collision is not only balance issue involved with light mechs, but also BASIC GAME MECHANISM.


We are now watching 100 ton's of metal hulls are bouncing each other like rubber ball and you think it's OK?


It makes game look crummy. So, this is proper priority I think.


1. Bug fix

2. Netcode fix

3. Collision


These BASIC MATTER should come forward. perhaps new mechs, game-mods, maps can wait...

[Megalosauroid]

PGI wont re-implement collisions until they finish rolling out the force fields and active camouflage for light mechs.

[Terran123rd]

They didn't say low, just not top. It's probably 3rd behind netcode and CW.

[SpajN]

Yeah it is low priority

I rather take CW a month earlier than collision.

[Homeless Bill]

They've also stated they want netcode fixed before collision, and that that's the main barrier for it right now. As soon as netcode is fixed, I suspect collision won't be more than a couple weeks behind.

[Tennex]

What the hell indeed.

Especially since its already in the game. And they just hav to reactivate it. Do they really listen?

[Das Wudone]

collision should come after the netcode fix. community warfare is a vital aspect of the game and i would bet everyone will take that rather than collision 1st.

[Brilig]

Homeless Bill, on 22 January 2013 - 06:34 PM, said:

They've also stated they want netcode fixed before collision, and that that's the main barrier for it right now. As soon as netcode is fixed, I suspect collision won't be more than a couple weeks behind.

I'll throw my vote in with this idea. Also seems like that's what the plan has ben for a while. http://mwomercs.com/...t-code-roadmap/