justinmccombs/html5tetris

Automatically exported from code.google.com/p/html5tetris

html5tetris's Issues

End of Game at Level 15 Needs to be More Obvious

Players who beat the game think feel that the game has crashed on them when 
they beat the game.

Some sort of natural dialogue should pop up for them, to congratulate/inform 
them that they have beaten the game.

Original issue reported on code.google.com by [email protected] on 11 Nov 2011 at 3:25

Issue top out

What steps will reproduce the problem?
1. Stacking too the top
2.
3.

What is the expected output? What do you see instead?
to lose whne crossing top line. Can vcross top line.

What version of the product are you using? On what operating system?
? windows XP

Please provide any additional information below.
Game does not top out

Original issue reported on code.google.com by [email protected] on 18 Nov 2011 at 7:03

Change T-spin Mini recognition

A T-Spin should be mini if:

1. Already a T-spin by 3-point method
2. Last movement was a rotation
3. one of the points next to the tip of the T is unoccupied

Original issue reported on code.google.com by [email protected] on 13 Nov 2011 at 8:04

High Score Issue

What steps will reproduce the problem?
1. Getting a high score - approximately 650,000+ The Game ends
2. Game ends with only half the blocks on the screen filled
3. Game over even though there is still game left to be played

What is the expected output? What do you see instead?
I expect to keep playing and to get a higher score but instead I see a game 
over screen.

What version of the product are you using? On what operating system?
Most recent version, used on both Mozilla Firefox and Google Chrome, same issue.

Please provide any additional information below.
The high-score of the day always is around the 600,000-700,000 range and I 
believe this is the issue. Thanks

Original issue reported on code.google.com by [email protected] on 24 May 2014 at 2:20

Configurable Controls and auto-repeat

Users all want to be able to customize their controls as well as their 
auto-repeat.

Original issue reported on code.google.com by [email protected] on 13 Nov 2011 at 7:48

Crazy Rendering and/or Block Placement Error in Chrome for OSX

When swapping back into the game's tab, the entire arena was filled with red 
and purple blocks, and the grey preview blocks were pasted on the bottom.

From Mikey's Facebook comment:
""" yeah, chrome 16.0.912.32 beta, running osx 64 bit (10.6), darwin kernel 
10.8.0 ... and i dunno i was switching around tabs really quickly and when i 
switched back into that tab it was like that ... """

Probably has something to do with webkit's renderer on OSX not playing nicely 
with the game's Lazy Rendering Scheme.

Original issue reported on code.google.com by [email protected] on 11 Nov 2011 at 3:15

Swap Piece and Lock Down time

The slide/lock time and/or number of moves seems to get all screwy if you dick 
around with a piece while sliding it, then swap it, the lock down counters seem 
to not be reset appropriately.

Original issue reported on code.google.com by [email protected] on 11 Nov 2011 at 3:32

Small spelling error

Spelling error in "about TwitchTetris" section. Second paragraph, second 
sentence;

"This ispossible" no space between is and possible.

Original issue reported on code.google.com by [email protected] on 10 Nov 2011 at 10:50

High Scores are easy to spoof

True anti-spoof protection is nearly impossible. The next best method is to 
keep the score of the game in real-time on the server side. This means that the 
entire logical portion of the game needs to be re-written in python, and should 
be updated in real time along with the player's game, to verify that the way 
they got to that score was actually possible. Otherwise, they can just inject 
whatever score they want into the JS, and return the score.

That means that the only remaining exploit would be a tetris-playing bot. I'm 
cool with that, so long as they release the source for me to see :)

The exploiter said something about SOP, which has nothing to do with this issue.

Original issue reported on code.google.com by [email protected] on 31 May 2012 at 1:05

Make ghost piece more subtle

Reddit users were complaining about the ghost piece being too distracting.

The color of the ghost should be darkened, and tested on monitors of different 
color temp.

Original issue reported on code.google.com by [email protected] on 13 Nov 2011 at 7:46