|
|
Post by OrochiGeese on Nov 21, 2018 7:19:04 GMT
I christen this spot the "STOveTopStuffing"
Okite Yaburi STO into Ralph's taunt and then his bearhug into the other taunt. Beautiful :)
|
|
|
|
Post by OrochiGeese on Nov 21, 2018 9:05:37 GMT
The "Grey Gore" of El fantasma pálido ... ouch. |
|
|
|
Post by Dawnbr3ak3r on Nov 22, 2018 9:32:22 GMT
"Bullet Hell" doesn't always end well:
|
|
|
|
Post by DM_PSX on Nov 23, 2018 0:50:57 GMT
I also had the Geese situation happen. Two guys tagged in at the exact same moment, so they stood on the apron until I quit out ten minutes (game time) later.  |
|
|
|
Post by Dawnbr3ak3r on Nov 23, 2018 4:22:34 GMT
I think it's safe to say that maybe we should collectively assign slightly different Cooperation stats to our edits as a potential workaround.
|
|
|
|
Post by OrochiGeese on Nov 23, 2018 7:23:24 GMT
So do you think this is an issue of a specific cooperation number being used or an issue where two opponents share the same cooperation number?
I got a kick out of DM referring to it as a "Geese situation" 😁
|
|
|
|
Post by Dawnbr3ak3r on Nov 23, 2018 8:10:32 GMT
So do you think this is an issue of a specific cooperation number being used or an issue where two opponents share the same cooperation number? I got a kick out of DM referring to it as a "Geese situation" 😁 I'm wondering if possibly lowering Cooperation would be a manageable workaround until/if the bug is addressed. |
|
|
|
Post by Timberwolf on Nov 23, 2018 15:46:43 GMT
I've never had a "Geese Situation" even though a lot of my teams have the same numbers. My regular teams may be like 100%. New teams just starting out may be lower. Rivals forced to work together (think AJ Styles and Daniel Bryan) will be a lot lower.
When I saw Geese's moment, I thought that may have been a fluke. But when DM posted the same thing, maybe it is indeed a bug. Has someone reported it to Spike? This could be a game breaking bug. One could be simming a canon match in a live stream and this happens. We don't want that.
|
|
|
|
Post by Timberwolf on Nov 23, 2018 15:50:01 GMT
The "Grey Gore" of El fantasma pálido ... ouch. Safe to say his knees are destroyed. He won't walk again :lol: |
|
|
|
Post by OrochiGeese on Nov 23, 2018 22:30:35 GMT
So do you think this is an issue of a specific cooperation number being used or an issue where two opponents share the same cooperation number? I got a kick out of DM referring to it as a "Geese situation" 😁 I'm wondering if possibly lowering Cooperation would be a manageable workaround until/if the bug is addressed. Are you saying we should reduce the % that edits tag out? That would be Touchwork then, right? I'm not totally sure how Cooperation would come into play here based on my understanding of it but various tidbits of FPW knowledge seem to leave my brain every day so I'm probably missing something obvious 😁 Safe to say his knees are destroyed. He won't walk again :lol: Yeah, you know I didn't even notice the impact on the knees LOL. For some reason I always JUST focus on impact to the back of the head and neck for that particular move. But those knees land right on the mat so you gotta figure a CRITICAL! means a rough time for them. Luckily it was non-canon or else Tsaoring Chou would need to change his "Soaring Spirit" nickname for a bit 😞 |
|
|
|
Post by Dawnbr3ak3r on Nov 23, 2018 22:43:18 GMT
Are you saying we should reduce the % that edits tag out? That would be Touchwork then, right? I'm not totally sure how Cooperation would come into play here based on my understanding of it but various tidbits of FPW knowledge seem to leave my brain every day so I'm probably missing something obvious 😁 Cooperation dictates when/if an edit tags in/out. I'm saying we could potentially make a small adjustment to their numbers to see if it makes any difference. On the other hand: The bug is so rare that it may not be worth the effort. |
|
|
|
Post by OrochiGeese on Nov 23, 2018 23:31:57 GMT
Are you saying we should reduce the % that edits tag out? That would be Touchwork then, right? I'm not totally sure how Cooperation would come into play here based on my understanding of it but various tidbits of FPW knowledge seem to leave my brain every day so I'm probably missing something obvious 😁 Cooperation dictates when/if an edit tags in/out. I'm saying we could potentially make a small adjustment to their numbers to see if it makes any difference. On the other hand: The bug is so rare that it may not be worth the effort. I could have sworn that behavior was governed by the Touchwork category. Like the higher the Touchwork setting, the less damage an edit will tolerate before tagging out. What does Touchwork do, then? & tag u And yeah, we should compare the logic %'s (perhaps for both categories) of the edits who have frozen up. It may be entirely a game thing (if the timing of the two tags are exactly the same) but perhaps logic settings may be interacting with it. |
|
|
|
Post by DM_PSX on Nov 23, 2018 23:36:03 GMT
I had the same bug pop up directly after during a timed battle royal, ore than once. I have a guy wearing a hulk mask who throws people around like Hulk does Loki in Avengers. There were 3 people left. So he tosses someone out (not causing an elimination) and then criticals them on the outside with a triple powerbomb. So now the woman in ring stood there, and the Hulk guy on the outside just stood there for 6 minutes game time. I think this has to do with the wrestlers not having a valid target to act on. All the AI is based on making decisions based on the situation of their current target. So tagging out at the EXACT same time caused them both not to have a valid target to act upon, and no events could occur that would cause them to acquire a new target. If the logic updater code sees no valid target, it probably just returns from the function. There should be a sanity check to make sure that it looks to acquire a new target after a certain time has passed. If no notice, the referee also seems to have no target. The people who were being tagged in had the same touchwork value, not the guys who tagged out. It was just pure coincidence. Here is the battle royale in question. The second time caused a 6 minute face off.   I will report this. |
|
|
|
Post by Dawnbr3ak3r on Nov 23, 2018 23:44:40 GMT
Yeah, this same bug was in the game prior to 2.0.Whatever, but got fixed at some point.
And, you're right, Geese - I always get these two settings confused. So yeah, maybe altering the Touchwork setting would possibly alleviate the issue, but maybe not. /shrug
|
|
|
|
Post by OrochiGeese on Nov 24, 2018 0:10:18 GMT
DM, thanks for reporting it 😎 I think your explanation makes a ton of sense. Interesting that the referee also loses all ability to focus. Spike needs to know about this. It's been affecting us more recently. It would really suck if it ruined a particularly great match, especially a streamed canon one like Timberwolf said. Funny coincidence that the two edits DID have the same touchwork value but I think it's just that, a coincidence. I don't think the two (or four) edits in my match freeze from a few weeks ago had the same values. |
|
