Games in Progress: 3 | Players logged in: 5 | Players Registered: 37413 | Games Played Total: 68655
Print Page - Losing money when gambling ($-179 in the pub)

Planet M.U.L.E.

Planet Mule 1 => Bugs 1.2.1-3 => Topic started by: Core Xii on February 17, 2010, 20:16



Title: Losing money when gambling ($-179 in the pub)
Post by: Core Xii on February 17, 2010, 20:16
You can "win" negative amounts of money in the pub, which is then taken away from your bank.

Steps to reproduce:
  • Catch mountain wambus (but don't close the message that you caught it)
  • Wait for ~90 seconds
  • Press Button to close wambus message
  • Go to pub

  INFO [DevelopmentMessenger.showMessage]            Core Xii caught the Mountain Wampus and got $100
  INFO [MuleGameContainer.logSkippedFrames]          Skipped frames: 62
  INFO [MuleGameContainer.logSkippedFrames]          Skipped frames: 61
  INFO [MuleGameContainer.logSkippedFrames]          Skipped frames: 61
  INFO [GameModel.gamble]                            (P10) Core Xii gambles $-179, max: 47.5, left: -92.8, fraction -1.9536843
  INFO [DevelopmentMessenger.showMessage]            Core Xii won $-179 in the pub


Title: It is possible to lose money when gambling
Post by: Keybounce on February 18, 2010, 02:20
When you find the mountain wumpus, the game pauses.

But as far as the gambling in the casino is concerned, the timer does not pause.

If you spend the time at that point to talk with the other players, your gambling income will go down, and it can go negative.

This was repeated, and resulted in less-than-zero, changed to zero.


Title: Re: It is possible to lose money when gambling
Post by: Intergalactic Mole on February 18, 2010, 03:09
You should post a link to the game in which this happened.


Title: Re: It is possible to lose money when gambling
Post by: mikman on February 18, 2010, 13:21
It was this game in development 2.
http://www.planetmule.com/hi-score-game/game?game_id=19092


Title: Re: Core Xii won $-179 in the pub
Post by: Peter on February 19, 2010, 07:21
Oops. Thanks for the report. We've noted it and it will be fixed in the next version.