Hey Prussian,
thz for reply.
I ll watch that and try to participate next tournament.
-
We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
Hey Prussian,
thz for reply.
I ll watch that and try to participate next tournament.
Week Ten ~ Commencement Message
Tournament Week Nine is now complete. Tournament Week Ten is now underway. Thus far we have:
165 total matches resolved.
1 match was adjudicated this week by myself.
1 match remains.
Given the advanced nature of our tournament, only with great reluctance and repeated opportunities for resolution will I now be adjudicating matches. While I still ask our participants to complete their matches in a timely fashion, I recognize that the more than two month duration of our tournament represents a very considerable investment of time by all those remaining in contention for the Tournament Championship. Remaining matches will be accorded a measure of leeway to ensure they are decided in-game, and not by administrative means. Though again, in certain circumstances I reserve the right ensure tournament progression should the need arise. Also, match resolution will no longer be handled via threadmarked post to this thread. I shall use PM's as required to ensure timely match resolution.
There is only a single Round Seven "No Loss" Match ~ a Tournament Semi-Final Match. @Kidzin and @WilliamVonBillhelmHelmet are free to schedule this match at their convenience at some point over the next week or so. This extended span of time is possible as there may be three or more weeks until the "One Loss" Bracket is resolved and we can recognize our other Tournament Finalist.
Round Seven "No Loss" Match Host Responsibility is the Top Player in our "No Loss" Bracket Finalist Match.
Round Eight "One Loss" Matches should be resolved prior to noon (Pacific Time) on Friday, 03 August and Round Nine through Eleven "One Loss" Matches can commence immediately/as match brackets are filled. All remaining "One Loss" participants are asked to complete matches at a pace faster than a single match per week, as this would aid in closing the time-gap between "No Loss" and "One Loss" Brackets. For this reason, here "One Loss" Match Host Responsibilities through Round Eleven. Participants are encouraged to advance through match play as rapidly as possible.
Round Seven "One Loss" Match Host Responsibility is the Top Player in each Tournament Bracket.
Round Eight "One Loss" Match Host Responsibility is the Top Player in each Tournament Bracket.
Round Nine "One Loss" Match Host Responsibility is the Bottom Player in each Tournament Bracket.
Round Ten "One Loss" Match Host Responsibility is the Bottom Player in each Tournament Bracket.
Round Eleven "One Loss" Match Host Responsibility is the Bottom Player in each Tournament Bracket.
Please complete all Round Eight "One Loss" matches in a timely fashion by noon HBS-Time (Pacific Time) time next Friday, the 3rd of August, as I will review the circumstances of any unresolved matches at that time. While 24, 48 and 72-hour extensions are possible, anything more than that may constitute extreme circumstances and require adjudication.
If any problems or questions arise, please contact me at the earliest possible opportunity. I can not work to resolve specific problems and questions if I don't know about them. : )
And as a precious touchstone of our tournament, please review:
TOURNAMENT CONSIDERATIONS (derivative of):
1.) Please treat everyone with respect. This is a game.
2.) Please be responsible for your actions and words. This is a game.
3.) Please be welcoming and keep it considerate. This is a game.
4.) Have fun and be kind to one another! This is a FUN game.
5.) If within a week, you and your Bracket Opponent can not come to match resolution. Please decide between yourselves which will move on to the next Round and submit the appropriate Challonge.com input.
And as ever, good luck and good BATTLETECH gaming! :bow:
165 total matches resolved.
1 match was adjudicated this week by myself.
1 match remains.
Given the advanced nature of our tournament, only with great reluctance and repeated opportunities for resolution will I now be adjudicating matches. While I still ask our participants to complete their matches in a timely fashion, I recognize that the more than two month duration of our tournament represents a very considerable investment of time by all those remaining in contention for the Tournament Championship. Remaining matches will be accorded a measure of leeway to ensure they are decided in-game, and not by administrative means. Though again, in certain circumstances I reserve the right ensure tournament progression should the need arise. Also, match resolution will no longer be handled via threadmarked post to this thread. I shall use PM's as required to ensure timely match resolution.
There is only a single Round Seven "No Loss" Match ~ a Tournament Semi-Final Match. @Kidzin and @WilliamVonBillhelmHelmet are free to schedule this match at their convenience at some point over the next week or so. This extended span of time is possible as there may be three or more weeks until the "One Loss" Bracket is resolved and we can recognize our other Tournament Finalist.
Round Seven "No Loss" Match Host Responsibility is the Top Player in our "No Loss" Bracket Finalist Match.
Round Eight "One Loss" Matches should be resolved prior to noon (Pacific Time) on Friday, 03 August and Round Nine through Eleven "One Loss" Matches can commence immediately/as match brackets are filled. All remaining "One Loss" participants are asked to complete matches at a pace faster than a single match per week, as this would aid in closing the time-gap between "No Loss" and "One Loss" Brackets. For this reason, here "One Loss" Match Host Responsibilities through Round Eleven. Participants are encouraged to advance through match play as rapidly as possible.
Round Seven "One Loss" Match Host Responsibility is the Top Player in each Tournament Bracket.
Round Eight "One Loss" Match Host Responsibility is the Top Player in each Tournament Bracket.
Round Nine "One Loss" Match Host Responsibility is the Bottom Player in each Tournament Bracket.
Round Ten "One Loss" Match Host Responsibility is the Bottom Player in each Tournament Bracket.
Round Eleven "One Loss" Match Host Responsibility is the Bottom Player in each Tournament Bracket.
Please complete all Round Eight "One Loss" matches in a timely fashion by noon HBS-Time (Pacific Time) time next Friday, the 3rd of August, as I will review the circumstances of any unresolved matches at that time. While 24, 48 and 72-hour extensions are possible, anything more than that may constitute extreme circumstances and require adjudication.
If any problems or questions arise, please contact me at the earliest possible opportunity. I can not work to resolve specific problems and questions if I don't know about them. : )
And as a precious touchstone of our tournament, please review:
TOURNAMENT CONSIDERATIONS (derivative of):
1.) Please treat everyone with respect. This is a game.
2.) Please be responsible for your actions and words. This is a game.
3.) Please be welcoming and keep it considerate. This is a game.
4.) Have fun and be kind to one another! This is a FUN game.
5.) If within a week, you and your Bracket Opponent can not come to match resolution. Please decide between yourselves which will move on to the next Round and submit the appropriate Challonge.com input.
And as ever, good luck and good BATTLETECH gaming! :bow:
I and others are working to ensure any outstanding matches are resolved in a timely manner... or administratively adjudicated accordingly.
While I am willing to work with all remaining participants to best permit match resolution to be determined in-game rather than by adjudication, I must now reinforce than match delay requests must be brought to my attention as soon as the situation presents itself. Delays of 24, 48 and even 72-hours are possible. More than that, not so much. :bow:
Thank you one and all for your interest / participation in this tournament. It is greatly appreciated. :bow:
And as ever good luck and good gaming!
While I am willing to work with all remaining participants to best permit match resolution to be determined in-game rather than by adjudication, I must now reinforce than match delay requests must be brought to my attention as soon as the situation presents itself. Delays of 24, 48 and even 72-hours are possible. More than that, not so much. :bow:
Thank you one and all for your interest / participation in this tournament. It is greatly appreciated. :bow:
And as ever good luck and good gaming!
Week Eleven ~ Commencement Message
Tournament Week Ten is now complete. Tournament Week Eleven is now underway. Thus far we have:
173 of a possible 180 (or 181) total matches resolved.
1 match was adjudicated this week by myself.
1 match remains.
Given the advanced nature of our tournament, only with great reluctance and repeated opportunities for resolution will I now be adjudicating matches. While I still ask our participants to complete their matches in a timely fashion, I recognize that the more than two-month duration of our tournament represents a very considerable investment of time by all those remaining in contention for the Tournament Championship. Remaining matches will be accorded a measure of leeway to ensure they are decided in-game, and not by administrative means. However I do reserve the right to ensure tournament progression through match administrative ajudication should the need arise. Also, match resolution will no longer be handled via threadmarked post to this thread. I shall use PM's as required to ensure timely match resolution.
There is only a single Round Seven "No Loss" Match ~ a Tournament Semi-Final Match. @Kidzin and @WilliamVonBillhelmHelmet are free to schedule this match at their convenience at some point over the next week or so. This extended span of time is possible as there may be two or more weeks until the "One Loss" Bracket is resolved and we can recognize our other Tournament Finalist.
Round Seven "No Loss" Match Host Responsibility is the Top Player in our "No Loss" Bracket Finalist Match.
A single Round Eight Match remains to be resolved. This match is scheduled or Saturday, 04AUG. Round Nine "One Loss" Matches should be resolved prior to noon (Pacific Time) on Friday, 10 August and Round Nine through Eleven "One Loss" Matches can commence immediately/as match brackets are filled. All remaining "One Loss" participants are asked to complete matches at a pace faster than a single match per week, as this would aid in closing the time-gap between "No Loss" and "One Loss" Brackets. For this reason, here "One Loss" Match Host Responsibilities through Round Eleven. Participants are encouraged to advance through match play as rapidly as possible.
Round Eight "One Loss" Match Host Responsibility is the Top Player in each Tournament Bracket.
Round Nine "One Loss" Match Host Responsibility is the Bottom Player in each Tournament Bracket.
Round Ten "One Loss" Match Host Responsibility is the Bottom Player in each Tournament Bracket.
Round Eleven "One Loss" Match Host Responsibility is the Bottom Player in each Tournament Bracket.
Please complete all Round Nine "One Loss" matches in a timely fashion by noon HBS-Time (Pacific Time) time next Friday, the 10th of August, as I will review the circumstances of any unresolved matches at that time. While 24, 48 and 72-hour extensions are possible, anything more than that may constitute extreme circumstances and require adjudication.
If any problems or questions arise, please contact me at the earliest possible opportunity. I can not work to resolve specific problems and questions if I don't know about them. : )
And as a precious touchstone of our tournament, please review:
TOURNAMENT CONSIDERATIONS (derivative of):
1.) Please treat everyone with respect. This is a game.
2.) Please be responsible for your actions and words. This is a game.
3.) Please be welcoming and keep it considerate. This is a game.
4.) Have fun and be kind to one another! This is a FUN game.
5.) If within a week, you and your Bracket Opponent can not come to match resolution. Please decide between yourselves which will move on to the next Round and submit the appropriate Challonge.com input.
And as ever, good luck and good BATTLETECH gaming! :bow:
173 of a possible 180 (or 181) total matches resolved.
1 match was adjudicated this week by myself.
1 match remains.
Given the advanced nature of our tournament, only with great reluctance and repeated opportunities for resolution will I now be adjudicating matches. While I still ask our participants to complete their matches in a timely fashion, I recognize that the more than two-month duration of our tournament represents a very considerable investment of time by all those remaining in contention for the Tournament Championship. Remaining matches will be accorded a measure of leeway to ensure they are decided in-game, and not by administrative means. However I do reserve the right to ensure tournament progression through match administrative ajudication should the need arise. Also, match resolution will no longer be handled via threadmarked post to this thread. I shall use PM's as required to ensure timely match resolution.
There is only a single Round Seven "No Loss" Match ~ a Tournament Semi-Final Match. @Kidzin and @WilliamVonBillhelmHelmet are free to schedule this match at their convenience at some point over the next week or so. This extended span of time is possible as there may be two or more weeks until the "One Loss" Bracket is resolved and we can recognize our other Tournament Finalist.
Round Seven "No Loss" Match Host Responsibility is the Top Player in our "No Loss" Bracket Finalist Match.
A single Round Eight Match remains to be resolved. This match is scheduled or Saturday, 04AUG. Round Nine "One Loss" Matches should be resolved prior to noon (Pacific Time) on Friday, 10 August and Round Nine through Eleven "One Loss" Matches can commence immediately/as match brackets are filled. All remaining "One Loss" participants are asked to complete matches at a pace faster than a single match per week, as this would aid in closing the time-gap between "No Loss" and "One Loss" Brackets. For this reason, here "One Loss" Match Host Responsibilities through Round Eleven. Participants are encouraged to advance through match play as rapidly as possible.
Round Eight "One Loss" Match Host Responsibility is the Top Player in each Tournament Bracket.
Round Nine "One Loss" Match Host Responsibility is the Bottom Player in each Tournament Bracket.
Round Ten "One Loss" Match Host Responsibility is the Bottom Player in each Tournament Bracket.
Round Eleven "One Loss" Match Host Responsibility is the Bottom Player in each Tournament Bracket.
Please complete all Round Nine "One Loss" matches in a timely fashion by noon HBS-Time (Pacific Time) time next Friday, the 10th of August, as I will review the circumstances of any unresolved matches at that time. While 24, 48 and 72-hour extensions are possible, anything more than that may constitute extreme circumstances and require adjudication.
If any problems or questions arise, please contact me at the earliest possible opportunity. I can not work to resolve specific problems and questions if I don't know about them. : )
And as a precious touchstone of our tournament, please review:
TOURNAMENT CONSIDERATIONS (derivative of):
1.) Please treat everyone with respect. This is a game.
2.) Please be responsible for your actions and words. This is a game.
3.) Please be welcoming and keep it considerate. This is a game.
4.) Have fun and be kind to one another! This is a FUN game.
5.) If within a week, you and your Bracket Opponent can not come to match resolution. Please decide between yourselves which will move on to the next Round and submit the appropriate Challonge.com input.
And as ever, good luck and good BATTLETECH gaming! :bow:
Zak and I looking like we will play our round 9 match on Saturday the 11th. I assume this will be fine as the top of the one loss bracket is still on round 8?
A 24-hour extension till Saturday the 11th of August is fine.
But please don't compare Rounds, as the "No Loss" bracket has only a single match remaining prior to the Championship Match. While the "One Loss" Bracket has five matches remaining prior to the Championship Match.
The way it stands now, the "No Loss" Bracket has been in a holding pattern for the better part of a month, waiting for the "One Loss" Bracket to catch up.
We knew from the very beginning that this PauseEX for the "No Loss" Bracket was going to be a result of a 91-participant double-elimination format. So as I request every week, if "One Loss" Bracket matches can be held at a pace faster than one per week, that would be appreciated. :bow:
Attempts #1 and #2 of @HonorKnight 's still-unresolved match with @Anaro Sunfire (Subtitle: Comstar favors no man. However, Comstar may have a soft spot for Hunchbacks):
This week I face @Anaro Sunfire in honorable combat. Unfortunately, @Anaro Sunfire and TheCallidus were unable to resolve their match due to scheduling conflicts, and by the time TheCallidus was deemed to have forfeited, it was already too late for a match over the weekend. @Anaro Sunfire and I are off of each others' time zones by 8 hours, making it near-impossible to arrange a match during the week due to our respective schedules, so the only opportunity we saw was a delayed match on the following Saturday, which we scheduled for 6 PM my time, 10 AM his time.
Attempt #1:
After a half-dozen attempts to create the match failed to connect, we finally faced off in glorious combat. We both approached each other, meeting largely in the middle. However, after combat was engaged, on round 6 my opponent withdrew back out of sensor range. I immediately sent my scout forward to re-engage in combat, only to find my scout sensor locked and all alone, so I pulled it back to the safety of the rest of my group, briefly leaving sensor range myself. Over the course of a few turns of me being positioned just on my side of the central hill, using the hill for cover, and @Anaro Sunfire hugging the edge of sensor range, we exchanged a little LRM fire (which was going in my favor due to turn order), until at last my opponent began to close for combat. Seeing the nature of the OpFor lance, I knew backstabs were incoming, so I tried to keep myself positioned with my back to rocks or cliffs, not wanting a repeat of my misadventures with @Zakhodit! This worked for a little while, with my steadily doing more damage to my opponent than he was doing to me, until he managed to get a back shot at my Hunchback 4G with just two medium lasers. One of the medium lasers hit my left torso, just barely penetrating with 5 damage to structure, but by a game-changing act of RNGesus, that scratch became a critical hit which triggered an ammo explosion! Picking my jaw up off the floor, I saw the writing on the wall that this Hunchback was now going to be a melee specialist for the remainder of this match, and I charged him toward my opponent's nearby Hunchback 4P, filling up with evasion and in range to melee next turn. I think a couple more 'Mechs moved, but the details are lost to my memory due to the shock of what happened next: Comstar decreed that our match was over and we could not play it through. I wasn't sure where to go from here, I even worried @Anaro Sunfire might think I had caused the disconnect on purpose due to the devastating critical hit I had just taken! But he was very reasonable about it and just suggested we start again. Nonetheless, this outcome left me unsettled. Even if I ended up winning the next match, would it really be I who earned those laurels? Or would it be forever tainted because Comstar, not I, had effectively placed that crown upon my head?
Attempt #2:
A couple more attempts to join the multiplayer lobby later, I faced off with my opponent once more in slightly less-glorious and more-disconcerted combat. This time there was no prolonged holding back at maximum sensor range, we faced each other right in the middle, alongside the central hill (although I had the sense to keep my high-evasion 'Mechs in front and protecting my flanks this time to blunt the effectiveness of a backstabbing strategy). Very quickly after combat was engaged, @Anaro Sunfire's moved his Hunchback 4P to the front line and entered Guard mode. I then broke the Guard with a Firestarter DFA and unleashed a heavy volley of instability-inducing weaponry on it, knocking it down with exposed structure in its left shoulder. This knockdown provided me with a potential full round of optimal-range called shots on it the next turn before it could stand up (technically up to 5 called shots since one of my 'Mechs hadn't moved yet before the knockdown). @Anaro Sunfire tried to retaliate by moving multiple 'Mechs to a side flank of my Firestarter and trying to take down its weakened leg with multiple alpha strike before it could pull back to safety; however, with the aid of Cover and 4 stacks of Evasion, I retained 2 structure in that leg and was free to jump back and reorient myself to protect that leg. I then got less than halfway through what should have been a deadly chain of called shots before Comstar intervened once more, and decreed that our match was over. As agonizing as it was to watch this highly-favorable combat situation interrupted and voided, I have to admit to feeling some comfort that at least these two Comstar interruptions had alternated between when @Anaro Sunfire was in the lead and when I was in the lead. So at this point, no matter who was the final victor of our series of matches, Comstar could not be said to have played favorites, and our fate would be determined by our own merit. We did joke, though, that Comstar seemed opposed to violence against Hunchbacks today, separating us each time a Hunchback was taking heavy damage!
Unfortunately, we were now over two hours into this attempt to resolve our match, and all signs were pointing to a continuing series of connection problems tonight. So we will be forced to try again tomorrow and hope that Comstar will allow us a fair fight without interrupting us this time.
This week I face @Anaro Sunfire in honorable combat. Unfortunately, @Anaro Sunfire and TheCallidus were unable to resolve their match due to scheduling conflicts, and by the time TheCallidus was deemed to have forfeited, it was already too late for a match over the weekend. @Anaro Sunfire and I are off of each others' time zones by 8 hours, making it near-impossible to arrange a match during the week due to our respective schedules, so the only opportunity we saw was a delayed match on the following Saturday, which we scheduled for 6 PM my time, 10 AM his time.
Attempt #1:
After a half-dozen attempts to create the match failed to connect, we finally faced off in glorious combat. We both approached each other, meeting largely in the middle. However, after combat was engaged, on round 6 my opponent withdrew back out of sensor range. I immediately sent my scout forward to re-engage in combat, only to find my scout sensor locked and all alone, so I pulled it back to the safety of the rest of my group, briefly leaving sensor range myself. Over the course of a few turns of me being positioned just on my side of the central hill, using the hill for cover, and @Anaro Sunfire hugging the edge of sensor range, we exchanged a little LRM fire (which was going in my favor due to turn order), until at last my opponent began to close for combat. Seeing the nature of the OpFor lance, I knew backstabs were incoming, so I tried to keep myself positioned with my back to rocks or cliffs, not wanting a repeat of my misadventures with @Zakhodit! This worked for a little while, with my steadily doing more damage to my opponent than he was doing to me, until he managed to get a back shot at my Hunchback 4G with just two medium lasers. One of the medium lasers hit my left torso, just barely penetrating with 5 damage to structure, but by a game-changing act of RNGesus, that scratch became a critical hit which triggered an ammo explosion! Picking my jaw up off the floor, I saw the writing on the wall that this Hunchback was now going to be a melee specialist for the remainder of this match, and I charged him toward my opponent's nearby Hunchback 4P, filling up with evasion and in range to melee next turn. I think a couple more 'Mechs moved, but the details are lost to my memory due to the shock of what happened next: Comstar decreed that our match was over and we could not play it through. I wasn't sure where to go from here, I even worried @Anaro Sunfire might think I had caused the disconnect on purpose due to the devastating critical hit I had just taken! But he was very reasonable about it and just suggested we start again. Nonetheless, this outcome left me unsettled. Even if I ended up winning the next match, would it really be I who earned those laurels? Or would it be forever tainted because Comstar, not I, had effectively placed that crown upon my head?
Attempt #2:
A couple more attempts to join the multiplayer lobby later, I faced off with my opponent once more in slightly less-glorious and more-disconcerted combat. This time there was no prolonged holding back at maximum sensor range, we faced each other right in the middle, alongside the central hill (although I had the sense to keep my high-evasion 'Mechs in front and protecting my flanks this time to blunt the effectiveness of a backstabbing strategy). Very quickly after combat was engaged, @Anaro Sunfire's moved his Hunchback 4P to the front line and entered Guard mode. I then broke the Guard with a Firestarter DFA and unleashed a heavy volley of instability-inducing weaponry on it, knocking it down with exposed structure in its left shoulder. This knockdown provided me with a potential full round of optimal-range called shots on it the next turn before it could stand up (technically up to 5 called shots since one of my 'Mechs hadn't moved yet before the knockdown). @Anaro Sunfire tried to retaliate by moving multiple 'Mechs to a side flank of my Firestarter and trying to take down its weakened leg with multiple alpha strike before it could pull back to safety; however, with the aid of Cover and 4 stacks of Evasion, I retained 2 structure in that leg and was free to jump back and reorient myself to protect that leg. I then got less than halfway through what should have been a deadly chain of called shots before Comstar intervened once more, and decreed that our match was over. As agonizing as it was to watch this highly-favorable combat situation interrupted and voided, I have to admit to feeling some comfort that at least these two Comstar interruptions had alternated between when @Anaro Sunfire was in the lead and when I was in the lead. So at this point, no matter who was the final victor of our series of matches, Comstar could not be said to have played favorites, and our fate would be determined by our own merit. We did joke, though, that Comstar seemed opposed to violence against Hunchbacks today, separating us each time a Hunchback was taking heavy damage!
Unfortunately, we were now over two hours into this attempt to resolve our match, and all signs were pointing to a continuing series of connection problems tonight. So we will be forced to try again tomorrow and hope that Comstar will allow us a fair fight without interrupting us this time.
Last edited:
@HBS_Null, are there better or worse times through the day (or week) to try and hold such world-spanning Tournament matches?
There very well may not be. But with the tourney now approaching three months in duration and the Tournament Champion fast approaching, I felt asking the question might help those still in the hunt to have the best chance possible to complete their matches. :bow:
There very well may not be. But with the tourney now approaching three months in duration and the Tournament Champion fast approaching, I felt asking the question might help those still in the hunt to have the best chance possible to complete their matches. :bow:
@HonorKnight lol I actually think you might have this one, the no arclight is killing me on the initiative. I will be praying tonight to the RNG gods and see how we go on the field of battle in the morning.
We managed to complete our match today on our third try, and @Anaro Sunfire earned a well-deserved victory. His Treb, 4P, 2xFirestarter team defeated my Treb, 4G, Enforcer, Firestarter team.
We didn't rush into melee quite so fast as our 2nd match, instead it started more like our 1st match, exchanging sensor locks and LRM fire while gradually closing the distance and each of us trying to outmaneuver the other. My initiative advantage continuously gave me the upper hand in damage dealt with our Trebuchets, I imagine it only went on as long as it did as a reaction to our second match which went very poorly for him when he moved his Hunchback in too close. In the waning turns of the LRM rain, @Anaro Sunfire circled around behind my lance with one of his Firestarters, presumably to increase his opportunities for backstabs through flanking.
Eventually @Anaro Sunfire closed into close quarters, and the dance of death began in earnest. As the Firestarters closed in, I moved my vulnerable Trebuchet and Hunchback up against a cliff face, where only a few spots are valid jumping points. As his Bulwark Hunchback 4P stepped cautiously over a ridge and Guarded before beginning its assault on my Bulwark Hunchback 4G, One of his Firestarters jumped to a spot on the cliff face and began backstabbing that same Hunchback, his Apex Trebuchet kept up breaching shot LRM15s on it. His final Frestarter tried to join the fray too, but couldn't find another position in the cliffside rubble to execute another backstab, so it just jumped a couple hexes away along the edge of the cliff and contributed to the dog-pile on my Hunchback 4G. We reached 100 fury at this point, and we each used our called shots on the others' Hunchback. My fury called shot was to his leg hit but didn't completely destroy the leg; I then followed it up with the rest of my lance with side arc shots to first blow out the leg to knock it down, then core it out (taking out a side torso along the way due to damage spread). His fury called shot was not fruitless either, managing to blow out my Hunchback 4G's AC/20.
At this point I was reminded that I truly despise HBS's rules for what locations are valid to melee from. My Hunchback 4G may have lost its AC/20, but there was a perfect melee target right next to it in the form of a Firestarter; this was an ideal target for a Hunchback punch, as it would ignore the evasive pips and one 80-damage punch can be devastating to a Light 'Mech such as this. Yet somehow I guess the slope it was standing on made it not a valid target for melee. Even though it was standing in a spot I could easily walk to, I was unable to melee it.
So anyhow, since my Hunchback was now really only good for melee, and it wasn't able to do that here, I started sprinting it towards @Anaro Sunfire's Trebuchet, as my Enforcer and Firestarter also moved in that direction, trying to keep enough distance to avoid any further backstabs. A couple turns later, I dog-piled on his Trebuchet, got it well into unsteady territory with a firestarter punch and a Treb volley, and charged my Hunchback in to... once again not be able to melee due to the bizarre logic HBS uses to decide what are valid melee locations. Of the 3 locations next to it on this side that were adjacent to his Trebuchet, only the spot my Firestarter was standing in was a valid place to melee his Treb from, so instead of using its deadly melee, my Hunchback had to sit there poking it with its few remaining weapons instead. Even my Enforcer couldn't DFA the treb, neither from the open two spots on the near side nor the two open spots on the far side, all were invalid DFA locations for some reason! So his Trebuchet, which should have been knocked flat and killed before it could react, instead stayed standing and alive for two more turns, while his Firestarters got extra time to wear me down with heat shutdowns and backstabs.
Ultimately I did kill his Trebuchet, but at great cost due to how long it took with my Hunchback never being able to melee it. I forget whether I lost my Treb before or after I killed his Treb, but it came down to my 4G+FS versus his FS+FS... and a few turns later my 4G alone versus his FS alone. Our last two 'Mechs ran (and jumped) circles around each other first on the side and then the top of the center hill, him managing to stay continuously out of melee range (at the cost of not being able to use his machine guns either), while keeping more stacks of evasion and using two medium lasers versus my one medium laser and a small laser... until eventually the math of this situation added up to my lumbering hunchback falling to his more maneuverable Firestarter. A very interesting match, I wish you luck in the rounds to come, @Anaro Sunfire!
But seriously, use Arclight on a light in the future, it makes all the difference, especially if you want to use LRMs in the early game!
We didn't rush into melee quite so fast as our 2nd match, instead it started more like our 1st match, exchanging sensor locks and LRM fire while gradually closing the distance and each of us trying to outmaneuver the other. My initiative advantage continuously gave me the upper hand in damage dealt with our Trebuchets, I imagine it only went on as long as it did as a reaction to our second match which went very poorly for him when he moved his Hunchback in too close. In the waning turns of the LRM rain, @Anaro Sunfire circled around behind my lance with one of his Firestarters, presumably to increase his opportunities for backstabs through flanking.
Eventually @Anaro Sunfire closed into close quarters, and the dance of death began in earnest. As the Firestarters closed in, I moved my vulnerable Trebuchet and Hunchback up against a cliff face, where only a few spots are valid jumping points. As his Bulwark Hunchback 4P stepped cautiously over a ridge and Guarded before beginning its assault on my Bulwark Hunchback 4G, One of his Firestarters jumped to a spot on the cliff face and began backstabbing that same Hunchback, his Apex Trebuchet kept up breaching shot LRM15s on it. His final Frestarter tried to join the fray too, but couldn't find another position in the cliffside rubble to execute another backstab, so it just jumped a couple hexes away along the edge of the cliff and contributed to the dog-pile on my Hunchback 4G. We reached 100 fury at this point, and we each used our called shots on the others' Hunchback. My fury called shot was to his leg hit but didn't completely destroy the leg; I then followed it up with the rest of my lance with side arc shots to first blow out the leg to knock it down, then core it out (taking out a side torso along the way due to damage spread). His fury called shot was not fruitless either, managing to blow out my Hunchback 4G's AC/20.
At this point I was reminded that I truly despise HBS's rules for what locations are valid to melee from. My Hunchback 4G may have lost its AC/20, but there was a perfect melee target right next to it in the form of a Firestarter; this was an ideal target for a Hunchback punch, as it would ignore the evasive pips and one 80-damage punch can be devastating to a Light 'Mech such as this. Yet somehow I guess the slope it was standing on made it not a valid target for melee. Even though it was standing in a spot I could easily walk to, I was unable to melee it.
So anyhow, since my Hunchback was now really only good for melee, and it wasn't able to do that here, I started sprinting it towards @Anaro Sunfire's Trebuchet, as my Enforcer and Firestarter also moved in that direction, trying to keep enough distance to avoid any further backstabs. A couple turns later, I dog-piled on his Trebuchet, got it well into unsteady territory with a firestarter punch and a Treb volley, and charged my Hunchback in to... once again not be able to melee due to the bizarre logic HBS uses to decide what are valid melee locations. Of the 3 locations next to it on this side that were adjacent to his Trebuchet, only the spot my Firestarter was standing in was a valid place to melee his Treb from, so instead of using its deadly melee, my Hunchback had to sit there poking it with its few remaining weapons instead. Even my Enforcer couldn't DFA the treb, neither from the open two spots on the near side nor the two open spots on the far side, all were invalid DFA locations for some reason! So his Trebuchet, which should have been knocked flat and killed before it could react, instead stayed standing and alive for two more turns, while his Firestarters got extra time to wear me down with heat shutdowns and backstabs.
Ultimately I did kill his Trebuchet, but at great cost due to how long it took with my Hunchback never being able to melee it. I forget whether I lost my Treb before or after I killed his Treb, but it came down to my 4G+FS versus his FS+FS... and a few turns later my 4G alone versus his FS alone. Our last two 'Mechs ran (and jumped) circles around each other first on the side and then the top of the center hill, him managing to stay continuously out of melee range (at the cost of not being able to use his machine guns either), while keeping more stacks of evasion and using two medium lasers versus my one medium laser and a small laser... until eventually the math of this situation added up to my lumbering hunchback falling to his more maneuverable Firestarter. A very interesting match, I wish you luck in the rounds to come, @Anaro Sunfire!
But seriously, use Arclight on a light in the future, it makes all the difference, especially if you want to use LRMs in the early game!
Last edited:
Week Twelve ~ Commencement Message
Tournament Week Eleven is now complete. Tournament Week Twelve is now underway. Thus far we have:
175 of a possible 180 (or 181) total matches resolved.
2 matches remain to be resolved from last week.
5 (or 6) matches remain in the tournament as a whole.
Given the advanced nature of our tournament, only with great reluctance and repeated opportunities for resolution will I now be adjudicating matches. While I still ask our participants to complete their matches in a timely fashion, I recognize that the more than two-month duration of our tournament represents a very considerable investment of time by all those remaining in contention for the Tournament Championship. Remaining matches will be accorded a measure of leeway to ensure they are decided in-game, and not by administrative means. However I do reserve the right to ensure tournament progression through match administrative ajudication should the need arise. Also, match resolution will no longer be handled via threadmarked post to this thread. I shall use PM's as required to ensure timely match resolution.
Our “No Loss” Bracket Champion has been recognized. Congratulations to @WilliamVonBillhelmHelmet on his remarkable and unbroken series of Victories. :bow:
Two Round Nine Matches remain to be resolved. These matches will be resolved by Sunday, 12AUG. The Round Ten "One Loss" Match should be resolved prior to noon (Pacific Time) on Friday, 17 August and Round Ten and Eleven "One Loss" Matches can commence as soon as match brackets are filled. All remaining "One Loss" participants are asked to complete matches at a pace faster than a single match per week, as this would aid in closing the time-gap between "No Loss" and "One Loss" Brackets. For this reason, here "One Loss" Match Host Responsibilities through Round Eleven. Participants are encouraged to advance through match play as rapidly as possible.
Round Nine "One Loss" Match Host Responsibility is the Bottom Player in each Tournament Bracket.
Round Ten "One Loss" Match Host Responsibility is the Bottom Player in each Tournament Bracket.
Round Eleven "One Loss" Match Host Responsibility is the Bottom Player in each Tournament Bracket.
Please complete the Round Ten "One Loss" match in a timely fashion by noon HBS-Time (Pacific Time) time next Friday, the 17th of August, as I will review the circumstances of any unresolved matches at that time. While 24, 48 and 72-hour extensions are possible, anything more than that may constitute extreme circumstances and require adjudication.
If any problems or questions arise, please contact me at the earliest possible opportunity. I can not work to resolve specific problems and questions if I don't know about them. : )
And as a precious touchstone of our tournament, please review:
TOURNAMENT CONSIDERATIONS (derivative of):
1.) Please treat everyone with respect. This is a game.
2.) Please be responsible for your actions and words. This is a game.
3.) Please be welcoming and keep it considerate. This is a game.
4.) Have fun and be kind to one another! This is a FUN game.
5.) If within a week, you and your Bracket Opponent can not come to match resolution. Please decide between yourselves which will move on to the next Round and submit the appropriate Challonge.com input.
And as ever, good luck and good BATTLETECH gaming! :bow:
175 of a possible 180 (or 181) total matches resolved.
2 matches remain to be resolved from last week.
5 (or 6) matches remain in the tournament as a whole.
Given the advanced nature of our tournament, only with great reluctance and repeated opportunities for resolution will I now be adjudicating matches. While I still ask our participants to complete their matches in a timely fashion, I recognize that the more than two-month duration of our tournament represents a very considerable investment of time by all those remaining in contention for the Tournament Championship. Remaining matches will be accorded a measure of leeway to ensure they are decided in-game, and not by administrative means. However I do reserve the right to ensure tournament progression through match administrative ajudication should the need arise. Also, match resolution will no longer be handled via threadmarked post to this thread. I shall use PM's as required to ensure timely match resolution.
Our “No Loss” Bracket Champion has been recognized. Congratulations to @WilliamVonBillhelmHelmet on his remarkable and unbroken series of Victories. :bow:
Two Round Nine Matches remain to be resolved. These matches will be resolved by Sunday, 12AUG. The Round Ten "One Loss" Match should be resolved prior to noon (Pacific Time) on Friday, 17 August and Round Ten and Eleven "One Loss" Matches can commence as soon as match brackets are filled. All remaining "One Loss" participants are asked to complete matches at a pace faster than a single match per week, as this would aid in closing the time-gap between "No Loss" and "One Loss" Brackets. For this reason, here "One Loss" Match Host Responsibilities through Round Eleven. Participants are encouraged to advance through match play as rapidly as possible.
Round Nine "One Loss" Match Host Responsibility is the Bottom Player in each Tournament Bracket.
Round Ten "One Loss" Match Host Responsibility is the Bottom Player in each Tournament Bracket.
Round Eleven "One Loss" Match Host Responsibility is the Bottom Player in each Tournament Bracket.
Please complete the Round Ten "One Loss" match in a timely fashion by noon HBS-Time (Pacific Time) time next Friday, the 17th of August, as I will review the circumstances of any unresolved matches at that time. While 24, 48 and 72-hour extensions are possible, anything more than that may constitute extreme circumstances and require adjudication.
If any problems or questions arise, please contact me at the earliest possible opportunity. I can not work to resolve specific problems and questions if I don't know about them. : )
And as a precious touchstone of our tournament, please review:
TOURNAMENT CONSIDERATIONS (derivative of):
1.) Please treat everyone with respect. This is a game.
2.) Please be responsible for your actions and words. This is a game.
3.) Please be welcoming and keep it considerate. This is a game.
4.) Have fun and be kind to one another! This is a FUN game.
5.) If within a week, you and your Bracket Opponent can not come to match resolution. Please decide between yourselves which will move on to the next Round and submit the appropriate Challonge.com input.
And as ever, good luck and good BATTLETECH gaming! :bow:
Yeah, congratulations @WilliamVonBillhelmHelmet !! Let's see who reaches the final match (or the first of the two final matches). 
Despite past delays impacting this past week's match, efforts continue to get us back on track. More to follow...
@Anaro Sunfire and @Leffe7's match is scheduled for Saturday, the day after tomorrow.
I ask @Zakhodit to be prepared to work with the winner in scheduling and holding the next match in a timely fashion, perhaps as early as this Saturday night or Sunday.
Similarly, I ask @Kidzin to be prepared to work with the winner of this second match, to hold the final "One Loss" Bracket Match of the Tournament.
After more than 3 months, Valhalla's Tournament of Champion's Final(s) against @WilliamVonBillhelmHelmet is (are) fast approaching. :bow:
Week Thirteen ~ Commencement Message
Tournament Week Twelve is now complete. Tournament Week Thirteen is now underway. Thus far we have:
177 of a possible 180 (or 181) total matches have been resolved.
Just two matches remain prior to the Tournament Finals.
Given the advanced nature of our tournament, only with great reluctance and repeated opportunities for resolution will I now be adjudicating matches.
Our “No Loss” Bracket Champion has been recognized. Congratulations to @WilliamVonBillhelmHelmet on his remarkable and unbroken series of Victories. :bow:
Only two "No Loss" matches remain. This week's match will see @Anaro Sunfire facing off against @Zakhodit. This match should be resolved prior to noon (Pacific Time) on Friday, 24 August, though an extension is possible given that last week's match delayed the start of your Tournament Window. The winner of this match will be pitted against @Kidzin in the final "No Loss" match.
Round Ten "One Loss" Match Host Responsibility is the Bottom Player in each Tournament Bracket.
Round Eleven "One Loss" Match Host Responsibility is the Bottom Player in each Tournament Bracket.
After the Tournament Finals match-up is set, I will randomly assign Host Responsibility.
If any problems or questions arise, please contact me at the earliest possible opportunity. I can not work to resolve specific problems and questions if I don't know about them. : )
And as a precious touchstone of our tournament, please review:
TOURNAMENT CONSIDERATIONS (derivative of):
1.) Please treat everyone with respect. This is a game.
2.) Please be responsible for your actions and words. This is a game.
3.) Please be welcoming and keep it considerate. This is a game.
4.) Have fun and be kind to one another! This is a FUN game.
5.) If within a week, you and your Bracket Opponent can not come to match resolution. Please decide between yourselves which will move on to the next Round and submit the appropriate Challonge.com input.
And as ever, good luck and good BATTLETECH gaming! :bow:
177 of a possible 180 (or 181) total matches have been resolved.
Just two matches remain prior to the Tournament Finals.
Given the advanced nature of our tournament, only with great reluctance and repeated opportunities for resolution will I now be adjudicating matches.
Our “No Loss” Bracket Champion has been recognized. Congratulations to @WilliamVonBillhelmHelmet on his remarkable and unbroken series of Victories. :bow:
Only two "No Loss" matches remain. This week's match will see @Anaro Sunfire facing off against @Zakhodit. This match should be resolved prior to noon (Pacific Time) on Friday, 24 August, though an extension is possible given that last week's match delayed the start of your Tournament Window. The winner of this match will be pitted against @Kidzin in the final "No Loss" match.
Round Ten "One Loss" Match Host Responsibility is the Bottom Player in each Tournament Bracket.
Round Eleven "One Loss" Match Host Responsibility is the Bottom Player in each Tournament Bracket.
After the Tournament Finals match-up is set, I will randomly assign Host Responsibility.
If any problems or questions arise, please contact me at the earliest possible opportunity. I can not work to resolve specific problems and questions if I don't know about them. : )
And as a precious touchstone of our tournament, please review:
TOURNAMENT CONSIDERATIONS (derivative of):
1.) Please treat everyone with respect. This is a game.
2.) Please be responsible for your actions and words. This is a game.
3.) Please be welcoming and keep it considerate. This is a game.
4.) Have fun and be kind to one another! This is a FUN game.
5.) If within a week, you and your Bracket Opponent can not come to match resolution. Please decide between yourselves which will move on to the next Round and submit the appropriate Challonge.com input.
And as ever, good luck and good BATTLETECH gaming! :bow:
@Anaro Sunfire and I played our match. We played a 40 minute match that was cut off by comstar. We had traded long range shots but no mechs destroyed.
We both made a donation to the word of Blake fund and started again.
This was a much more intense fight
https://m.twitch.tv/videos/301908065
This battle could have gone either way. If @Anaro Sunfire and I played 10 times it could easily result in 5-5.
I look forward to playing @Anaro Sunfire in future tournaments!
We both made a donation to the word of Blake fund and started again.
This was a much more intense fight
https://m.twitch.tv/videos/301908065
This battle could have gone either way. If @Anaro Sunfire and I played 10 times it could easily result in 5-5.
I look forward to playing @Anaro Sunfire in future tournaments!
@Zakhodit, thank you for recording and posting your match with @Anaro Sunfire. Such high level gameplay offers a clinic for gamers new to BATTLETECH. It also offers gamers like myself, an opportunity just to sit back and watch the Big and Stompy magic happen. : )
Great match! And congratulation to you both in have progressed so very far in the tournament. :bow:
Great match! And congratulation to you both in have progressed so very far in the tournament. :bow: