DeletedUser
Guest
If you have A noble chain of 4 coming in on the same second isn't that against the rules
Cau's I have just that.:icon_sad:
Cau's I have just that.:icon_sad:
One of the solutions that Krieg is talking about is sending a few defensive troops on that second, to try to kill one noble so you won't get nobled, then stack the village to be safe.
[ke]What you're going to want to do is to send out all your defensive troops 20 seconds before the SECOND attack hits, compensate for the lag time and have it so your defensive troops land in-between the first and last noble attack. There are FAR MORE advanced and better ways, but this is the simplest and easiest way to do it. I seriously suggest reading a guide though.[/ke]
[ke]He might only have 1 village though. I'll give you a very short and easy way to do it:
Send out 50 swords, wait 10 seconds and cancel them.
Keep doing this until you know the lag time for how long it takes the cancel button to react for your troops to start heading back.
What you're going to want to do is to send out all your defensive troops 20 seconds before the SECOND attack hits, compensate for the lag time and have it so your defensive troops land in-between the first and last noble attack. There are FAR MORE advanced and better ways, but this is the simplest and easiest way to do it. I seriously suggest reading a guide though.[/ke]
If the all 4 nobles are in the same second i can't see this working though, troops returning to there base always do so bang on the second, no MS taken into account. Therefore it would be impossible to snipe a train this way unless they were spread out over 2 different seconds in a 1 sec timescale.
OP lost his village though and decided to restart other side of world.
Your description is severely flawed.
Your lag only needs to be known to the nearest second.
When sending cancelling send ms = return ms, with that single bit of knowledge splitting is FAR easier.
ie.
Send an attack at 5:05:03:627
You cancel 2 seconds later (roughly, ms does not matter, just rounded to the nearest second = 2)
it will return at 5:05:07:627, if it said it will originally hit at :627 it will always return at :627 when cancelled.
Using this knowledge you send support over and over until the ms is right and cancel immediately every time it isn't right.
Your description is severely flawed.
Your lag only needs to be known to the nearest second.
When sending cancelling send ms = return ms, with that single bit of knowledge splitting is FAR easier.
ie.
Send an attack at 5:05:03:627
You cancel 2 seconds later (roughly, ms does not matter, just rounded to the nearest second = 2)
it will return at 5:05:07:627, if it said it will originally hit at :627 it will always return at :627 when cancelled.
Using this knowledge you send support over and over until the ms is right and cancel immediately every time it isn't right.
[ke]Dude, did I say ANYTHING about Milliseconds?[/ke]
Which was the problem.
Without knowledge that send ms = return ms splitting via send/cancel is simply not effective.
No. They return 'bang on the second' as you worded it if you send an attack, it hits its target, and returns, when cancelled it returns on the same ms it would have hit the target.
[ke]If you don't know about MS, then MS aren't going to affect you. What you added to the conversation was what a semi-experienced player should need to know and it's knowledge that would only help a semi-experienced player. A regular noob probably isn't even going to know about MS.[/ke]
Which is why you teach it to them.....
[ke]This guy is asking how to defeat it, he's not asking for a crash course. I'm not going bombard him with a bunch of information that is completely irrelevant at the present point in time. Afterwards, sure? Right when he was asking though? It would've been a more deteriment to tell him everything.[/ke]
The knowledge you gave him would not have helped him split the train at all if he had sent the attack and had the ms wrong when it was sent. So no, you didn't give him how to defeat it, though I actually suspect you yourself didn't even know that send ms = return ms.
[ke]How can you have the MS wrong?[/ke]