Warrior General Games

yello is boltz

Originally posted by "Bort"
second, what if anything goes into the chance of a defender avoiding running into a an engaged block? Vision? Agility? Or is it just the pathing routine to run into it and be delayed regardless of dot quality or distance etc? Very frustrating aspect of the game, would be nice to know how it works to avoid it..

LOL why the heck did I not follow up with "Is the check easier if the blocker is engaged in a block?"

Oy Vey, I bet it isn't. That would be a good place to start a fix - two people being easier to see and a non grabby moving blocker easier to get around.

Originally posted by yello1
The TE Here blockes not one, not two, but THREE defenders.

I know he is throwing a screen here. Defenders are stacked waiting for it.

But the screwed up blocking lets the HB go lol on his way.

So sick of it.

This dot just got flexed over it.

Was going to need flex.

Not now.

FIX THE BLOCKING BORT.

ONE BLOCKER ONE DEFENDER BLOCKED THATS IT FFS!

http://goallineblitz.com/game/replay.pl?game_id=2070946&pbp_id=5465419

Former Dot
http://goallineblitz.com/game/player.pl?player_id=1802194

TE does not block all 3 dots... Only blocks the CB... RT blocks the DE and the SS is jammed trying to get around those blocks.

So where is the problem yello?

Originally posted by beenlurken
TE does not block all 3 dots... Only blocks the CB... RT blocks the DE and the SS is jammed trying to get around those blocks.

So where is the problem yello?


this is how i see it too fwiw

Originally posted by yello1
Okay followed up with Bort and got this.

Originally posted by "Bort"


Originally posted by "yello1"


You stated earlier that Blockers can not block more than one player and that hang ups are due to the defender trying to get around the blocker/blocked duo. Two prong question,

first is there any plan to review that pathing, because I have seen dots (FS in the recalled instance) run several dot widths straight into an already engaged blocker and be stuck for several ticks. Is that working as intended or?

second, what if anything goes into the chance of a defender avoiding running into a an engaged block? Vision? Agility? Or is it just the pathing routine to run into it and be delayed regardless of dot quality or distance etc? Very frustrating aspect of the game, would be nice to know how it works to avoid it..

The pathfinding range/strength variables could probably use some adjustments here and there, but overall it tends to work pretty well IMO.

The largest factors are vision and agility vs speed. Vision determines if the defender even sees a blocker to try and avoid him. And agility will allow him to change direction. Super speedy guys will probably have more difficulty once they are up to speed, because it's harder to change direction.
.

Originally posted by "Bort"


Originally posted by "yello1"


Thanks, one more follow up. The collision circle is not the size of the dot is it? I can run past two people dancing pretty easily, they don't take up the nearly two yards a dot on the field is. Would it be possible to reduce that collision size even more given they are entangled with each other? It just seems to happen alot, far more than it ought. Not the best example but I cant see how the TE blocking the one defender here could really have gotten in the way of the other two or three defenders so much that they do not make a play.
http://goallineblitz.com/game/replay.pl?game_id=2070946&pbp_id=5465419


Well that replay in particular just seems to be unlucky untimely placement and a bit of getting tangled up on each other combined with the receiver getting a bit of a cut fake going on, but I know what you're talking about in general.

I think the "fix," if there is one, would be to actually increase the collision radius so they take a little wider path around the blocker and don't get tangled up. Maybe Catch can add that to the list of stuff to take a look at this offseason, if possible.

So that takes care of the question. It would appear Bort concurs there is something that could be tweaked and will put it on a list of things to consider tweaking.

I'll take that.

in that case I'm going to lock this thread, as it's just getting out of hand. Bort is aware of any issue present