Poll
Question:
Puhl
Option 1: Why do you keep posting crap about Watch Games, who gives a shit?
votes: 2
Option 2: I'm midly interested, keep posting.
votes: 3
Option 3: I like to see the Glitches
votes: 1
Option 4: Fuck off attention whore
votes: 1
Option 5: WUMPST
votes: 0
Option 6: yes or no
votes: 0
Option 7: I don't believe these glitches actually happened
votes: 0
If you pause the game at just the right moment when the batter makes contact you get a blank screen (presumably when the screen switches). Probably happens in lots of screen switches so maybe it's not that interesting.
How much more black could it be? And the answer is none. None more black.
its like a black mirror
Here's another, right after screen switch in which the batter is missing
Discovered a watch glitch, think I saw this once before but never documented.
Men on 1st and 2nd, sharp ground to LF, throws to 3rd, no one covers 1st guy scores, 2nd guy rounds third, throw goes home, he starts running back, but batter gets to third so he's forced to come home. Catcher runs him down and tags him.
Up to now all normal (in the RBI watch world), now the weird part is the batter decides to head for home also and C, who just tagged one guy out about half way between home and 3rd just continues on to 3rd and tags out the next runner, but I have no idea why the CPU logic sent that guy home.
Hope this all makes sense.
Quote from: Gerlost on 11/21/05, 04:15:19 PM
How much more black could it be? And the answer is none. None more black.
Actually, it could be more black. There's one color in the NES "palette" (0x0D for the nerds among us) that is sometimes referred to as "blacker than black." From the NES Tech FAQ (http://nesdev.parodius.com/NESTechFAQ.htm):
"Palette value $0D is the blackest value of them all, but it is what's known as "blacker than black". In other words, some video monitors or television screens might not accept that colour as a valid NTSC colour value. It has been said that it might even cause some video screens to interpret it as another blanking signal, and mess up their synching rates."
So there you go.
i feel like i just got nerded on.
i could also say that you guys are racists.
Here's another glitch I've never seen before
Just played a watch game against Mclane's team, he used up all his PHs in the 8th inning(CPU used 1 in the 4th, and 3 in the 8th) but somehow in the 9th Galarraga was available again (PH #3), so he got 5 PH ABs in the game. I'd never seen that before.
Quote from: ultimate7 on 11/22/05, 02:01:20 PM
Discovered a watch glitch, think I saw this once before but never documented.
Men on 1st and 2nd, sharp ground to LF, throws to 3rd, no one covers 1st guy scores, 2nd guy rounds third, throw goes home, he starts running back, but batter gets to third so he's forced to come home. Catcher runs him down and tags him.
Up to now all normal (in the RBI watch world), now the weird part is the batter decides to head for home also and C, who just tagged one guy out about half way between home and 3rd just continues on to 3rd and tags out the next runner, but I have no idea why the CPU logic sent that guy home.
Hope this all makes sense.
maybe the CPU runner sees that "nobody is covering home" since the catcher is not actually there?
But I don't think there is any other time when CPU sends a runner to a base just because it is uncovered. Usually they just go to the next base only if no one is yet in possesion of the ball (if it hasn't been fielded yet)