THIS is how to Stress Test!

Today going to be starting the public testing for the @Tippy service. Please do not confuse this with the bot being completed or deposit yet nor think the service is launched, this is simply me seeing if my reply queue functions are working and having a little fun with the community whilst doing it. Read below to learn how you can win a 100% @klye upvote (~$20.000 SBD) on any post you wish by participating in the testing of @Tippy.

Game & Rules

Today we'll as a community be playing "Roll High to Get The Pie" in order to place a somewhat realistic load on the @tippy service engine to see how it performs under normal conditions in it's current state. In order to play this game first we must understand what exactly the game is and learn the requirements in order to play it!

Basically we'll be using @Tippy's "roll" function to roll numbers on it's RNG (random number generator) between 1 - 100,000. Users wishing to enter or play the game must comment the post they'd like upvoted if they win and under it well the following @Tippy command:

@tippy roll 100000 _OR @tippy -d 100000

Do it correctly your comment below SHOULD look something like the screencap below:

In order to be eligible to win you must upvote this testing post..
ONLY 1 ROLL PER AN ACCOUNT! MULTIPLES WILL DISQUALIFY YOU!
Ignoring The 1 Roll Per Account May Result in Being Flagged

Assuming @tippy isn't crashed, off, bugged, waiting for the comment limiter or drunk it will reply with a roll number between 1-100000. This is your entry to the contest / giveaway and the highest number rolled by a user once this post is 24 hours old will receive a 100% upvote on the link they specified worth toughly $20 SBD reward.

Other prizes include a 50% upvote for the lowest number as well as votes of unknown value to the first users to roll numbers 350, 420, 1337, 31337. Prizes given out once this post reaches 24 hours old. First users to roll these numbers may claim the prize.

Expect Bugs! Lord Knows I Am...

If you happen to do your roll command and tippy doesn't respond in an hour feel free to try again! This is development / testing and it's without a doubt we'll likely crash the service as well as uncover unknown bugs. This is the true point of this test and in order to provide the best service possible first it must withstand rigorous testing, errors found / fixed as we get closer to launch! Thanks to everyone who is helping test! Good luck!

LEADERBOARD / THE WINNERS

_{( Contest Over! )}

HIGHEST: @steemanator rolled 99542 Voted!
LOWEST: @adamm rolled 2176 Voted!

@Tippy Status: ONLINE

_{( if it crashes I'll log the errors and restart it )}

BUGS FOUND SO FAR: 8

• Replies processing last in, first out & overwriting itself when overloaded... Will fix. Should be processing FIFO (first in, first out) and able to maintain a queue longer than 2 objects.
  

  

• Script attempts a NaN powerup when letters are introduced to the roll call.. whut (Thanks @gikitiki)

• Comment Queue during start up sync prone to crashing, needs error handling polished and timing fixed

• Investigate call on block 13187652 to see what crashed it

• Unf*ck the comment queue while syncing.. Currently fires one and warns of others..

• Fix timestamp display and toggle functions

• Look into resync crashes that erase blockdata file content

• dice / roll function needs some lovin'

---