=THE NEXT ARMADA EVENT ON VASSAL= ROUND ONE... FIGHT!!!

By doobleg, in Star Wars: Armada

Hahahaha hahahaha haha! Oh gods, this is funny. Gowtah, if I wanted to say you abused Vassal I would of stated it right to you.

As a matter of fact, I allowed you to get away with several infractions such as you replacing your MC30 well after it was deployed. Which, is considered illegal.

So, honestly, if I wanted to call you out on several things, I could. Do I care? Personally, yes, but since I have been deemed "too competitive" I have to take a step back and learn to deal with it.

Like I said, I would cause you right out Gowtah if I was going to. I brought this whole situation up becuase someone I respect saw the vlog point and said that they would not of called it an overlap. That is all. You and Nebulon-B say you think it was and I have to concede that I have little experience in Vassal and will go with people's judgement who have more than I.

Go ahead and do your MS paint picture. I don't care if it was an overlap or not. I just want to learn from the situation so I can make the call on my own.

Oh, as for me, if I was to make the call. I would likely say that it was an overlap. Just like I did there. The reason being is because I could not see a corner or mat pixels on either side of the corner.

So, all in all, cool your jets Gowtah and don't accuse me of such things.

What is definite in my experience is the preciness of vasall vs the table. None of those manual operations (notching, hoovering etc), including those worn-out tools that seem to yield a bit more or less at every yaw for every player, can match the accuracy of the computer.

vasall is a great tool, and since I am at it, thx to the Armada programmers. I am certain that this is the opinion of everyone here on the Forums.

Okay, now that everyone's had their say, I'm gonna ask that this discussion come to a close.

Everyone scheduling their games okay? Matt Antilles and I are looking at playing this weekend - still hammering out the details. :)

Good luck. I will be awaiting the next round.

Ginkapo vs ItzSteve will be somewhere around 6pm GMT time. 11am PDT on Wednesday

Edited by Ginkapo

Oh, we had set the time but forgot to post it. godofcheese and I will be hitting it off on Wednesday 5 am GMT.

Ok i watched the vlog, yes the ram was very close

I went over the game with another player on here and and he had a different opinion on a ram that changed the entire game.

the problem is *YOU* agreed that it was a ram...

"Lyraeus> - I think I will overlap. . .

<Lyraeus> - or not. . . I was worried about that rock

<gowtah> - I'd say you do overlap yav though

<Lyraeus> - side arc for DAYS!

<Lyraeus> - NOOO we nick!

<Lyraeus> - darn. . . "

there is absolutely nothing that can be debated now because YOU agreed with him, if you hadn't (which you were perfectly in your rights to do) and had brought a 3rd party in to rule on it or simply rolled for it, you *Might* have grounds to stand on

as it is now you are simply Contradicting yourself...

You are missing the point. Yes I agree ld that it was a ram because I don't have the experience with Vassal you do or many others. There is also no way to be sure that it was a ram.

I am still new to Vassal so i have to take this on faith till I get the experience to know otherwise.

So it's not a question of whether or not it was my fault. I want to know if it was or was not a ram. This way I can learn for what to look for.

I don't have these issues on a table. I don't have them because I can hover the tool and get a much more accurate representation of where my ship will be. You can't do that in Vassal.

I was watching the game live, I magnified the situation (albeit not to maximum because it looked clear enough), for me the bump was evident.

I didnt review, sorry if I hurt feelings, was my objective view then.

I saw the bump also, and it was *just* touching which could be argued a touch and not an overlap under the (IMO stupid) current ramming rules. With Vassal that rule literally means are the outmost pixels next to each other or is a single pixel overlapping.. which was about the case.

For Vassal IMO it's just a ram, but that is a little different than tabletop. It's not a problem, just a minor difference to get used to.

Ok i watched the vlog, yes the ram was very close

I went over the game with another player on here and and he had a different opinion on a ram that changed the entire game.

the problem is *YOU* agreed that it was a ram...

"Lyraeus> - I think I will overlap. . .

<Lyraeus> - or not. . . I was worried about that rock

<gowtah> - I'd say you do overlap yav though

<Lyraeus> - side arc for DAYS!

<Lyraeus> - NOOO we nick!

<Lyraeus> - darn. . . "

there is absolutely nothing that can be debated now because YOU agreed with him, if you hadn't (which you were perfectly in your rights to do) and had brought a 3rd party in to rule on it or simply rolled for it, you *Might* have grounds to stand on

as it is now you are simply Contradicting yourself...

You are missing the point. Yes I agree ld that it was a ram because I don't have the experience with Vassal you do or many others. There is also no way to be sure that it was a ram.

I am still new to Vassal so i have to take this on faith till I get the experience to know otherwise.

So it's not a question of whether or not it was my fault. I want to know if it was or was not a ram. This way I can learn for what to look for.

I don't have these issues on a table. I don't have them because I can hover the tool and get a much more accurate representation of where my ship will be. You can't do that in Vassal.

I was watching the game live, I magnified the situation (albeit not to maximum because it looked clear enough), for me the bump was evident.

I didnt review, sorry if I hurt feelings, was my objective view then.

I saw the bump also, and it was *just* touching which could be argued a touch and not an overlap under the (IMO stupid) current ramming rules. With Vassal that rule literally means are the outmost pixels next to each other or is a single pixel overlapping.. which was about the case.

For Vassal IMO it's just a ram, but that is a little different than tabletop. It's not a problem, just a minor difference to get used to.

I don't see touching as an issue. In the Navy we had ships within spitting distance (the equivalent of a base contact) and we never hit each other.

In Vassal it can mess with a capacity to get into tight spaces that on a table would be no issue.

The closest I have gotten on a table has been base corner to touching the corner of a shield horn and base. It can be don't (don't recommend it often if you want to keep your sanity, and blood pressure low).

Ginkapo made a suggestion on the Vassal 2.2.X release thread for mirror matches to change the base color. It could also be a simple fix such as being able to have each player have their own colored bases. So Player 1 gets white, 2 gets black, 3 gets a dark grey and 4 gets a light grey. There would not be any questions at that point.

Guys T.o. said to stop Talking about it

Move on its over and doesn't matter

Sorry I replied to an earlier post before reading the drop-it post. No worries.

Sorry I replied to an earlier post before reading the drop-it post. No worries.

Daht was a rookie mistake.

I am here till thursday. Try the veal.

Sorry I replied to an earlier post before reading the drop-it post. No worries.

Daht was a rookie mistake.

I am here till thursday. Try the veal.

:P

JJs vs Cactusman will be starting in just under an hour!

Sorry I replied to an earlier post before reading the drop-it post. No worries.

Daht was a rookie mistake.

I am here till thursday. Try the veal.

you Really like Daht Pun don't you? :P

:lol:

JJs Juggernaut (player 2) vs thecactusman17 (player 1)

400-101 (299 MOV) win for JJs Juggernaut

Objective: Hyperspace Assault

A great game to thecactusman17. I managed to dish out large amounts of damage with my squadrons. Gallant Haven prevented most of the imperial squadrons' damage, while the A-wings dished it back with Torin Farr's help. The bombers did amazing work with Bomber Command Center keeping my squadrons from rolling any blanks. Admonition hypered in and threatened both Gozantis on turn two and Demolisher dealt a bid hit to Rieekan's Assault Frigate, forcing the brace burn. Devastator unleashed its fury on Yavaris, but Yavaris just managed to live through the volley, so it had two turns of having Luke, Wedge, and Dutch double-tap; first on Demolisher, finishing it off, and then the ISD. This and the firepower of my ships brought the ISD down at the end of turn 6, just barely killing it. Then Wedge rolled the hit/crit he needed to finish off the scatterless Vector. Leia was an absolute star here (never used her before, just didn't fit my style), but she was able to keep the squadron commands where they were needed. Lots of fun, and good game to cactusman!

Vlog posted on the other thread.

I propose a motion dahht Clontrooper is expelled from the tournament for infringement of intellectual property rights.

I propose a motion dahht Clontrooper is expelled from the tournament for infringement of intellectual property rights.

I propose that the next person to use "Daht" as a pun in this thread be stabbed.

Who's with me?

LTD vs MattShadowlord has started.... NOW!

And as Australians, we choose not to stab anyone unnecessarily.

I propose a motion dahht Clontrooper is expelled from the tournament for infringement of intellectual property rights.

Just take solace in knowing that you do it better. ;)

WhatsArmadaWithYou and Miferr scheduled for Wednesday, 6/29 at 7:00PM Central, 5:00PM Pacific, Midnight GMT.

WAWY brings a Screed DeMSU...squadron build!

Miferr brings Madine MC80 with Engine Techs, plus TRC90s!

LTD vs Matt completed, with a 249 to 0 win to me. Vlog is in the other thread.

LTD put up a good fight and certainly deserved some points from the game, but a loss of the squadron battle in the centre and his MC80 being marginalised and not getting to fire a single shot pretty much sealed the game.

Well played though LTD, better luck next time!

Ginkapo vs ItzSteve will be somewhere around 6pm GMT time. 11am PDT on Wednesday

Fast forwarding 24hours.

THIS GAME IS ON NOW!

Thats right, for all the latest interdictor vassal chat, pop on over to our chatroom NOW

Ginkapo vs ItzSteve will be somewhere around 6pm GMT time. 11am PDT on Wednesday

Fast forwarding 24hours.

THIS GAME IS ON NOW!

Thats right, for all the latest interdictor vassal chat, pop on over to our chatroom NOW

ItzSteve vs Ginkapo

Ginkapo first player, picks most wanted. Foresight and Vector.

As usual, I was outdeployed, thanks to Steves rogues this time. Admo far right, Lando far left, the other three clustered near the obstacles in the middle.

First turn Steve came out slow at speed 1. Lando and Admo began their attack runs, meaning that in turn 2 admo lined up a double arc on Demo for the next turn. A double arc that succeeded in killing Demo without using sensor teams. Its fair to say that throughout the game I rolled obscene dice, without only TRC's on Jaina and two sensor teams to aid me.

Game continued, but the loss was tough for Steve. Bright hope started messing with Ozzel and Wuluff, tractors and slicers galore, with Lando lining up at the end of the turn to double arc Ozzel. Rogues finished Tycho and started to hit Admo as Bright Hope was perfectly obscured by the station.

Lando sure enough one shots Ozzel and continues on his way. From this point Bright Hope, Jaina and Foresight taunt the remaining two ships, lining them both up for Admo kills. The Rogues struggle to deal with the two ships nearby, admonition and a station skating Bright hope.

Game ends turn 5 with a tabling.

423 to 16 points. 10-0 407 MOV.

Cheers for the game, was fun. You'll be smashing these guys in no time.

Just one week to go, people! All games must be completed by Wednesday 6th July 0001 GMT.

If you are having difficulty scheduling your game, let me know. :)