Sponcon: Excite Bike 0.00001x rate
 

How this will work:

This thread is a parody of R^3's rate function. The goal of this thread is to get all of the FFR community to play Excite Bike on 0.00001x rate by posting pictures of arrows in this thread at the right times.

Unlike in R^3's actual rate function, the judgement windows themselves will also be slowed down to 0.00001x rate rather than kept as individual frames, otherwise this would be impossible. (Obviously.)

You may ask: how the hell are we supposed to know when to post? I'm not giving you any hints. You're supposed to work it out yourself. You are allowed to post about strategy and arrow timings and stuff in this thread; it is, after all, a community achievement. (unless you're arcnmx who gave me the frame timings for this thing and you're not supposed to just go and tell everyone)



Rules

Each person may only post one arrow in total in this thread. That way we get 32 people in total to post arrows for a FC and make it truly a community effort.

**NO POST EDITING.** If you post an arrow by mistake, it's staying there and everyone will hate you. I'm sorry to be a killjoy, but this is how FFR is supposed to work: if you make a mistake, you have to accept it and move on, or start over; you can't correct it while you go along, haha. If I see an arrow posted with an "edited" line under the post it will be ignored and I might have to ignore all other posts by you in the thread or something... Just don't edit your posts, OK? And if you're a mod/admin/whatever don't edit other people's posts to fudge the arrow timings.

How to post an arrow: Just post a picture of an arrow pointing the correct way. It doesn't have to be a picture of an FFR arrow, any picture is fine, as long as it's obvious which way it's pointing.

If your image host goes bankrupt or whatever I will very reluctantly let you edit your post.

Don't use the mirror mod. (obviously)

Also I'm not going to tell you whether your post was an Amazing/Perfect/Good/Average/Boo until the very end of this thing, because I'm lazy. Let's just pretend you have arrow judgements turned off.



Scoring and credits

I will use combo scoring. The total credit payout, as it currently stands, is equal to your total combo score (max: 49600). If I get donations (please? :D ), I will multiply your combo score by the appropriate number. (i.e. so if you only score half the max total, only half the credit pot will be paid out and the other half returned, no matter what the credit pot is)

Payouts: I will split the credit pot so that your share of the credits will be in the ratio 10:5:2:1:0 according to whether you contributed an Amazing, a Perfect, a Good, an Average, or a Boo. This is to discourage people from sabotaging the community effort by purposefully submitting an average or early good to get credits, not that anyone would do that, but just saying.

Re: Sponcon: Excite Bike 0.00001x rate
 

"BOO"

Re: Sponcon: Excite Bike 0.00001x rate
 

0-frame jack

banned for hack

gf sponcon

Re: Sponcon: Excite Bike 0.00001x rate
 

Re: Sponcon: Excite Bike 0.00001x rate
 

55 minutes per frame btw, have fun.

Re: Sponcon: Excite Bike 0.00001x rate
 

Indeed. The time between two arrows is so significantly large that you cannot expect this to succeed in any way.

Perhaps you should try making the rate 10 times higher. That way this would only last a couple of months.

Re: Sponcon: Excite Bike 0.00001x rate
 

It only takes 7.8 days.

Re: Sponcon: Excite Bike 0.00001x rate
 

Oh. I read it as 0.00001%.

Re: Sponcon: Excite Bike 0.00001x rate
 

i would like a bubble wrap dispenser for my car one day

Re: Sponcon: Excite Bike 0.00001x rate
 

0.03333333333333333333333333333333 seconds each frame normal rate

3333.3333333333333333333333333333 seconds for each frame on 0.00001x rate

First note: 153333.33 [ 46 x 3333.333 ]
Second note: 163333.317 [ 49 x 3333.333 ]
Third note: 186666.648 [ 56 x 3333.333 ]
Fourth note: 209999.979 [ 63 x 3333.333 ]
Fifth note: 223333.11 [ 67 x 3333.333 ]
Sixth note: 246666.642 [ 74 x 3333.333 ]
Seventh note: 279999.972 [ 84 x 3333.333 ]
Eighth note: 303333.303 [ 91 x 3333.333 ]
Ninth note: 313333.302 [ 94 x 3333.333 ]
Tenth note: 336666.633 [ 101 x 3333.333 ]
Eleventh note: 373333.296 [ 112 x 3333.333 ]
Twelfth note: 396666.627 [ 119 x 3333.333 ]
Thirteenth note: 419999.958 [ 126 x 3333.333 ]
Fourteenth note: 429999.957 [ 129 x 3333.333 ]
Fifteenth note: 453333.288 [ 136 x 3333.333 ]
Sixteenth note: 536666.613 [ 161 x 3333.333 ]
Seventeenth note: 559999.944 [ 168 x 3333.333 ]
Eighteenth note: 583333.275 [ 175 x 3333.333 ]
Ninteenth note: 606666.606 [ 182 x 3333.333 ]
Twentieth note: 616666.605 [ 185 x 3333.333 ]
21st note: 639999.936 [ 192 x 3333.333 ]
22nd note: 653333.268 [ 196 x 3333.333 ]
23rd note: 676666.599 [ 203 x 3333.333 ]
24th note: 699999.93 [ 210 x 3333.333 ]
25th note: 709999.929 [ 213 x 3333.333 ]
26th note: 733333.26 [ 220 x 3333.333 ]
27th note: 746666.592 [ 224 x 3333.333 ]
28th note: 756666.591 [ 227 x 3333.333 ]
29th note: 779999.922 [ 234 x 3333.333 ]
30th note: 803333.253 [ 241 x 3333.333 ]
31st note: 826666.584 [ 248 x 3333.333 ]
32nd note: 836666.583 [ 251 x 3333.333 ]

60 seconds in one minute
3600 seconds in one hour
86400 seconds in one day

Since the first note was already hit at the amazing frame, we are actually starting on the second note (it is a down arrow). 163333.317-153333.33 is 9999.987 seconds, which means the down arrow (second note in the song) will be hit at approximately 167 minutes after the thread was created today (3:36 PM to 6:23 PM EST)

This also means [836666.583-163333.317] = 673333.266, meaning this entire process will take 7.7932090972222222222222222222222 days.

Re: Sponcon: Excite Bike 0.00001x rate
 

Best poll NA...

Worst 400th post NA...

Re: Sponcon: Excite Bike 0.00001x rate
 

Thanks for confirming my really quick approximation was pretty much correct lol

Re: Sponcon: Excite Bike 0.00001x rate
 

Third note (up arrow) will be hit 389 minutes after the second note; 6:23 PM EST to 12:52 AM EST since it's seven frames apart.

Basically to figure out when to hit the next note, look at the beatbox data and see how many frames apart each note is. 56 and 63 is seven frames apart meaning that the fourth note (down) will be hit ~389 minutes after the third note, august 15th 12:52 AM EST to august 15th 7:21 AM EST.

Take 3333.33 and multiply by how many frames apart something is. e.g. 3333.33x7 frames apart is 23333.31, divide by 3600 to get the hours. Then multiply by 60 to get the minutes.

Essentially this is a spon con where the users are rushing to calculate when to post the next notes, lol.

I put the frame data in this post.

The big problem here however is the rounding issue. I got 389 from 388.88883333333333333333333333333 and 167 from 166.66666666666666666666666666667, so there will be some minor timing issues.

Re: Sponcon: Excite Bike 0.00001x rate
 

No one hit the 2nd note yet though, just me whooshing at nothing (sun)

Re: Sponcon: Excite Bike 0.00001x rate
 

not really spontaneous if you ask me

Re: Sponcon: Excite Bike 0.00001x rate
 

Wait, so what does this mean in terms of timing on posts? 3333 seconds for a frame on .00001 rate is a little less than an hour, so would being a few minutes off in the calculations due to rounding still make amazings?

Also guys 6:23 PM EST is approaching in a few minutes; get ready to post the down arrow for the second note

Re: Sponcon: Excite Bike 0.00001x rate
 

...OOOOOH, I get this thread now. Haha. Wow, this is kind of clever.

Re: Sponcon: Excite Bike 0.00001x rate
 

Amazing!

Re: Sponcon: Excite Bike 0.00001x rate
 

inb4 dossar AAA's Excitebike 0.00001x

Re: Sponcon: Excite Bike 0.00001x rate
 

First note was hit August 15th, 3:36 PM EST (2:36 PM Server Time. For server time, subtract an hour from EST)

Frame differences from the previous note

2nd note [down] : 3 [ frame 46 to frame 49 ] <-- hit on August 15th, 6:23 PM EST
3rd note [up] : 7
4th note [down] : 7
5th note [left] : 4
6th note [right] : 7
7th note [up] : 7
8th note [down] : 7
9th note [up] : 3
10th note [right] : 7
11th note [up] : 11
12th note [up] : 7
13th note [up] : 7
14th note [down] : 3
15th note [left] : 7
16th note [right] : 25
17th note [up] : 7
18th note [down] : 7
19th note [left] : 7
20th note [down] : 3
21st note [up] : 7
22nd note [right] : 4
23rd note [down] : 7
24th note [up] : 7
25th note [left] : 3
26th note [down] : 7
27th note [up] : 4
28th note [right] : 3
29th note [left] : 7
30th note [down] : 7
31st note [up] : 7
32nd note [right] : 3

This is for calculating how long you need to wait in between every note. Currently we've hit the first two notes, so we need to wait ~389 minutes for the third note, going from 6:23 PM EST to August 16th 12:52 AM EST. I'm not exactly sure if the rounding discrepancies will be big enough that we'll get some perfects instead of amazings.