Warrior General Games

Originally posted by peeti


Back to the topic...i also had a CB playing LB today in a few plays. I will look at it tomorrow but it has prolly to do with the stuff as i changed ST DC yesterday to put faster guys in the middle

I have been having my SS playing ROLB on a pretty consistent basis as a sub, I am hoping that this fix may end solving that problem as well. I am using a very basic ST DC though with just K, P and KR/PR with this problem still happening. crossing fingers

Originally posted by Corndog
So, it's somehow tied to the punt depth chart?

Gotta love how I posted the same info and even told support 2 days earlier. Then Time Trial says "Hey it's only on punts". And within 2 hours your posting that Bort will fix ASAP. But, I wasn't a tester so everyone just go ahead and ignore my post.

At least it's going to be fixed.

Originally posted by bdnannac
Gotta love how I posted the same info and even told support 2 days earlier. Then Time Trial says "Hey it's only on punts". And within 2 hours your posting that Bort will fix ASAP. But, I wasn't a tester so everyone just go ahead and ignore my post.

At least it's going to be fixed.

welcome to glb.

Originally posted by bdnannac
Gotta love how I posted the same info and even told support 2 days earlier. Then Time Trial says "Hey it's only on punts". And within 2 hours your posting that Bort will fix ASAP. But, I wasn't a tester so everyone just go ahead and ignore my post.

At least it's going to be fixed.

Support isn't the place for this. Support stuff goes to Admins who don't have access to the code.

I posted a bug about the problem, people posted possible solutions. I tested each solution and posted about the results to confirm the problem. I listened to what other people proposed as a solution, was able to demonstrate the issue existed, demonstrate what wasn't the problem (three+ people at the depth chart position), demonstrate what the exact problem was, which led CornBlade to the problem.

I don't have any special pull. If it helps, I have like 10 outstanding bug reports that have no solutions.

I'm not pissed at anybody. Just seemed to be weird timing I guess. I'm sure you saw we were saying it was on punts and Corn just happened to see your post. It happens. Just glad it's got a fix.

Originally posted by bdnannac
Gotta love how I posted the same info and even told support 2 days earlier. Then Time Trial says "Hey it's only on punts". And within 2 hours your posting that Bort will fix ASAP. But, I wasn't a tester so everyone just go ahead and ignore my post.

At least it's going to be fixed.

Its generally easier to fix bugs when you have more info rather than less.

Originally posted by Corndog
Its generally easier to fix bugs when you have more info rather than less.

Now go fix the hard ones.

http://glb2.warriorgeneral.com/game/forum/forum/13336

Ctrl-F "Time Trial"

Originally posted by Time Trial
Now go fix the hard ones.

http://glb2.warriorgeneral.com/game/forum/forum/13336

Ctrl-F "Time Trial"



Didn't get much. The out of bounds one is hard to tell by watching and nearly impossible to reliably recreate. The other is just announcing that you can't respec while on a team.

Originally posted by Corndog
Didn't get much. The out of bounds one is hard to tell by watching and nearly impossible to reliably recreate. The other is just announcing that you can't respec while on a team.

What about the one where when you read alerts in GLB2 (from GLB1) they show up with GLB2 links?

It looks like about 3 of them are resolved, but still listed in the bugs forum.

...now do Niboris' bugs.

Originally posted by Corndog
Didn't get much. The out of bounds one is hard to tell by watching and nearly impossible to reliably recreate. The other is just announcing that you can't respec while on a team.

Also the description seems to indicate that he landed out of bounds, but I can't see the play at work, so I can't remember what it was about the description that made me think that.

Originally posted by Time Trial
Also the description seems to indicate that he landed out of bounds, but I can't see the play at work, so I can't remember what it was about the description that made me think that.

That's just how the description of things strings together

QB Bruise QB threw a pass to WR4 Bruise Slot WR, who made a jumping catch and went out of bounds for a 23 yard gain and a first down.

Compare to
QB Uncatchable Passes threw a pass to HB Larry Tonka, who made a jumping catch for a 2 yard gain. Tackled by CB2 Bruise CB3.
QB Bruise QB pitched to HB Bruise HB/Returner, who went out of bounds for a 11 yard gain and a first down.

If you're tackled, you get "for a X yard gain. Tackled by Player".
If you end the play by going out of bounds, you get "went out of bounds for a X yard gain."

From that play, it does *look* like he went out of bounds in the air. But there's no way to tell from what we get if he landed in bounds and stepped out or what.

Originally posted by Time Trial
...now do Niboris' bugs.

I can't even get developers where I actually work to work on my bugs.

Originally posted by crazy454
Whatever it is, I believe something should be done about it.

+1

So I didn't change any depth charts since the fix for this. Now it's pulling my BTE to play TE. I already have 2 TE's listed there and not the BTE. Do I need to redo and save my depth charts again since we had the fix?

Originally posted by bdnannac
So I didn't change any depth charts since the fix for this. Now it's pulling my BTE to play TE. I already have 2 TE's listed there and not the BTE. Do I need to redo and save my depth charts again since we had the fix?

Probably