[Exploit] Dev Version can Allow False Victories on ICO

In a game I just finished which desynced in the first ten minutes, I was using the dev version (I mod frequently, so I just use it by default, though I had no mods enabled).  Anyways, after the other human in the FFA gave up, I decided to try something..

I decided to see what happens if I tried Ctrl+Shift+.+a+c+e on all enemy planets.  For those of you unfamiliar with the dev version of the game, that keystroke will colonize any selected planets.  In other words, if someone started to lose while using the dev version, they could just wipe out all enemies in this manner.  They'll receive a victory screen and it will count as a win on their record.  The other human had already quit, so unfortunately, I couldn't check if he would have received a loss screen.  My guess would have been no.

UPDATE: I just tested with another couple of players.  Once again, I received a victory screen and my ICO profile had it's win count incremented.  The other players however didn't receive loss screens.

4,529 views 10 replies
Reply #1 Top

In a game I just finished which desynced in the first ten minutes, I was using the dev version (I mod frequently, so I just use it by default, though I had no mods enabled). Anyways, after the other human in the FFA gave up, I decided to try something..

I decided to see what happens if I tried Ctrl+Shift+.+a+c+e on all enemy planets. For those of you unfamiliar with the dev version of the game, that keystroke will colonize any selected planets. In other words, if someone started to lose while using the dev version, they could just wipe out all enemies in this manner. They'll receive a victory screen and it will count as a win on their record. The other human had already quit, so unfortunately, I couldn't check if he would have received a loss screen. My guess would have been no.

Such ability to artificially inflate one's record needs to be fixed before the game goes live.

Oh there are much easier commands to win with the dev.exe. But using any of them that cause affect gameplay will result in an instant desync. So I don't think its a very big deal. Its easy enough to inflate your win record if you want to, I don't think its a huge exploit.

Reply #2 Top

I know it's not difficult to inflate it, but it is rather overly easy...

Reply #3 Top

Here we have our one shot to make us modders look good, and you have to go and ruin it...the pros would never have figured it out, half of them probably don't even use the damn thing...

Reply #4 Top

if dev exes and normal exes can play in the same game together, then... thats not right.

Reply #5 Top

Quoting Pbhead, reply 4
if dev exes and normal exes can play in the same game together, then... thats not right.

The problem is you can still get a win on your record on a desynced game. The dev just happens to be able to induce them at will and make winning a breeze.

Actually I think using the dev.exe on normal ICO games might be the best way to track down the desync error since it lets you know when you desync, which is of value to everyone.

Reply #6 Top

Quoting Seleuceia, reply 3
Here we have our one shot to make us modders look good, and you have to go and ruin it...the pros would never have figured it out, half of them probably don't even use the damn thing...

In the first game, the other guy had already quit and in the second, the other guys consented to the test and I reported this issue on here immediately.  I did nothing wrong.

 

Also, Goa, what setting/overlay displays when a desync occurs?

Reply #7 Top

Thanks for the info!

Reply #8 Top

Quoting Volt_Cruelerz, reply 6
In the first game, the other guy had already quit and in the second, the other guys consented to the test and I reported this issue on here immediately. I did nothing wrong.

Volt, I was totally kidding man...

Reply #9 Top

Quoting Volt_Cruelerz, reply 6
Also, Goa, what setting/overlay displays when a desync occurs?

The screen goes darker and red words saying desync go over the middle of the screen. You can't miss it. ;)

Reply #10 Top

Somehow I missed it lol, then again, I'm colorblind, so maybe that caused it..