Marvin

Hey, kid, happy birthday.

Great except for the following: [*]Deciding who is and who isn't "agressive enough" is a subjective decision. I think all reqirements in the match should be objective, to avoid any ... objections. [*]Halting the match to check a player's current shield and armor status is like playing roulette. Up one minute ... down the next. If you can't kill the guy in twenty minutes then, likely as not, he will kill you in twenty one. [*]There's a specific reason for restricting a match so as not to use AI fighters ... but I see no reason why we shouldn't have shuttles available to us in a one v. one. Counting what Remo suggested, the rest sounds good to me.

quote:Originally posted by Supreme Cmdr: ...not like the edge of you seat stuff you can get in BC when there a huge fleet battles going and you're down to your last shield level, out of missiles with the CE screaming about damaged systems like a banshee. Even that isn't nearly as exciting as when the guy who is eating away at your shields is ShoHashi or Chavik or ... in some cases ... Denny.

This one's on you, Chav. Good job ... to all three of you. It takes cajones to get between a cloaked carrier and his target. Nice post, too. Er, make that "two" ...

quote:Originally posted by jamotto: In fact, the one you saw at Best Buy was likely also a remake. This movie is like a second generation remake The Jimmy Stewart version is also a remake? Wow. Didn't know that ... it got big press when it came out 'cause the stunt pilot was killed while making the movie ... during a second take. Who was in the first version?

What time does it start?

Yeah. Don't you remember the part about ... uh, what was it again?

quote:Originally posted by ShoHashi: Quazar? Don't you mean Eclipse? What's worse, Sho? Me forgetting who else was at the meeting or you forgetting we talked about how my memory wasn't what it used to be (or yours, for that matter)?

quote:Originally posted by DennyMala: Is there something we that didn't attend the meeting needs to know...? Yeah. If you're still stuck trying to finish Thief 2 Quazar can help you out.

After posting the suggestion, I had a conversation with Gordon who is also working on a scenario with a "hidden" player. I then started editing Remo's "Operation Home Run" and realized that ... time-wise ... Remo had the solution first. Since it appears there will be a number of different missions using hidden players/teams, I'd suggest using the same method of inserting them in each. Getting six players into a game without restarts is complicated enough already ... no need to confuse the issue even more so.

quote:Originally posted by Freyar: ...it makes me wonder if they were partying up there or something.... Food fight?

quote:Scenario 1: The three counter agents must log in first ... and close their chat windows before the shuttle logs in. How will they know when the game starts? Try having the agent log on first, position himself accordingly, send the data to himself, then send enough "bump" messages to clear the chat window of any information telling of his position.

How about after the moderators' meeting?

If you don't watch Enterprise, you won't see what old TOS players did in their younger days. Like T'Pau, who presided (will preside, I suppose) over Spock's wedding fiasco. Next, I expect to see a young Vulcan making a name for himself in two ways: [*]1. Uncovering the Romulan plot. [*]2. Marrying an Earth woman named Amanda. If somebody else accomplishes item 1, I'll be sorely disappointed. But I'll continue to watch, nonetheless.

Okay, Remo, I've copied this one down. Let us know when you'd like to test it.

Well, Rip finally made it ... we extended the day to include a third mission. I think he enjoyed it. Chavik had to represent the Insurgents all by himself so me and Rip helped him out a bit. A bit? The Insurgents won all three matches. Ironic considering Chav spent most of the day fighting with Microsoft to stay on line.

Of course, if the kid continues to see-feel-hear-smell the ghost after Grandpa has been sold, he's gonna think Mom is really stupid ... at the very least.

This must be my day for learning new things. I previously thought a distortion field was created any time someone went into hyperspace. Or someone's ship, anyway.

Sounds like a round-about way of putting "intruders" aboard another ship to steal cargo. You learn something new all the time.

Androids instead of mechanical men? Lame.

No doubt about it.

I was in hyperspace for two full minutes and knew exactly what was gonna happen on exit. You could hear me halfway down the block.

quote:Originally posted by Zane Marlowe: I have friends who are laughing at you right now.... You mean with me, right? Anyway, now comes the disagreeable part ... a discussion on the rules for this kind of R/P activity. Remember, guys, this is just a preliminary list of rules for role-playing, MP style. Look them over and add your own thoughts, comments, and ... rules. 1. Only players who participated in the specific match can write up an AAR in role-playing format. Other than that, first come - first served. Those who come after can add to the story line. 2. The story must deal with a match already played and reflect what actually happened in that match. 3. Each player must write only about his/her own character ... in terms of thoughts, actions, and consequences. We shouldn't be trying to get into each other's heads. Include other players only when necessary and only to reflect what you actually observed. 4. No participant can be killed within another player's role-playing story line. Only the player, himself, can make that decision. Any of the kills associated with a fleet match will be attributed to a player's ship. Ways to circumvent an obvious kill include: [*]Use of escape pods. [*]Cloning of players. [*]Being, yourself, indestructible (e.g. Marvin the robot). [*]Using the transporter. [*]Giving up (not a suggested solution). The player killed will decide how to come back from the dead, so to speak. For other players who must describe the kill, refer only to the destruction of the ship. 5. No story line should contradict any previous parts of the R/P story. Which mean, if you're going to contribute to the story, you'd better read what's already been posted. 6. To make the story more interesting, certain facts can be added by senior members of the match. For example, in "Shuttle Attack," none of the shuttles have been given a particular reason for being targets; they might be hauling dangerous artifacts or an alliance dignitary might be aboard. These details could be added to give the story more depth. More interest. But such details shouldn't be included without thought to the overall picture ... else they end up restricting what comes after. Which is why a senior member should be consulted prior to adding details of this type. 7. The story line will take place in the multiplayer universe. As far as Prime Fleet is concerned, Beta Wing need not adhere to this rule so long as their R/P activities remain within the purview of Prime's role-playing structure and posted either in the Role-Playing section of 3000AD or a similar section at Prime. But, either way, stories based on MP events must take place within the MP universe. 8. NPCs, if included in a story line, must not play a major role in the outcome of any part of the story. A player can use an NPC as an excuse for poor performance but only in general terms. Additionally, if you're going to name your NPCs, give them names not used by everyone (e.g. Resnig). The original crew belong to GalCom's Supreme Commander ... the best you could expect from that group would be clones. If your ship's name is associated with a specific group of characters from a book or movie or anime, think about using them, instead. 9. Any major background story must conform to original 3000 AD "history." Again, details will usually result in a more interesting story but, because of the effect it might have on future play, get it okayed by Remo before posting it for all to read.

After Actions R/P Report. The following story is an example of kind'a how I envision role-playing to work within the confines of multiplayer. Notice two things: 1. The story deals with a match already played and reflects what actually happened in that match. 2. I deal only with my own character in terms of thoughts, actions, and consequences. We shouldn't be trying to get into each otherÔÇÖs heads. [RP] Marvin accepted the assignment with a snappy salute. Trotting toward his command craft, he mulled over the options. A shuttle had been detected in the Gaulan region and his was one of two GalCom ships assigned to destroy it. No reason. No specifics at all. Just destroy that SC. Stopping by the Alpha Wing Bar, he motioned to his navigator and combat officer, ending what would've been a winning hand of poker for an engineer from another crew. The engineer protested, demanding that at least the combat officer play out his hand. Marvin would have none of it. By the time they'd reached the boarding ramp to GCV-Asimov, her tactical officer had orders in hand and engines warmed to the ready. "Captain," she said as Marvin snatched the briefing pad, "We're low on cloaking fuel. And, if I read the mission brief correctly, we will need all we can store." Marvin ordered his poker-playing officers to make a quick detour to their quarters for a one-minute sonic shower. He then followed his tactical officer into the lift. "Make do," Marvin replied. "We don't have time to replenish our supply and, besides, we won't be the only carrier assigned to this mission." "I know that, sir. Commander Marlowe will be approaching Gaulan ... probably from a different direction. I suggest we take the direct route ... through Castrin." Propitious timing. At the moment she made that suggestion, the doors to the lift parted, depositing her and Marvin on the bridge. He nodded, saying, "When she gets to the bridge, have the navigator set course." As the Asimov departed the station, Marvin had his communications officer contact Commander Marlowe. Between the two of them, they agreed that, if they should find themselves together in Gaulan with hostiles in the area, Marlowe would attack the shuttle while Marvin kept the hostiles busy. The transition to Castrin proved uneventful, the region seemed clear of hostile targets, and so Marvin ordered a jump toward the Gaulan gate. But halfway into hyperspace, his tactical officer reported two bogeys in the vicinity of their destination. The Asimov went to combat status: missiles armed and selected, main gun on line at maximum power, jammers at the ready. "Hold off on the PTA," Marvin ordered, "We don't want to be giving away our position if we're forced to cloak." Communications flowed quickly between all GalCom ships in the immediate area. Marvin, on a secure frequency, relayed his plan to press ahead and bypass the hostile ships hovering like mosquitoes near the jumpgate. In response, Commander Marlowe indicated that he'd try to engage one or both the ships in an effort to draw fire away from Marvin. Upon exiting hyperspace, Marvin's tactical officer noted that the hostiles were not in a position to immediately endanger the Asimov. Marvin acknowledged and ordered his helmsman to continue through the gate. "Sir," his tactical officer persisted, "Might I suggest we cloak prior to reaching the gate ... in an effort to confuse the hostiles." "Probably won't work," mused Marvin, "But I think we can spare the fuel. Let's see how this thing plays out." "Uh, Captain," the communications officer added, "I think I have one of the hostiles identified. It's Dreada. He's a GalCom priority. Somebody should engage to destroy." Marvin checked the VDD. "How close to the gate are we?" he asked. "Twenty-two kilometers and closing," answered the navigator. "Keep going," Marvin insisted. "Marlowe will take care of Dreada." The Asimov pushed through into Gaulan and the tactical officer scanned for the shuttle. "I've found it, Captain. It's near the station. We'll need to go in under cloak." Marvin nodded, looking over the officer's shoulder at the VDD. "How long 'till our engines are recharged?" he asked. Before anyone could respond, Commander Marlowe's ship appeared on the TRS and a familiar voice announced he was going to take out the shuttle. Marvin analyzed the situation in an effort to assess his own options. While in the midst of his analysis, Dreada's craft appeared ... less than 20 kilometers aft of the Asimov. "Hard about," ordered Marvin. "Target and engage that hostile." "Sir, he has us at a disadvantage," admonished the tactical officer. "Okay, then cloak," replied Marvin. Rapidly, the crew of the GCV-Asimov responded to the threat. Cloak engaged. Missiles fired. Main guns brought to bear. Dreada's shields began to drop. The battle appeared to be going in favor of GalCom. Then Marlowe jumped for the shuttle. And Dreada followed Marlowe. Now, what happened next wasn't a pretty sight. At least, not for Marvin and his crew. You see, Marvin ... being a robot ... must follow his programming. And he has a very specific program for when he plans to attack either a starstation or anything in close proximity. It goes something like this: [*]0001 charge engines [*]0002 insert jump target [*]0003 engage cloaking device [*]0004 initiate jump Which is exactly what Marvin did. He checked to make certain his engines were charged ... they were. He inserted Dreada's rapidly receding ship into targeting. He engaged the cloak and then immediately initiated the jump. That's when he heard somebody say, "Cloak disengaged" ... just before he heard somebody else announce that they had entered hyperspace. "Not dis-engage cloak," he countermanded. "I said TO cloak. Cloak ON." "But sir," came the subdued reply, "We were already cloaked. When you press 'Cloak' again ... when you're already cloaked ... then you UN-cloak." One lobe of Marvin's positronic brain blew completely. One lobe went into a panic ... mentally screaming, "Nooooooo!!!" The third lobe took over and realized that, if Dreada was headed for where Marvin knew he was headed, the Asimov was gonna be in deep trouble really quick. "Attention all crewmembers," he shouted, "Everyone to the escape pods. You ... we ... have less than seventy seconds to eject from this craft." "But sir," protested his tactical officer, "We're still in hyperspace." Marvin leaped into the lift and hauled the officer in after him, insisting, "Don't contract two words when one of them is important to the sentence." His tactical officer looked at him, bewildered. So Marvin, while climbing into the last escape pod available (hey, he's the captain ... last to leave the ship), explained, "You should've said, 'We are still in hyperspace' ... the operative word being 'are' ... 'cause if we don't get out of this ship before we exit hyperspace then 'are' will be replaced with 'was' ... if you get my drift." His tactical officer didn't get Marvin's drift ... not until, safely floating in a pod about 12,000 kilometers away from the starstation where Marlowe stalked the enemy shuttle, she and Marvin watched as their beloved command craft decelerated and, targeted by the station, promptly became space rubble. ÔÇ£That,ÔÇØ Marvin explained, ÔÇ£was our ship.ÔÇØ [/RP] Something like that. In its own thread. With the R.O.E. posted at the top, as a sticky. P.S. Notice, also, that I've managed to write it so that I'm still alive.

Authorized users can log into Prime Fleet West anytime before the match to get the password. As soon as it's up, that is.