Running the Stars

Certain things are important to note for future courses of action.
1. Decision making algorithem needs certain levels of inputs before it can properly advise on a certain course of action. This is important in helping manage group dynamics and “team building” when the captain desires to know a particular consensus.

2. Let the Squib bargain. Generally she would normally but I have grown to see the advantages of letting her do so. The machine in which I currently am typing on is a prime example of this.

3. Insectoids don’t like torches.

Landing on whatever planet to deliver our non-technical cargo, I was dismayed to discover that the planet lacked a certain level of technical aptitude. Simply put, the things they considered technical supply stores were equivalent to hobby shops. The point of contact was found for delivering the wet ware we hauled, and the Squib set to bargaining quite splendidly for some new technical equipment, since we really weren’t in the market for a slave. So in return for the ownership of one of the passenger/cargo pieces we were traded a portable computer. With the upgraded 2d processor model I consider this a trade in our favor.

Somewhere along the dull surface, the captain and his Twi’lek consort- who- is- still- mad- at- me- in- the- most- irrational- sense- for- doing- what- was- clearly- logical happened upon a group of hive minded insectoids looking for transport. The captain took this job and then proceeded to plot us a course to an even more dismal planet. Apparently these creatures breed quite rapidly and their technical level has been kept low for fear of them spreading. This of course, was easily understood when you could see the ground shift visibly as we were landing. That many bugs was rather disheartening.

The creatures (I really should jot down species designations but sometimes there are just too many syllables to remember correctly) humorously took us to their leader. Another job was offered, this one right up the blaster jockey’s line of approval (though oddly enough, BJ#1, the bounty hunter, was not interested in the bounty. #2 wanted more data). The captain curiously wanted group input for decision making. I found this rather shocking and altogether unnerving. Once again I noticed that forming a consensus was being done arbitrarilly based off of feelings and illogical inputs. I deemed to computate the proper course of action (a program I hope to refine as I go to be a compass for our crew in times like this in the future, even if such decision might be about which cheese to purchase for food stores). Sadly, the communication skills of the hive mind was not quite compatible so that the program, though leaning towards one decision, could not give me 100% reliability without further inputs. We agreed to gain further data.

Data gathering was somewhat problematic as once we found the corret subjects, they refused to answer the parameters of the questions and then became violent. Which I think means we took the job. After some rather horrendous displays of hand to blaster combat, we happened open some fine examples of technical marvels, which I then had to hide behind due to the firing of blasters by persons not of our crew. Log to be continued after I patch a door servo…

Observations:
Captain: Seems to consider there is a “morally” right way of thinking though I have yet to see a scientific or mathematic proof regarding this outlook. Emotionally driven in this regard. Could lead to unwanted situations as he guides ship and crew to needless confrontations.

Twi’lek: Needs proper armaments, especially since the Squib and I procured her taser for our security systems.

Blaster Jockeys: at last, discernable inputs. #1 seems to be a form of bounty hunter, though curious to what qualifies as a bounty of interest as he was interested in passing up the one given by the insectoids. May hold same issue as captain in that regard. Further analysis is required. #2 seems to have gun envy (pistol rather than rifle) but carries himself somewhat differently. From mutterings it may be discerned that he is a pilot of one of those small and highly vulnerable style crafts. Observation still required by finally distinctions are noted.

Squib- Most ingenious technician with a flare for creativity. I feel I have found a like mind at last.

3M- Still a solid crew member whose attitudes are easily observable. Why do some of the others speak of him as if he were a simple machine, clearly such a droid is more artwork than that. Alas the common folk know nothing of the technical arts.

No new leads. The vermin are well hidden. No bounty on us in particular for whatever trouble cooked up when I was stuck in the Medical Hold.

At the bounty hunter’s guild, there was a bounty in another system that might be valuable.. Will have to check on that after the social event.

The Twi’lek appears to have a bounty all her own from a group called The Order the new guy drugged her as we were trying to convince her to play bait to find out about these guys. We still went along with the plan but I will have to watch what I say around him. I may need to introduce him to a blaster bolt if he continues in this mode. The Order’s men sabotaged a local platform with some bad programming. We investigated, but nearly managed to fall out of the sky instead. Who ever this group is they were well equipped with plenty of resources and no qualms about killing innocents to get their job done.

The issue seems to have begun when some of the crew came in discussing an issue. The twi’lek was injured from some scuffle and one of the two blaster jockies as well. After patching up the twi’lek I was handed a data pad to access and obtain information from. The security protocols were rather rudimentary (sadly as was the equipment, I really must get my hands on some better parts but our cargo is organic rather than technical, sigh). Regardless, the datapad indicated the twi’lek had a bounty on her head, which seemed to be the cause of the trouble that was encountered off ship.

Some discussion ensued which devolved into general arguing. The rational solution that the blaster jockies and the twi’lek seemed to be dancing around was simply going to the location to collect on said bounty to obtain further information. I had faith that my companions would come to this conclussion shortly and thus instructed the medpac i had equipped the twi’lek with for her injuries to render a mild sedative to put her out for a while, thus to facilitate the plan I assumed the crew was already planning. This engendered further discourse.

We had to obtain a skiv and then set of for the coordinates given in the data pad. By we, I mean to indicate the two blaster jockies, the sedated twi’lek, and 3M. I noted later as we were approaching the destiantion that I miscalcuted the length of the journey as the twi’lek awoke early. Proper route planning is therefore essential for any later excursions like this one. The oversight seems to not have mattered as the platform was deserted. Well, exterminated perhaps would be the more appropriate term. Upon investigation (and the recovery of some useful tools that had been scattered about) the platform had been hit with a rather serious computer virus. 3M, myself and blaster jockey 1 departed the skiv and went to investigate the nearby surrounds while the twi’lek (who seemed to be experiencing an undo level of psychological issues at the time) and blaster jockey 2 stayed aboard the skiv. Upon investigation of the local factory setting, we discovered the corpses of the local workers (died of asyphixiation) and going through computer records, discovered that the platform had been sabatoged by a series of R2 astromech units. There were some men in nondescript uniforms who stated some information that was of a seemingly usefal nature that was later relayed to the twi’lek. Then the platform started to lurch as its propulsion systems failed and we left.

Findings: The twi’lek is being pursued by an organization for unknown reasons. Will have to review other crew logs for the name as it slips past me presently. Said group is particularly goal oriented (enough to murder an entire platform of people) however their execution of plans is somewhat shoddy (missed stopping all astromechs from completely destroying platform before objectives met).

Observations: The twi’lek seems agitated about the course of action taken despite the logical outcomes and information gain. Apparently she prefered the relative ignorance she was in previously. Curious but in perhaps a sad way. I do not see how further actions to alleviate the situation are made better by a fundamental lack of givens. However, it may be best to avoid for some time.

3M continues to be a marvel. Clearly the exterior shell of the protocol droid is merely a ruse. I am curious as to his make and model. If I can obtain the right parts I would like to speak with the squip and 3M to see if we might be able to improve his targeting programs. Aside of the squib, he is the only crew member who seems to make a modicum of sense on this ship.

Excursions with blaster jockeys has yet to give me substantive information to clearly define one from the other (aside of the general outward appearance of course). Standard procedure for social protocols seems reasonable until distinct social patterns emerge. Note: so far, neither seems to appreciate research.

A blog for your campaign

While the wiki is great for organizing your campaign world, it’s not the best way to chronicle your adventures. For that purpose, you need a blog!

The Adventure Log will allow you to chronologically order the happenings of your campaign. It serves as the record of what has passed. After each gaming session, come to the Adventure Log and write up what happened. In time, it will grow into a great story!

Best of all, each Adventure Log post is also a wiki page! You can link back and forth with your wiki, characters, and so forth as you wish.

One final tip: Before you jump in and try to write up the entire history for your campaign, take a deep breath. Rather than spending days writing and getting exhausted, I would suggest writing a quick “Story So Far” with only a summary. Then, get back to gaming! Grow your Adventure Log over time, rather than all at once.