• (disco)

Wait, are you guys making up prize names on the spot?

Congratulations on this new set of embellished requirements, the president's daughter would be proud of this achievement.

• (disco)

Thanks for the great description, Remy :-) I'm a bit surprised, and overly joyful that my submission actually made it through!

As I already wrote in the README: There is a way to "cheat" in such a way that nobody can realistically notice. If someone wants to be walked through the maths, raise your hand. Otherwise I'm going to be too lazy :stuck_out_tongue:

• (disco)

You're going to figure out a way to rip off this slot machine, and rebuild your bankroll.

Why? You already have a perfectly good skewed roulette wheel...

• (disco)

Ben - (everything assumes a 38 number USA, double-zero wheel)... On the first spin, the odds of a number coming up is nearly 100% (it would be 100% if we exclude the chance various "problems" such as the ball leaving the wheel - rare, but it does happen). Now for a second spin (fair wheel), the odds of the same number coming up are 1/38 [because we don't care what the first number was, only if they are the same]. This is radically different than the article (assuming I did not misread while having my first cup of coffee) stating odd of 1/1444 - (aka 1/(n*n)

• (disco) in reply to JBert

As I mentioned, the judging is entirely subjective, and I want to highlight clever and fun solutions, and yeah, we're making up prize names. Although "Bruce Said So" might stick around.

• (disco) in reply to Remy

The venerable IOCCC does the same thing.

• (disco) in reply to Maciejasjmj
Maciejasjmj:
You already have a perfectly good skewed roulette wheel...

Why not make the slot perfectly fair and get a certain waitress to play it…

• (disco)
You had padded it, anyway- apparently while Gilda was showing you out the back door with one hand, she stole your wallet and got a really big tip with the other.

What did the protagonist smoke to forget you NEVER. EVER. EVER. have all your money in one place?

• (disco) in reply to dkf
dkf:
and get a certain waitress to play it…

I'd rather Get In The (waitress') Slot.

Filed under: awaiting more creative euphemisms from @remy

• (disco) in reply to TheCPUWizard

Err, yes, that's perfectly true for a fair roulette wheel; I am aware of that.

However, even the requirements don't want a fair roulette wheel. Both implementation and documentation (so this is "veritable") describe that, if a duplicate is about to happen, we spin the wheel again. So in order to actually see a duplicate, the following must happen:

First call to FewRunsWheel.operator()(). This calls FairWheel.operator()(). Returns a number, let's say [s]42[/s] err 23 for example. Return that number.

Second call to FewRunsWheel.operator()(). Calls FairWheel.operator()(), which returns 23 again. FewRunsWheel detects that, and drops the result, instead calling (and then returning blindly) again: FairWheel.operator()(), returning 23 a third time

I think we can agree that FewRunsWheel.operator()() returning the same number three times in a row has probability 1/(n*n)

• (disco)

“GRT JOB,”

"Greet job"?

Anyway, since these are kind-of but not really obfuscated coding contests, I propose that they instead be dubbed obfuscated requirements contests. Somewhere, in the vast jumbled expanse between "this part is just for flavor" and "it must do this", there is an actual requirement. Can you find it?!

• (disco) in reply to Zylon
Zylon:
I propose that they instead be dubbed obfuscated requirements contests.

Just like normal requirements!

• (disco) in reply to Zylon

Hmmm, ORC does have a ring to it...

• (disco) in reply to JBert
JBert:
the president's daughter would be proud of this achievement.

I am!

• (disco)

Right now on the radio news in Germany:

http://www.desmoinesregister.com/story/news/2015/04/11/prosecutors-evidence-indicates-lottery-vendor-employee-tampered-equipment/25629733/

Edit: I like the position the article is cropped here. (For future documentation a screen snapshot)

[image]
• (disco) in reply to PWolff

So the ticket almost lapsed. I guess he kept sending "you could be a winner" e-mails and got no reply.

• (disco) in reply to PWolff
PWolff:
tampered with lottery equipment before buying a Hot Lotto ticket that would go on to win \$14.

Well, that's not really worth it, is i...

article:
tampered with lottery equipment before buying a Hot Lotto ticket that would go on to win \$14.**3 million**

Nevermind, DiscoOneBox...

• (disco)

Works with Twitter contests, too:

http://www.hscott.net/twitter-contest-winning-as-a-service/

I affirm that I searched thedailywtf.com for mentions of this and didn't find any.

In particular for the spelling of the first comment I searched for a user named Alec. No results found.

• (disco) in reply to PWolff

Um... I mixed two similar things up... :no_mouth: my bad...

What was/is on our radio news is this:

http://www.heise.de/newsticker/meldung/Polizei-Spielautomaten-Hacker-kassierten-mehrfach-ab-2533374.html

Translation of title and abstract (as well as I can do at the moment):

##Slot Machine Hackers Repeatedly Cashed Up

####Gelsenkirchen police incriminate several persons of having manipulated the software of slot machines for their own gain. Initially, they are believed to have co-operated with the operators of the machines, but to have them deceived afterwards.

(corrections welcome)

According to the radio commentary, initially the deceived ones were the players, but then the programmers of the software exploited a "flaw" in the software.

So, basically, the same as this contest is about.

### Leave a comment on “The Lucky Deuce: Getting in the Slot”

Log In or post as a guest

Replying to comment #:

« Return to Article