Announcement

Collapse
No announcement yet.

NSB PICK 'EM #58 and #59. 13th October 2018

Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • #51
    Originally posted by Introspective View Post
    Koba-Grozny does my second pick qualify mate?
    yeah, I think the intent was clear enough, but I'd suggest you use Early / mid / late in future to avoid confusion. Edit: oooops didn't see siablos response above. We'll discuss it and let you know.
    Last edited by Citizen Koba; 10-14-2018, 11:08 AM.

    Comment


    • #52
      Originally posted by Koba-Grozny View Post
      yeah, I think the intent was clear enough, but I'd suggest you use Early / mid / late in future to avoid confusion.
      Thanks mate, only done this once before will use the preferred terms next time.

      Comment


      • #53
        Originally posted by Koba-Grozny View Post
        yeah, I think the intent was clear enough, but I'd suggest you use Early / mid / late in future to avoid confusion. Edit: oooops didn't see siablos response above. We'll discuss it and let you know.
        Havent seen his post as he's on ignore but ok.

        Comment


        • #54
          Originally posted by Introspective View Post
          Havent seen his post as he's on ignore but ok.
          Ah. He said no... we'll figure it out though. It was easier when John l was still part of the crew cos then we'd could always get a majority vote one way or another. I might ask a couple other players their opinion.

          Comment


          • #55
            Originally posted by Koba-Grozny View Post
            Ah. He said no... we'll figure it out though. It was easier when John l was still part of the crew cos then we'd could always get a majority vote one way or another. I might ask a couple other players their opinion.
            Predictably, thanks for the update & help in clearing it up.

            Comment


            • #56
              Originally posted by BoxingFan85 View Post
              BoxingFan85, Tete , Decision , Wide
              BoxingFan85, Crawford , KO, Late, 2X
              I got one right ffs...


              Originally posted by Redd Foxx View Post
              Red Foxx, Tete , Decision , Wide
              Redd Foxx, Crawford , KO, Late, 3x

              Please note multiplier in effect.
              Sweet one there Redd!

              Comment


              • #57
                Originally posted by Koba-Grozny View Post
                Damn, if this hasn't started yet I'm changing from tete by close Decision to tete KO mid. The more I watch em the less I can see any conclusion but Aloyan getting destroyed.

                Koba. Tete KO mid
                Who is this ****ing imbecile?

                Comment


                • #58
                  Nsb pick 'em #58 and #59 (10/13/18) picks and points tally.

                  NSB PICK 'EM #58 AND #59 (10/13/18) PICKS AND POINTS TALLY.

                  RESULTS:

                  Tete, DEC, CLOSE
                  Crawford, KO, LATE



                  DuckAdonis: 45 (20, 25)
                  KOBA: 40 (20, 20)
                  Chrismart: 55 (25, 30) 1 perfect
                  DramaShow: 45 (20, 25)
                  NC Uppercut: 60 (30, 30) 2 perfect
                  FrankieClutch: 50 (25, 25)
                  Vinnykin: 45 (20, 25)
                  Mammoth: 45 (20, 25)
                  Idunnoshet: 50 (30, 20) 1 perfect
                  Redd Foxx: 115 (25, 90) 1 perfect, x3 used
                  BoxingFan85: 85 (25, 60) 1 perfect, x2 used
                  BlakBread: 45 (20, 25)
                  BigZ44: 50 (20, 30) 1 perfect
                  ruedboy: 45 (20, 25)
                  SceneBoxer: 45 (25, 20)
                  BLASTER1: 55 (25, 30) 1 perfect
                  SUBZER0ED: 45 (20, 25)
                  Ganondorf: 45 (20, 25)
                  Otrocubiche: 45 (20, 25)
                  The plunger man: 45 (20, 25)
                  A.K: 45 (20, 25)
                  KingTito: 50 (20, 30) 1 perfect
                  mathed: 80 (20, 60) 1 perfect, x2 used
                  siablo14: 70 (20, 50) x2 used
                  Eff Pandas: 50 (20, 30)
                  ShoulderRoll: 50 (20, 30)
                  jpowell100: 45 (20, 25)
                  Oluminati: 60 (20, 40) x2 used
                  Koolkc107: 40 (20, 20)
                  Just looking: 40 (20, 20)
                  King Arthur/Introspective: 50 (20, 30)1 perfect. subject to
                  confirmation.
                  RockyB: 50 (25, 25)
                  Baltimore: 45 (20, 25)
                  MulaKO: 40 (20, 20)
                  Julia Slobberts: 45 (20, 25)
                  HandsofIron: 75 (75) x3 used
                  MindGame: 30 (30) 1 perfect
                  Damn Wicked: 60 (60) 1 perfect, x2 used
                  B morph: 50 (50) x2 used
                  Last edited by PICK EM CREW; 10-26-2018, 05:28 PM.

                  Comment

                  Working...
                  X
                  ERROR: The request could not be satisfied

                  403 ERROR

                  The request could not be satisfied.


                  Request blocked. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
                  If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.

                  Generated by cloudfront (CloudFront)
                  Request ID: XXR5-Q_b9m_by8iIHO5A3gRLIBqLj5cKNy_STc1wufRl-r7_Y7ArOA==
                  
                  TOP
                  ERROR: The request could not be satisfied

                  403 ERROR

                  The request could not be satisfied.


                  Request blocked. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
                  If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.

                  Generated by cloudfront (CloudFront)
                  Request ID: 3yMKdz6cDElWX8KZyekM-mJMMPspzBE3DDk5LtVMu75DrMDMFiwSgA==