Announcement

Collapse
No announcement yet.

Appeal Paladen vs Marksmin TWLJ game 1

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Appeal Paladen vs Marksmin TWLJ game 1

    No assis or other caps could do subs for Paladen. I alone seemed to be the only person on squad able to do them, I was in and died multiple times trying to do subs typing wildly and pm players instead of matchbot because I was so frantic. Whole squad was yelling at me as I play because the assis/ caps tried and could not do it. It is not right that only 1 player who is in the game playing top level TWL competitive play has to do this commanding alone. We have caps and assis for a reason. Hate doing this but it was a mess. We had multiple lagouts too which made it even more frantic trying to attempt them. Wound up just quitting after I could not even get my cursor onto matchbot. Please allow at least 3 to do subs.
    TWDT-J CHAMPION POWER 2018
    TWDT-B CHAMPION POWER 2018
    TWDT TRIPLE CROWN MEMBER POWER 2018
    TSL TRIPLE CROWN FINALIST 2018
    TSLD CHAMPION 2018
    TSLB CHAMPION 2018

  • #2
    Yes, first two set of games had a lot of issues and this was match one of them for sure. We will look into the appeal and will post our verdict on Monday.

    Comment


    • #3
      I support this appeal.
      1:waven> u challenge
      1:waven> if i challenge it looks too scary

      Originally posted by MHz
      Hope you contract ebola from your, no doubt cheap, Easter Egg, you fucking shit-jav, pug-faced cunt.

      Comment


      • #4
        In the thunder vs marksmin appeal Turban said the staff was unlikely to grant an appeal because the game was lopsided. This match was also very lopsided, so I expect to consistency with the way the staff responds to appeals.

        Comment


        • #5
          all appeals will be treated with fairness, rest assured.

          Comment


          • #6
            It was lopsided because the game was 5 vs 4 from the very start verses you all due to destructs constant and immediate lagouts. The bots were not properly set up for us then to do subs to deal with this issue in a timely and effective manner. This was a PREGAME BOT GLITCH BEFORE the game even started. We had no clue this was an issue until the game was already going and then we are down a guy. The settings were a huge issue for us and without a doubt caused game dynamic interruptions for our entire line that affected the score.

            This should not even be about the score at all honestly. It was a PREGAME setup issue that denied us our rightful sub commanders and kept us from being able to use them. It cost us wasted minutes and me get multiple deaths too trying to deal with it as I was yelling at them to sub and dying while doing so and then they are yelling at me they can not and I have to do it. I honestly thought the damn matchbot was broken.. and oh ya it WAS! I'm then angry as crap because I can't even set my cursor on the matchbot correctly while at the same time attempting to dodge flying bullets and bombs and getting killed. I literally had to just give up attempting the sub commands. I think yeh even then lagged out too at one stage while all this madness was going on. We wanted to sub out dumathoin too but were denied because of this issue. I was the ONLY one able to deal with this and was playing in the game at the same time! I was pounding commands only to PM people in spec or playing in the game or misspell it. Def remember like 6 attempts that were fails. I never even succeeded and just gave up and missed out using our other subs we were allotted and should have been able to use.
            It was a complete unexpected shit show and the bot issue
            definitely affected the score and game dynamics from our stand point. In a multiple lagout scenario like this immediate subs are VERY important and so is subbing out a struggling playesr. No wonder it seemed lopsided lol. 4 vs 5 and 3 vs 5 games tend to do that.
            TWDT-J CHAMPION POWER 2018
            TWDT-B CHAMPION POWER 2018
            TWDT TRIPLE CROWN MEMBER POWER 2018
            TSL TRIPLE CROWN FINALIST 2018
            TSLD CHAMPION 2018
            TSLB CHAMPION 2018

            Comment


            • #7
              our appeal regarding twlb marksmin vs thunder is based upon a "pregame setup issue" as well


              The Mind of the Father
              Riding on the subtle guiders
              Which glitter with the inflexible tracings
              Of relentless Fire

              Comment


              • #8
                You are greatly exaggerating, destruct lagged out a couple of times but most of the game was definitely not 4v5. I'm pretty sure the total 4v5 time was definitely under a single minute, maybe even 30 seconds. I'll try to say this as tactfully as possible but when you compare the two lineups I don't see how you can possibly think a lack of subs was the reason the match went down that way and that anything you did would have changed the outcome of that match.

                Comment


                • #9
                  Sounds like you want to discount a pregame bot error that denied your opponent two player subouts we wanted to use and caused me to die 4 times while I was not even able to play the game for minutes trying to deal with all this. If you feel you are so superior and it is a "default" win then just play us again and allow us the proper assis and cap spots on the bot and us to use our given subout quota we deserve. As it is now the game was tainted and your victory is tainted. Beat us legit as you feel is easy to do and then remove any cloud of illegitimacy this game holds.
                  TWDT-J CHAMPION POWER 2018
                  TWDT-B CHAMPION POWER 2018
                  TWDT TRIPLE CROWN MEMBER POWER 2018
                  TSL TRIPLE CROWN FINALIST 2018
                  TSLD CHAMPION 2018
                  TSLB CHAMPION 2018

                  Comment


                  • #10
                    Here are the bot commands sent during this match:

                    Code:
                    24 Mar 2019 18:34:50 (MatchBot11) : turban > !game Marksmin:Paladen
                    24 Mar 2019 18:34:55 (MatchBot11) : pineapple express > !myfreq
                    24 Mar 2019 18:34:59 (MatchBot11) : turban > !t1-setcaptain kim
                    24 Mar 2019 18:35:08 (MatchBot11) : turban > !t2-setcaptain Jess
                    24 Mar 2019 18:35:08 (MatchBot11) : yeH > !cap
                    24 Mar 2019 18:35:09 (MatchBot11) : Kim > !myfreq
                    24 Mar 2019 18:35:14 (MatchBot11) : Kim > !add mean
                    24 Mar 2019 18:35:17 (MatchBot11) : Kim > !add thrill
                    24 Mar 2019 18:35:20 (MatchBot11) : Nipple Nibbler > !myfreq
                    24 Mar 2019 18:35:21 (MatchBot11) : Kim > !add sing
                    24 Mar 2019 18:35:23 (MatchBot11) : Kim > !add vag
                    24 Mar 2019 18:35:25 (MatchBot11) : Kim > !add kim
                    24 Mar 2019 18:35:28 (MatchBot11) : tj hazuki > !myfreq
                    24 Mar 2019 18:35:28 (MatchBot11) : Jessup > !add yeh
                    24 Mar 2019 18:35:30 (MatchBot11) : Banks > !myfreq
                    24 Mar 2019 18:35:45 (MatchBot11) : Ardour > !myfreq
                    24 Mar 2019 18:35:49 (MatchBot11) : Jessup > !add duma
                    24 Mar 2019 18:35:50 (MatchBot11) : Lewanbawski > !myfreq
                    24 Mar 2019 18:35:51 (MatchBot11) : Jessup > !add des
                    24 Mar 2019 18:35:53 (MatchBot11) : Jessup > !add af
                    24 Mar 2019 18:35:56 (MatchBot11) : Jessup > !add beas
                    24 Mar 2019 18:35:56 (MatchBot11) : Sawyer > !myfreq
                    24 Mar 2019 18:35:58 (MatchBot11) : J-B-Inc > !myfreq
                    24 Mar 2019 18:36:00 (MatchBot11) : Jessup > !myfreq
                    24 Mar 2019 18:36:06 (MatchBot11) : Violence > !myfreq
                    24 Mar 2019 18:36:14 (MatchBot11) : Dele > !myfreq
                    24 Mar 2019 18:36:27 (MatchBot11) : destruct > !lagout <- first lagout command from destruct
                    24 Mar 2019 18:36:42 (MatchBot11) : Cuckold > !myfreq
                    24 Mar 2019 18:37:08 (MatchBot11) : bitsaver > !mf
                    24 Mar 2019 18:37:15 (MatchBot11) : diakka > !myfreq
                    24 Mar 2019 18:37:35 (MatchBot11) : Caralho > !myfreq
                    24 Mar 2019 18:39:34 (MatchBot11) : Kim > !help
                    24 Mar 2019 18:39:44 (MatchBot11) : Kim > !setcaptain violence
                    24 Mar 2019 18:40:07 (MatchBot11) : turban > !cap
                    24 Mar 2019 18:40:34 (MatchBot11) : tj hazuki > !myfreq
                    24 Mar 2019 18:40:57 (MatchBot11) : destruct > !lagout <- second lagout command from destruct
                    24 Mar 2019 18:41:34 (MatchBot11) : pineapple express > !myfreq
                    24 Mar 2019 18:42:22 (MatchBot11) : destruct > !lagout <- third lagout command from destruct. player out of lagout commands.
                    24 Mar 2019 18:42:53 (MatchBot11) : Jessup > !sub des:jess < jessup substituted destruct for himself. 
                    24 Mar 2019 18:43:05 (MatchBot11) : bitsaver > !mf
                    24 Mar 2019 18:43:05 (MatchBot11) : destruct > !lagout
                    24 Mar 2019 18:44:17 (MatchBot11) : destruct > !myfreq
                    24 Mar 2019 18:45:22 (MatchBot11) : Cyclone > !myfreq
                    24 Mar 2019 18:45:55 (MatchBot11) : Sawyer > !sub duma:saw <- sawyer trying to substitute himself in. not even assigned as an assistant captain by Paladen captains.
                    24 Mar 2019 18:46:10 (MatchBot11) : Joeses > !myfreq
                    24 Mar 2019 18:46:47 (MatchBot11) : Sawyer > !sub dumathoin:sawyer <- same as above.
                    24 Mar 2019 18:46:48 (MatchBot11) : Sawyer > !help
                    24 Mar 2019 18:46:54 (MatchBot11) : Sawyer > !cap
                    24 Mar 2019 18:48:01 (MatchBot11) : J-B-Inc > !myfreq
                    24 Mar 2019 18:50:57 (MatchBot11) : tj hazuki > !myfreq
                    24 Mar 2019 18:52:41 (MatchBot11) : Caralho > !myfreq
                    24 Mar 2019 19:00:19 (MatchBot11) : (pineapple express)> > !myfreq

                    Comment


                    • #11
                      My thoughts are as follows:

                      Destruct used up all his lagout commands and was substituted within 30 seconds from his last command. No additional sub attempts were made by any player prior to this substitution. I have also been told he did not immediately lag out after his last entry, and thus would say there was at most a 20 second windowwhere he was out of action and Paladen was playing with a man down. However, this in and of itself, is not worth appealing as it has nothing to do with bot issues.

                      I do not see anything out of the ordinary here that warrants a replay. Jessup might have been spammed by his team mates to make a substitute, and that could have affected his in-game performance, but no other assigned assistant or captain even attempted to make a substitute which is what you were appealing for. I also fail to see how the performance of one player could possibly make up for a 22 kill difference, but that is irrelevant in this case.

                      There will be a vote among TWL operators and this appeal will be handled later today.

                      Comment


                      • #12
                        Wtf they were on chat all yelling they couldn't do subs and it was not only sawyer saying this which is why I was trying to do in play game subs on dumathoin?? I wanted to sub out both dumathoin AND beast too but didn't even get around to beast as I gave up because of failed attempts and dying.

                        You guys did not add the proper amount of slots for us to use for subs this is a fact and the fact STILL remains you forced me , a player in the game to be the ONLY one who could do the commands to utilize subs which was impossible for me to do as I stated because of many failed attempts that was just getting me killed more. I don't even trust this report too honestly. The lagout reports fail often to show in game displays properly.

                        You admit you didn't set up the bot correctly and that it forced me alone to do all sub commands which affected 2 player slots. That is way more damage than just my single position alone as you are claiming. You effectively ruined 3 spots on our of our line because of this bot glitch which completely disrupted the squad gaming atmosphere for our squad and our sub out slots were nullified because of it too. Way more than just about me alone here turban.
                        TWDT-J CHAMPION POWER 2018
                        TWDT-B CHAMPION POWER 2018
                        TWDT TRIPLE CROWN MEMBER POWER 2018
                        TSL TRIPLE CROWN FINALIST 2018
                        TSLD CHAMPION 2018
                        TSLB CHAMPION 2018

                        Comment


                        • #13
                          3 player positions were affected by this bot glitch.
                          TWDT-J CHAMPION POWER 2018
                          TWDT-B CHAMPION POWER 2018
                          TWDT TRIPLE CROWN MEMBER POWER 2018
                          TSL TRIPLE CROWN FINALIST 2018
                          TSLD CHAMPION 2018
                          TSLB CHAMPION 2018

                          Comment


                          • #14
                            Proof sawyer was an Assistant on Paladen too.. wtf turban?? lol you are using faulty evidence from the bot glitch report as proof sawyer was not an assis on paladen?? That is because of the glitch itself. HE WAS AN ASSIS!!!

                            TWDT-J CHAMPION POWER 2018
                            TWDT-B CHAMPION POWER 2018
                            TWDT TRIPLE CROWN MEMBER POWER 2018
                            TSL TRIPLE CROWN FINALIST 2018
                            TSLD CHAMPION 2018
                            TSLB CHAMPION 2018

                            Comment


                            • #15
                              Turban I thought bot glitches and issues were sufficient enough for an appeal regardless of what team could win or not... if you grant one appeal due to bot and sub issues then it's best to grant them all and redo the whole week, not cherry pick and try find loop holes in reasoning as to why one squad with a glitch deserves a rematch over another. Simple solution is fix and test bots before league begins next time...

                              Comment

                              Working...