Yes, I was just poking fun at you a bit =) I really think you don't, though.
Twice in a row: ~4-8 seconds after the ghost descends before it pops up again (usually like 6 seconds)
Ghost appears on the other side once: ~15-18 seconds (6 seconds after for the ghost to appear on the other side, stays for 4 seconds and descends, and another 6 seconds before it appears back on our side).
Twice brings it to ~30 seconds. It made me a little sad, but it's somewhat rare. I'm just going to assume 50% chance on each side.
Then couldn't we say wall CGs are particularly buffed in that regard on Pictochat?
Yes, extremely buffed.
Are you really going to claim that Marth will be saved MOST of the time?
You said ~15-18 seconds between ghosts. If the ghost decides to appear on the other side, that's already ~30-36 seconds with no ghost on the side where the edgeguard is taking place. If it decides to appear twice on the other side (not unlikely at all), that's ~45-54 seconds with no ghost. Marth can't stall for THAT long -_-
Yes, Marth should be saved above 50%, which is most. You can predict when a ghost will come, and you know the two places the ghost can appear.
Sorry if I confused you a bit. It takes more consecutive ghosts to take that long. Out of 30 minutes, I've only seen it above 40 seconds once or twice. Test it out for yourself if I'm starting to speak mumbo jumbo lol.
Sure, characters like Peach, Yoshi, and Marth are more likely to be saved than Captain Falcon or Ganondorf, but they still cannot achieve 30+ seconds of stall time. I'm going to start questioning your understanding of the stage if you think Marth can stall long enough to get a "very good chance" of being saved.
True, but that's if you factor in their recovery by itself. You need to consider them getting launched, and the whole recovery process. You also have to see if the camera let us see if a ghost appeared yet, or if a ghost helps during the recovery.
If we don't see a ghost on that side during the whole edgeguard process, you would think the player would have some hope it would appear sooner or later when things aren't looking so well.
This is in response to my example of two characters being sent to opposite sides and the platform saving one of them.
How does this address my point at all? Why does it matter when or how often the ghost comes up in this scenario? What matters is that the ghost COULD save one player, but not the other, thus heavily influencing the outcome of a match.
Just giving some info to the probabilities that a ghost will appear. There is actually a high chance of one character being saved and the other dying. Small percent chance both could survive if they can stall for a good 5+ seconds.
Because we know the frequency, we know that we could expect one player to survive. You need all the info you can get.
If the issue is that it COULD save one player, what's the point of arguing about randomness? If it wasn't random, it would be similar to SV saving one player or the other. Or Lylat, where it's tilted one way and not the other, and one guy dies, even though we know when it tilts based on which scene it is. On PS1, you get sent off to the left side when the stage is about to tell you what transformation it's about to enter. If you get mountains or windmill, that helps you recover easily, but you have trouble if it transforms to fire or forest.
We know approximately when a ghost will appear, just not which side, as far as we know. Many things could save players, but the magnitude of the event isn't really too drastic to affect gameplay enough to be bannable material. The best you can come up with are very situational events that are rare in high level play? That's the best I can come up with for SV/PS1/Lylat also.
First of all, you are attacking the WRONG part of my example. Who cares what the characters are? What if Diddy manages to side-b gimp Snake so he's falling off the stage with no C4 and no Cypher? Why am I even bringing up another example? It doesn't matter. We have a matchup taking place on this stage. Forget about which player or character picked it. We have a stock that was supposed to be taken, and we see it given back because of the stage's randomness. And you're just going to dismiss it by saying CHARACTER FLAW?
50% is not random enough to feel like it should be 100%. If it doesn't come on that side, you get your guaranteed kill. If it does, you get a guaranteed punish. Pretty simple.
Your examples are all pretty situational and bad.
You're missing my point. You chose sheik in your example, who would have problems gimping throughout the entire edgeguard process if the ghost comes up even once. The ghost comes often enough to make gimping for Sheik a less than optimal option. If you don't want me to think about character's options, then don't bring them up at all.
Then, if you can say "oh well, poor Sheik can't guarantee a kill", why can I not say "oh well, poor x character can't abuse walls like Pikachu or Ike can"?
You can. Is there something you're trying to get at?
Why can't I say "nice choice for Ike to pick Pictochat" when you can say "nice choice for the player playing against Sheik to pick Yoshi's"?
Pictochat is a good stage for Ike. Too bad it's not legal.
Counterpicking to abuse randomness acceptable in one situation, but not in the other? Hypocrisy imo.
Can you explain how this "randomness" is being abused? The timings of the ghosts aren't very random, but you just don't know if it appears on the left or right.
Every 6 seconds after one ghost descends, a ghost appears on the left or right side on YI. You can confine the timing to a few seconds. If the ghosts were player triggered or something, the sheik would hate that even more.
I'm going to have to watch YI matches a few more times, because it was surprisingly rare for ghosts to appear on one side more than twice in a row. It should be easier to assume that it's not going to appear on the same side as often.
EDIT: Yeah, seems to be random which side it is after looking at it more. Lots of times they were on the same side more than once, and sometimes they went back and forth (aka random)
Every 13 or so seconds on Picto, what happens? There is much more wrong with Picto anyways. You should expect walls all over that stage, but positioning, etc go right out the window. I want to focus on YI for now so I deleted a lot of Picto stuff.
There are situations where it doesn't make a difference. I acknowledge this. But there are situations where it DOES, and these situations are NOT that rare.
Those helpless situations are rare. If you have a 50/50 prediction of a ghost, that's not bad at all.