Profile of Rosbone

I just rewatched the clip and at no point does the fuel point start flashing red and when they untick fog of war you can see its already capped. Also his cutoff wasn't taken, the one youre referring to is south base cutoff. Rewatch the video, his cutoff is in vision almost the whole time and no enemy squad touches it that I see.

You will probably only see the territory flash IN GAME. Not spectating a replay. So it does not flash in the video.

The point where Seeking is making bags touches the south fuel and south cutoff.

The south cutoff was already taken before the fuel is taken. So Seeking would have known at 1:25 game time that there is a squad to his south west (cutoff) and to his south (fuel).

The southwest squad can either go to the mid VP or the point Seeking is on. A smart player would converge their two squads at the point Seeking is on (to out number the enemy). Because they would also see a flashing territory and know Seeking is there.

If I was Seeking I would have pulled back probably earlier than he did. But he may have been looking at something else or was waiting to see if the mid VP area started flashing.

The problem is WE dont have the replays, so we have these spectate games where the operator is flashing the FOW on/off. You have no context as to what happened before that may have been a clue to Seeking. And how can we expect Seeking to remember every detail of games from a week or two ago??? I dont remember 15 minutes ago

sry but what unit do you mean? Only the pathfinders are involved in this situation. The sturms havent seen the rear echelons at all

Looking at AEs video at game time 1:25 he pauses.

At this point Seeking may have seen the territory switch from flashing RED to solid white. So you know something just capped/is capping that point and is probably moving towards you.

In my test below, the territory flashed red then turns solid white when captured.



Just a thought. I have about 4 hours of sleep so take it with a grain of salt

EDIT:
I use this mechanic all the time in 4v4, but dont pay attention to the details of how it works. I just see the colors and know something is there.

EDIT #2:
The cutoff was already taken and Seeking would have saw that also. So he would really know someone is headed his way soon.

Unfortunately seems people are using your clip as "proof" of desync.

It is just a reference. I agree and state that it is not perfectly synced. In fact you can almost never get them perfectly synced.

I'm sure you know that by using "," and "." on youtube you can move frame by frame.

No I did not know this. Thanks. I never use ANY google product if I dont have too. They are the devil and no one should ever use any google stuff.

Tournament directors asked me to make a google sheet for them and I said "You make the account, because I will not." And I should have just said no. My mistake. Click on the account and it has a whole history of everything I ever searched. Fvck Google people. No Android phones, No Google, No YouTube. Pull out before its too late.

Go to:
https://youtu.be/4d0utxORja0?t=87

This video was broken when I tried to watch it.... f'ing Google.

Since you are from the same country, do you think it's possible to react that fast?

The better question is how much lag does the replay have. For instance if that is Nicko and he is in Russia how far behind was he from Seeking.

I always talk about playing with Ishtari who is in Sweden. Ish yells out "Rosbone your grens!". I hear this thru Discord and say back "What they are safe?" Then "Oh no they are gonna get rekt."

Ishtari is playing at least 2 seconds ahead of me in real time. I am playing in the past.

We need some tests done where two people play and record the match thru OBS from different parts of the world. But the clocks may still be off so the people need to be in Discord chatting at the same time for a reference point.

These two frames are a little closer in time. The FOW is still moving.


- The units seem to be not moving.
- The G43 icon is missing in both as it transfers.
- The FOW is moved.

It is important to note that the FOW may NOT be calculated every frame, but once every 100mS or something. Needs reviewed. So you may see FOW differences just due to calc sequences not being synced.