PDA

View Full Version : CrimeCity robbery glitch



Babytway
04-12-2012, 04:03 PM
hello team,
last couple days i have notice that when i rob a hood i leave all cash on ground(un-collected) until i rob every building i want then i collect all at once and then bank it right away. well the glitch is if i get attacked while im in that hood the attacker is winning money off of me when i haven't even picked the money up off the ground yet. so when i do pick up is the money that the attacker won deducted from me or do i still get the whole amount seeing as though i didn't have the cash on me at the time

ryusho
04-13-2012, 03:26 AM
There was a recent update to the system that immediately credited the player's account with winnings from their robberies/attacks, whether the money/items have been picked up from the hood or not. This was done to prevent players from missing out on their winnings if the game crashed after a robbery/attack. (This information was gleaned from the change-log of the Crime City app.)

Please correct me if I'm mistaken on this update info.

Vile Lynn
04-13-2012, 01:41 PM
Yeah, it is not a glitch... same goes for loot, it goes into inventory even though you haven't picked it up yet.

I like the change. I had a few crashes, logged back on & had the cash that I left, luckily I haven't (yet) been robbed in the meantime.

Baby, since you rob so much, players are gonna know that you have un-banked cash if they catch you on a robbing spree.

Babytway
04-14-2012, 08:12 PM
its not unbanked cash because i dont even have it on me. and when i do pick it up all goes into my bank. im not losing any cash. i understand that the money will auto be credited to you if you exit the app or it crashes i know about that part.

ryusho
04-16-2012, 12:17 AM
its not unbanked cash because i dont even have it on me. and when i do pick it up all goes into my bank. im not losing any cash. i understand that the money will auto be credited to you if you exit the app or it crashes i know about that part.

Just change your understanding to "money will be auto-credited to you the moment you win a robbery/attack". So whether you pick it up or not, the server has already updated your cash on hand to include the winnings. If you choose not to pick it up, only you won't see it as cash on hand. Everyone else looking to attack/rob you will see it as cash on hand.

When you do get attacked, whether you pick up the cash or not, the amount lost is deducted from whatever the server has updated your cash on hand to be. So once you pick up the cash and immediately bank it, your net gain is your total winnings minus the amount lost to attacks 'times 0.9' (10% cost of banking; may not be applicable for those with the free banking gun).

Moral of the story since the new update: Bank immediately after each win if you don't want to risk any loss in winnings.

Chikita da Bamma
04-16-2012, 09:47 AM
Whether the behavior of having the balance of winnings available to be lost or robbed from you before you "pick it up" is correct or not is debatable, but that is not to the point.

What is to the point is that it creates a logical design flaw, and that flaw leads to a bug.

When the cash on hand balance on the server is different from the cash on hand balance shown on the App then there is a design flaw.

And because the balance is not re-synced after each transaction, together with the fact that balances aren't allowed to go negative in the App, a bug occurs.

Imagine I win $1,000 in a fight but don't pick it up. The server says my cash balance is $1,000 but the App still shows $0 because the bundle of cash is still lying on the ground. Then I lose the next fight, and the person I attacked gets $100 (10% of my cash on hand.) My server balance is now $900, my app still shows $0, and there's still a $1,000 bundle on the ground. When I pick up the cash, the app now says my balance is $1,000, even though I really have only $900. If I go to the Bank to deposit it, only $900 transfers from cash to bank, and so the app shows me having $100 on the screen, when I really don't, because that $100 is the money I lost when I attacked a second time.

And the system doesn't resynchronize until the next login.
Fail.

Chikita da Bamma
04-16-2012, 10:00 AM
And the bug compounds, because the app will let me buy Equipment on the basis of my cash, and show that I have the purchased equipment in my inventory, even when I don't as far as the server is concerned. Like in the previous example, if I then use my $100 "balance" to buy 2 Molotov cocktails, the app will say that I have two more of them than I really do. The disparities between the app and the server just increase over time, until things get really crazy.

ryusho
04-16-2012, 10:51 PM
This may seem sound in theory with an imaginative scenario, but practically it doesn't work that way. Hence, there is no bug. If you've tried out your scenario you've posed, you'll realise that there is no design flaw. There are in-game mechanics involved which I will not discuss since I'm not a Funzio staff member.

Chikita da Bamma
04-17-2012, 08:54 AM
practically it doesn't work that way.

Then I guess the ~ $20,000 of explosives I bought that way to confirm my posting "practically" don't exist that way, either. :p However, I just tested it again and it no longer works. But the explosives I bought this morning did stay in my Inventory after logging out and logging back in.

I also saw this evening a series of posts on some rival's Comments from someone who implied that he had done the same with her, deliberately losing money to her, and thanking her (!) for being so strong (+22K defense) and having so much income (over $50K/hr!) that he could "build himself up" and hoping she appreciated the money he lost to her....

After I posted the previous comment (about the bug letting you buy things with "virtual" unearned money) I thought I should delete it, since it basically gave away one of these money hacks, but now that I see it has (apparently) been fixed I don't mind discussing the details.

It was not just an imaginative scenario, it was a bug, but now it's been fixed.