User Pass
Home Sign Up Contact Log In
Forum > Discuss GLB Issues With Catch22 > NOT A BUG - CLOSED > #1 CB lined up against #WR...and #2 CB lined up against #1 WR
Page:
 
mocfam10
offline
Link
 
Originally posted by sunder B
Not a bug. It's a depth chart setting. If you want your best CB covering their #1 WR, move him to #2 on your depth chart. Problem solved.

I just don't understand the need for #1 to matchup against #1 when you can acheive the same thing by learning the depth charts and how to create the mismatches. Most people already know that #1 WR faces #2 CB and vice versa, so if everyone knows this (or can figure this out with minimal scouting), not sure why a change would need to be made.




I don't thing the game developer meant for it to go that way. I'm sure he meant for the #1 guy list on both depth charts to face off. Yes, there is a work around, but I don't think it was intended to be the sole way to get a true #1 vs #1 or #2 vs #2 matchup.
Sure, it's nothing major, but a DC or OC should have to manually make the adjustment to "correct" it by flipping the depth chart. Unless they are intentionally trying to create the mismatch. Not a huge mismatch, but not the true #1 vs #1 you see on saturdays and sundays.

Hence, why it is a programming thing. yes, with a simple solution, but not something that should have to be done. When I played in college, the #1 guy on our defense faced the #1 WR on the offense...both were listed first. In NCAA 08 or any other version, the guys listed 1st on the depth chart matched up on the same side of the field. GLB should be no different.
Last edited Jul 10, 2008 11:33:20
 
Novus
offline
Link
 
Originally posted by joemalaka
Originally posted by Novus


I beg to differ. I've seen the DCs on my teams shuffle CBs and WRs around to try to create mismatches before.


BY CHANGING THE DEPTH CHART JACKASS!

My point was that the #1 in the depth chart WR matched up against the #2 in the depth chart WR. To make mismatches you move players in the depth chart.

Maybe a suggestion should be that idiot jackasses cannot reply in the Bug forum.


And maybe a suggestion should be that if you get out-scouted by the other team, you shouldn't cry about it on the Bugs Forum.

Obviously I got the details wrong on HOW to create a mis-match, but I also don't own a team.

You do own a team. What's your excuse?
 
naraic
offline
Link
 
http://goallineblitz.com/game/forum_thread.pl?thread_id=565646

I explained several reasons why this would occur in this thread it is not necessarily a bug
 
thunderdoozer
offline
Link
 
Originally posted by sunder B
if everyone knows this (or can figure this out with minimal scouting), not sure why a change would need to be made.


The problem is the "if everyone" part. Not everyone knows this. Obviously.
 
Schaffer05
offline
Link
 
One of the teams i play on has had this similar issue, and the opposing team did not change depth charts last minute
 
Schaffer05
offline
Link
 
Originally posted by Novus
Originally posted by joemalaka

Originally posted by Novus



I beg to differ. I've seen the DCs on my teams shuffle CBs and WRs around to try to create mismatches before.


BY CHANGING THE DEPTH CHART JACKASS!

My point was that the #1 in the depth chart WR matched up against the #2 in the depth chart WR. To make mismatches you move players in the depth chart.

Maybe a suggestion should be that idiot jackasses cannot reply in the Bug forum.


And maybe a suggestion should be that if you get out-scouted by the other team, you shouldn't cry about it on the Bugs Forum.

Obviously I got the details wrong on HOW to create a mis-match, but I also don't own a team.

You do own a team. What's your excuse?


Novus, you were the one telling him he owns the team and to figure it out when he already knew what he was talking about and you didn't... Don't see where he needs an excuse, but I do see when you should think before you speak.
 
Mysterio
offline
Link
 
Originally posted by Novus
Originally posted by joemalaka

Originally posted by Novus



I beg to differ. I've seen the DCs on my teams shuffle CBs and WRs around to try to create mismatches before.


BY CHANGING THE DEPTH CHART JACKASS!

My point was that the #1 in the depth chart WR matched up against the #2 in the depth chart WR. To make mismatches you move players in the depth chart.

Maybe a suggestion should be that idiot jackasses cannot reply in the Bug forum.


And maybe a suggestion should be that if you get out-scouted by the other team, you shouldn't cry about it on the Bugs Forum.

Obviously I got the details wrong on HOW to create a mis-match, but I also don't own a team.

You do own a team. What's your excuse?


ITT Novus pretends like he knows what he's talking about like always. It has to do with which player has the better stats at that point in the game stamina setting wise. The WR and CB get shifted out all through the game which is why it's always good to have all solid CB's. At the beginning they SHOULD all line up though
 
Novus
offline
Link
 
Originally posted by Schaffer05
Novus, you were the one telling him he owns the team and to figure it out when he already knew what he was talking about and you didn't... Don't see where he needs an excuse, but I do see when you should think before you speak.


He's the one who didn't know you can intentionally create a mis-match. I knew it was possible; I just got the details wrong. But he didn't even know it at all!

PinTBC set us both straight on page 1. He pointed out that I was wrong on the detail of left-or-right, but that I was correct that the other team could've scouted him and created the mis-match intentionally.

I don't own a team. It shouldn't be a huge shock that I'm going to get something wrong now and then.

He DOES own a team. He should have already known mis-matches could be intentionally created -- AND INSTEAD HE THOUGHT IT WAS A BUG.

My basic premise was still correct. My error was in the details.
 
Adderfist
offline
Link
 
Originally posted by Novus
Originally posted by Schaffer05

Novus, you were the one telling him he owns the team and to figure it out when he already knew what he was talking about and you didn't... Don't see where he needs an excuse, but I do see when you should think before you speak.


He's the one who didn't know you can intentionally create a mis-match. I knew it was possible; I just got the details wrong. But he didn't even know it at all!

PinTBC set us both straight on page 1. He pointed out that I was wrong on the detail of left-or-right, but that I was correct that the other team could've scouted him and created the mis-match intentionally.

I don't own a team. It shouldn't be a huge shock that I'm going to get something wrong now and then.

He DOES own a team. He should have already known mis-matches could be intentionally created -- AND INSTEAD HE THOUGHT IT WAS A BUG.

My basic premise was still correct. My error was in the details.


If you don't know, then don't give advice. It's better to give no direction, than bad direction.
 
thunderdoozer
offline
Link
 
Actually, Novus, you just misunderstood the OP and started insulting him for not knowing something that you didn't even know either.

Of course he knows he can re-order the depth chart. He was asking if the matchup system was bugged. Whether is it or not, most of us have learned to adjust to it.
 
kb2120
offline
Link
 
In 2 WR sets, it is always #1 WR vs. #2 CB and vice versa.
In 3+ WR sets, it is #1 WR vs. #1 CB, #2 WR vs. #2 CB, etc.

Is this a bug ? That is open for interpretation, but I consider a bug something that doesn't always happen the same way.
 
Kyndig
offline
Link
 
Working as intended.
 
kaygdanimal
offline
Link
 
There is a bug but people are not willing to accept that because this is their favorite little game in the whole world.

If I list a CB as #1 in my depth chart, he should stay on the right side of the field. By "right side", I am referring to when you are looking at the screen with the offense facing north and the defense facing south.

We get burned constantly on the right side of the field ... but alas it's never when our #1 CB is on the right side, it's always when he's on the left side for whatever reason there may be. I've specifically listed him at #1 for a freaking reason. I want him shutting down the RIGHT SIDE of the field and instead, this last game we get burned because the engine decided to move him to the LEFT SIDE and put our #3 on the RIGHT, resulting in two touchdowns that never would have happened if the #1 CB was on the RIGHT side of the field like I had freaking DICTATED in the DEPTH CHART.

I'm sorry guys, but this shit has been bugging me like hell and it's time that us PAYING customers actually get this shit fixed. I understand that this is BETA but it's been going on for so long and still nothing has been done. I'm just sick and tired of getting burned by our whoever lines up on the RIGHT side whenever the guy I listed as our #1 isn't where I listed him to be at.

Edit: To clarify even more, when you see that a QB completed a pass to the RIGHT side, that is the side I am clarifying. The RIGHT side is usually where you want your #1 CB to be covering as most teams pass to the right side more often.
Last edited Jul 11, 2008 07:22:50
 
joemalaka
offline
Link
 
Originally posted by kb2120
In 2 WR sets, it is always #1 WR vs. #2 CB and vice versa.
In 3+ WR sets, it is #1 WR vs. #1 CB, #2 WR vs. #2 CB, etc.

Is this a bug ? That is open for interpretation, but I consider a bug something that doesn't always happen the same way.


Wrong. Look at my play. 3 WR set. #2 CB lined up against #1 WR.

http://goallineblitz.com/game/replay.pl?pbp_id=10482006
 
joemalaka
offline
Link
 
Originally posted by Kyndig
Working as intended.


I always love this answer. How do you know this?
 
Page:
 


You are not logged in. Please log in if you want to post a reply.