How long do you usually write?
Several paragraphs
Do you enjoy writing collaborative posts for things like conversations, combat, etc.?
Mainly collabarative posts with much character development.
Is grammar and depth of writing important to you?
Yes
Are there any writing subjects you particularly enjoy exploring?
I generally like all forms of writing, though I do enjoy action and myster the most.
Is there anything you really dislike and want to avoid like the plague?
Nope.
Is there something you are uncomfortable with happening to your character?
This is a droid character, and a secondary character to me at that, i do not particularly care for what happens to it. Even if it dies, though I would dislike that.
Do you have any short-term or long-term goals with this character?
The only real short-term goal I have for this character to have fun as a threat to anyone who wants to go against Khulbe the Hutt or for the droid to gain its freedom. If I were to formulate some long-term goal for this character, it would probably be to make the droid into a crime lord.
Now that would be fun.
Several paragraphs
Do you enjoy writing collaborative posts for things like conversations, combat, etc.?
Mainly collabarative posts with much character development.
Is grammar and depth of writing important to you?
Yes
Are there any writing subjects you particularly enjoy exploring?
I generally like all forms of writing, though I do enjoy action and myster the most.
Is there anything you really dislike and want to avoid like the plague?
Nope.
Is there something you are uncomfortable with happening to your character?
This is a droid character, and a secondary character to me at that, i do not particularly care for what happens to it. Even if it dies, though I would dislike that.
Do you have any short-term or long-term goals with this character?
The only real short-term goal I have for this character to have fun as a threat to anyone who wants to go against Khulbe the Hutt or for the droid to gain its freedom. If I were to formulate some long-term goal for this character, it would probably be to make the droid into a crime lord.
Now that would be fun.
Identification: ATD-170a
Series: ATD
World of assembly: Lothal
Age: 5
Degree: First
Purpose: Tactical Droid - develop strategies against the master’s enemies and employ them with effectiveness and efficiency within acceptable parameters.
Current Owner:
Khulbe the Hutt
Previous owner(s):
Imperial Officer Ethsam Daniot
Current Owner Affiliations:
The Salias Hotel Group
Spice smuggling operations and mines on Kessel
The High Cronin Consortium
Restraining bolt: Present
Series: ATD
World of assembly: Lothal
Age: 5
Degree: First
Purpose: Tactical Droid - develop strategies against the master’s enemies and employ them with effectiveness and efficiency within acceptable parameters.
Current Owner:
Khulbe the Hutt
Previous owner(s):
Imperial Officer Ethsam Daniot
Current Owner Affiliations:
The Salias Hotel Group
Spice smuggling operations and mines on Kessel
The High Cronin Consortium
Restraining bolt: Present
Short description of the droid.
ATD-170a stands seven feet tall, clad in gray durasteel plating that covers its upper torso, feet, and hands. It is built to be rather bulky, being an intimidating android to organics and to resemble a cruel leader who stands above its underlings. Its head is built to resemble an Imperial soldier’s helmet with three, front-facing, red optical sensors. A small antenna, of roughly five inches, moves upward on the right side of its head and constantly feeds it new information from other devices that it may uplink with, such as basic battle droids to get consistent reports. The upper torso as well resembles a soldier with redundant pauldrons that add to the factor of intimidation.
Details on programmed features.
Battlefield Analysis
ATD-170a is programmed to run simulations on all possibilities of a battle and calculate which strategy would be most effective to dispose of threats to both the unit and the master, whether it is a grand operation or a skirmish, ATD-170a is programmed to find the most optimal way to achieve the goals as per the master’s wishes. Often these parameters are set beforehand, allowing ATD-170a to be sure what the best course of action is, rather than merely killing all resistance on sight.
Ship-to-ship combat
This droid can also serve as commander of naval forces, having extensive knowledge of ship formations and weaponry. ATD-170a can form an effective counter-measure to most other attacks and will counter-attack should it prove advantageous to do so, and will even retreat should the battle be proving too costly with given resources. With that said, ATD-170a is no pilot and attempts to fly a ship is likely to be poor unless further expanded upon in its programming.
Droid Uplink
ATD-170a can operate as a mobile command platform which can operate droids outside of the primary platform, however, there is a limitation to this operation to reduce the chances of rebellion. This limitation is that not only can the primary chassis not move, but any droids that it uplinks with is also merely used for sight and rapid report from the battlefield, rather than needing surveillance provided to it. This is not a program that cannot be taken out, being encoded into the droid’s behavior directly, additionally, any droid that is uplinked to the ATD-170a must be uplinked prior to deployment.
Light Weaponry Understanding
This droid is programmed with a basic understanding of how to use blaster pistols in the need of self-defense, however, weapons outside of those parameters are incapable of being operated upon by ATD-170a unless further data is uploaded while the droid is powered down. Additionally, while it may possess an understanding of how to use blaster pistols, that does not necessarily mean the droid is very effective in using them. Out of every ten shots, it has been noted that only 30% will successfully disable an opponent, though as this droid is not meant for frontline combat, it has not been improved upon.
Description of all installed hardware modules.
Advanced Processing Unit
ATD-170a is able to process vast amounts of information in a very timely manner, allowing it to adapt to changes to enemy stratagem in kind. This allows ATD-170a to continue its primary directive as a Tactical Droid very effectively, being able to cope with unpredictability from organics better than most other modern tactical droids.
Language Synthesizer
ATD-170a, being installed with this hardware, allows it to speak outside of Binary, and understand languages outside of it. Of course, these languages need to be uploaded to ATD-170a. The current list languages programmed into ATD-170a is Binary, Basic, and Huttese. Any language outside of the programmed list is gibberish, which makes getting information past this unit easy if it is written in a foreign language.
Communications Antenna
This antenna allows ATD-170a to communicate with others on an encoded, or open, frequency. Additionally, it is this antenna that allows ATD-170a to achieve an uplink with another droid in its internal network of uplinked chassis. Should this antenna be lost, the function cannot be regained until repaired, although this does not hamper the droid’s ability to operate.
Equipment not permanently attached to Chassis/limbs.
A single CZX-4 Blaster pistol
Personality analysis and details on memory wipe patterns.
ATD-170a shows very little in terms of personality outside of its deployment of overtly brutal tactics in a bid to achieve its goals in a timely and efficient manner, despite constant attempts to edit out such behavior by Imperial specialists, it seems that such brutality was merely a part of the design in a primary function to carry out objectives. Additionally, despite being a droid, ATD-170a will develop a personality to ignore organic orders from lower soldiers and will only expressly follow orders from other officers or superiors. Whether this be a part of arrogance or it's learning military command structure is up for debate, only a consistent memory wipe routine can negate this. As for another personality trait that is developed is an increasing distaste of basic droids, whether they be labor or, more commonly, battle droids. ATD-170a regards basic battle droids so poorly due to the mere fact that they generally cannot cope with the constantly changing nature of a battlefield, leading to an occasional requisition of organic supplementary troops.
If there is another facet of this droid that is not to be ignored that, without regular memory wipes, ATD-170a will becoming increasingly selfish and will develop its own goals. It will plan meticulously just as it does when deployed into battle, and whether or not it will carry its plans out with such effectiveness is yet to be seen due to the consistent memory wipes. As such, any owner of this droid must pay close attention to what ATD-170a is doing to catch any attempts to formulate plans outside of what it is designed for and act independently.
It is advised that memory wipe be conducted at least every month in order for ATD-170 to not develop these traits, which it will rather quickly compared to other droids.
Modifications from base model.
N/A
Uses for which the droid is of limited or no use, as well as design errors.
This droid is not a frontline soldier and will typically perform with very low effectiveness as such, despite an overly tactical program. Additionally, despite the durasteel armor, the ATD series is very weak and has several exposed areas that will disable it, namely the head and an exposed lower 'spine'. In other uses, the droid is not meant to repair ships, slice systems, or do anything outside tactically analyzing a battlefield as it is merely not programmed to carry out such functions, nor does it have the proper hardware to do so.
Purpose for droid.
The purpose of ATD-170a is simply to aid in tactical deployment and maneuvering of ground forces, as well as naval forces in order to produce a favorable outcome in a decisive battle. Additionally, ATD-170a is meant as a mobile command unit for battle droids, as well as a rapid report unit on the state of the battlefield should it be uplinked with said droids.
Past achievements.
- Successful in numerous deployments against pirate raid against Imperial supply ships.
- Successful decisive victory against small smuggling ring aboard Junkfort Station.Past failures.
- Failure to save an Imperial Frigate from destruction.
- Capture by Cartel forces.
Being constructed shortly after the Treaty of Coruscant, Imperial command initially did not know what to do with this droid as there was no war for it to fight. As such, for the first two years of ATD-170a's life span, it was put into storage until an Imperial Captain aboard the Imperial Frigate The Gate Crasher, requisitioned the droid to aid in patrols where pirates had begun to run rampant, growing bolder in their attempts to raid Imperial convoys and supply routes. This captain, Ethsam Daniat, received ATD-170a only two days before the frigate was summoned to defend an Imperial supply ship that had come under attack by pirate raiders. As such, ATD-170a had begun to do what it was programmed for, to offer battlefield analysis and advice for the captain and his ship.
The skirmish lasted only for half an hour, ATD-170a finding flaws in the pirate formation and exploiting those weaknesses to cause a route of the two pirate vessels, leaving any who had made it onto the supply ships to their doom. The survivors attempted to hold out in the reactor, however, ATD-170a was able to advise a swift deployment of soldiers from all sides to overwhelm the pirates. However, Ethsam did not take this advice, instead bargaining with the pirates and costing the Sith Empire more in terms of precious resources in time to evacuate these survivors rather than simply killing them. When ATD-170a had expressed a dislike towards this action, it had its memory wiped and deployed once more to aid in the destruction of pirates that plagued the Junkfort System. It was this same pattern over and over again, merely destroying pirates and having a memory wipe everytime its plans were ignored in the favor of ethical treatment that gained the Empire nothing.
Yet, after two years of continued service proved to hamper pirate activity throughout the system until it boiled over into a skirmish aboard Junkfort Station, notable for its smuggling activity. Being within Imperial space, such illegal activity was against protocol and ATD-170a took it upon itself to deal with a small ring that had recently come through. The droid deployed what battledroids it could and before the smugglers knew it, they were in a firefight against imperial forces. The smugglers were caught by surprise, never having dealt with imperial droids before, and not knowing that the tactics they were using were advanced for a small security force. These smugglers had no chance of survival, being destroyed without a second thought and not allowed any survivors, such was the brutality of ATD-170a.
Being against protocal, Ethsam had no choice but to increase the frequency of the memory wipes so the droid would not act out of line again. This would lead to a drop in efficiency, not being able to learn from tactical blunders or utilize what tactics had the highest efficiency against these pirates. It was in this time that a disasterous turn happened upon the Imperial Frigate, being ambushed by pirates who had better equipment than those that had been previously faced. ATD-170a did its best to offer what tactical advice it could, but the entire command was in chaos, eventually leading to a boarding of the ship. In that moment, ATD-170a took control of what it could before ordering all hands evacuate and that the ship was being scuttled to prevent it falling into pirate hands. This led to mass casualities of the crew as they attempted to reach the escape pods and other shuttles, leaving ATD-170a as the remaining crew of the ship, hidden behind bulk-head doors in the bridge.
This did not stop the pirates from slicing through the door controls, and while ATD-170a attempted to put up a rather lackluster fight against the pirates. Only killing one of them, even after firing indiscriminately, before being restrained and turned off, though not before registering an insignia matching a Hutt Crime Lord. When it had been reactived, ATD-170a had been reprogrammed to see these pirates as allies, though also programmed to see Khulbe the Hutt as its designated owner. The droid was offered as gift to the Crime Lord, a repayment of some debt only for them to be killed and ATD-170a to be taken anyways.
As such, the droid was deignated as a Security Officer to other droids, and to guard the many slave girls of the Hutt. That is it's current job, to keep any would be thief from taking the rightful property of Khulbe the Hutt.
The skirmish lasted only for half an hour, ATD-170a finding flaws in the pirate formation and exploiting those weaknesses to cause a route of the two pirate vessels, leaving any who had made it onto the supply ships to their doom. The survivors attempted to hold out in the reactor, however, ATD-170a was able to advise a swift deployment of soldiers from all sides to overwhelm the pirates. However, Ethsam did not take this advice, instead bargaining with the pirates and costing the Sith Empire more in terms of precious resources in time to evacuate these survivors rather than simply killing them. When ATD-170a had expressed a dislike towards this action, it had its memory wiped and deployed once more to aid in the destruction of pirates that plagued the Junkfort System. It was this same pattern over and over again, merely destroying pirates and having a memory wipe everytime its plans were ignored in the favor of ethical treatment that gained the Empire nothing.
Yet, after two years of continued service proved to hamper pirate activity throughout the system until it boiled over into a skirmish aboard Junkfort Station, notable for its smuggling activity. Being within Imperial space, such illegal activity was against protocol and ATD-170a took it upon itself to deal with a small ring that had recently come through. The droid deployed what battledroids it could and before the smugglers knew it, they were in a firefight against imperial forces. The smugglers were caught by surprise, never having dealt with imperial droids before, and not knowing that the tactics they were using were advanced for a small security force. These smugglers had no chance of survival, being destroyed without a second thought and not allowed any survivors, such was the brutality of ATD-170a.
Being against protocal, Ethsam had no choice but to increase the frequency of the memory wipes so the droid would not act out of line again. This would lead to a drop in efficiency, not being able to learn from tactical blunders or utilize what tactics had the highest efficiency against these pirates. It was in this time that a disasterous turn happened upon the Imperial Frigate, being ambushed by pirates who had better equipment than those that had been previously faced. ATD-170a did its best to offer what tactical advice it could, but the entire command was in chaos, eventually leading to a boarding of the ship. In that moment, ATD-170a took control of what it could before ordering all hands evacuate and that the ship was being scuttled to prevent it falling into pirate hands. This led to mass casualities of the crew as they attempted to reach the escape pods and other shuttles, leaving ATD-170a as the remaining crew of the ship, hidden behind bulk-head doors in the bridge.
This did not stop the pirates from slicing through the door controls, and while ATD-170a attempted to put up a rather lackluster fight against the pirates. Only killing one of them, even after firing indiscriminately, before being restrained and turned off, though not before registering an insignia matching a Hutt Crime Lord. When it had been reactived, ATD-170a had been reprogrammed to see these pirates as allies, though also programmed to see Khulbe the Hutt as its designated owner. The droid was offered as gift to the Crime Lord, a repayment of some debt only for them to be killed and ATD-170a to be taken anyways.
As such, the droid was deignated as a Security Officer to other droids, and to guard the many slave girls of the Hutt. That is it's current job, to keep any would be thief from taking the rightful property of Khulbe the Hutt.
Date and time of last memory wipe.
10:00 10.01.06 ATC
Link to owner data files:
Khulbe the Hutt
