Sound4 wrote:Christen57 wrote:Sound4 wrote:This proves that when you ask for a replay you don't look at it but that is besides the point. They never said anything about connection so that already shutdowns that argument. They didn't say anything about reading either. Also about N3SH you were the one asking the replay for it. Look at the "what does this mean thread" it is is on the first page.
Would've been better you for to link me to it instead of sending me on a scavenger hunt for it but I think I found what you're referring to.Anyways, maybe your opponent was lagging without realizing it. That can happen. Sometimes lag can be easy or hard to detect/notice. Either way, the first thing that happened after you activated your ritual spell from hand was the opponent declaring their response, so why didn't you just let your opponent respond there?
In the other replay, you tried to activate Nachster's effect to special summon Cyber Dragon from your grave but your opponent was saying "on eff" and "hold on" and instead of holding on you still kept going. You need to hold on when your opponent says to hold on.
At 4:07 I explained and said my nachster 2nd eff and seeing on how he was fine with my nachster 1st eff there is a good chance he was already aware of the 2nd eff as well especially when he didn't say anything about not knowing ng its 2nd eff.
What do you mean by "a good chance"? Unless your opponent explicitly says they having no hand traps or anything else they can or want to respond with, you can't assume they would know and be okay with Nachster's second effect. You made an incorrect assumption.
I explained its 2nd eff and said "hold on" at 4:24. I was already beginning to resolve as well. "on eff" means nothing as well Furthermore, I had already begun resolving.
Your opponent was the one saying "hold on," not you, and they said "on eff" and "on summon" after you said "I also get to summon 2100 machine monster from gy," meaning they wanted to respond to Nachster's field effect which you should have let them do instead of wasting N3sh's time.