Revision as of 13:46, 21 January 2013

CHIEF
Just remember, firearms are your friends!
Age	35-40
Species	Military Program
Sex	Neuter (Appears Male)
Height	6'3"
Weight	Undefined
Background
Series	Tron
Combat Styles	BFG.EXE
Hometown	F-117 Computer System
Group	Unaffiliated
Occupation/Job	Instrument of Destruction
Force:	Forces of Ruin
Theme Song	Godsmack - I Stand Alone
Quote
Users are in love with war, after all, why would else would the make me?!
Recent Events
Doing as he so wishes~

Profile

Central Handler Intelligence for Extreme Firepower aka CHIEF is a rogue military program who has been over his lifetime repurposed for several jobs ranging from targeting computers, drone interfaces, and weapon systems. His code has been altered over time and time again, until during a classified project he broke free from user control. CHIEF is very aware of the users, however unlike many programs, he has no love for the users and sees them like a virus. For the most part CHIEF does as he wishes and refuses to take orders from anyone. He is a wild-card in the deck and prefers to stay as such. Living his rogue life carrying out his own desires, whatever purpose these desires may be.

History

CHIEF was created by the military for the use in the F-117. His job was to aid the users in interacting with the targeting computer. His job was to make sure that targets lined up and that the weapons made it to their location. If the user wanted something hit, he would make sure it would be lined up to hit that spot dead on.

Later in time, his code was removed from the system and repurposed for the use in a project known as "Star Wars". His job there was to then aid the system in knowing what was a 'friendly' target and what was a 'foe'. If it was a 'foe', it was to be lined up on from space and taken down with extreme force. However though his side of things were going smoothly, the project was canceled and CHIEF once more found himself being repurposed yet again for other jobs starting down the line with combat UAVs. He was moved from drone system to drone system. Acting as the interface between the user and their drone weapons of war in the skies.

The final straw came with another, final, repurpose. This time with a classified project dealing with a ground combat drone vehicle. With so many years of the same game, being it weapons, targeting, or interfacing, he was growing tired of constantly being altered and himself pulled apart by the very users who made him; so now he planned to have the tables turned. To make them feel his pain. During the test, things went horribly wrong as CHIEF went rogue. The very drone turned on the humans, with CHIEF unleashing everything the drone had upon them.

Though the system was killed, he himself was not so easily destroyed. Instead CHIEF made his way onto the Grid with personal attentions on his mind, because the rogue program had heard from those in his area of an interesting rumor. That the MCP of ENCOM had pulled a 'user' into the Grid. So to this little Rogue's mind, that if a user can be pulled into the Grid, then a program can escape, and CHIEF now has ever plan of finding out /how/ to do this very thing.

After all, military was in his code and nothing was going to stop his path of destruction to bring the war right back at those who made him. After all in the end of the day, who really made who?

Now on the Grid, CHIEF has found himself on many cases working alone. He has no interest in what the MCP has planned or anyone for that matter. Anyone who attempts to apprehend him, finds themselves quickly placed into a matter of choice of weather to run while be shot at or just be flat shot down. Heartless have become fun targeting practice and the bigger they are, the more CHIEF has found himself coming up with bigger and better ways of handling them.

The other thing CHIEF has become known for outside of his wild manners, is the fact that if any program speaks highly of a user in his presence, he nearly turns the weapon on their face and if he expects them to be a user, he becomes extremely hostile; even to extremely dangerous. For anyone who then attempts to protect the program that CHIEF has marked as a target, he makes it also his business to take them down as well.

These actions, he knows, has given him an extremely bad reputation with the lower end of the slums of data. The Killer of Users and those who favor them. This means such higher end programs like TRON, would also be on his hit list if he was to run into the user-loving program.

So this also leaves the question of what does he really think of someone like the MCP? The head computer who is trying to rule over the Grid he is walking on? Honestly CHIEF doesn't even care about him. He knows the MCP may have been responsible for bring a 'User' onto the grid by the rumors, but he also knows that if he was to even work with the MCP there was a strong possibility that the MCP would call the shots; hold his 'leash'. That is something CHIEF refuses to have happen; Not again.

No, CHIEF likes to remain a wild card on the Grid and with these heartless wondering about, he knows he is growing closer and closer to finding his own way out eventually. Just it takes time, patience, and little bit of 'fun' along the way. Perhaps even overriding a few 'jobs' from other systems to get the answers he seeks and exterminating a few programs along the way that get IN his way.

After all, all in the line of work to the mind of CHIEF is his ever driving mad goal.

Making the users know his pain. One piece at a time.

This has lead CHIEF to at last finding the access outside of the Grid, he quickly came to learn that the rules change a little while outside. He can't escape easily, the form of body is like his own by has some minor limitations, and the Users are indeed everywhere the eye can see. With this knowledge in Mind, CHIEF started to construct ideas and plans on how to handle the users with plans to strike at any locations of interest, weapons facilities, and items that are needed either for shelter, food, or medical.

Though he has yet to carry out any of these plans and he tends to keep himself hidden away by staying either up high or in the shadows. He now knows the users faces, he knows how they live, and he plans to exploit their world in every fashion he can until he thirst is satisfied.

CHIEF for the most part can be found staying within the Grid while he continues to work out his plans and concepts of operations. Including researching into how to get his hands on more firepower in order to carry out the operations he wishes to handle. After all, he knows how weapons operate. He knows the command lines required to make such things function. All he really needs is just the Instruments of Destruction to do his bidding.

After all, what is the fun of all those war-toys, if you can't play with them yourself from time to time.

Programmers

CHIEF has had six known programmers over his time. These individuals are perhaps the very cause of why this program is nutter than a loon and the very cause of his disdain for anything or anyone who isn't a program themselves. Most information regarding these people should be known for OOC reasons, however some key individuals may know this for IC reasons. If you believe your character should know this information icly, please speak to me first and we can go over some stuff.

Original Programmer

Name: Douglas Brier
Original Age During Project: 34(Left military in his mid 40s)
Current Status: Unknown
History: Douglas Brier was one of the computer programers for the Airforce who was in charge of the original code that was installed and used for the F-117 as part of the targeting interface. He called the program CHIEF as a bit of a joke really, mostly due to the fact he and his commander never saw eye to eye on things. He even figured out to make CHIEF actually mean something to only further his argument of the name. However when the F-117 was cancelled all his information regarding the project was stripped from him and he was assigned to a new project with that information. This also lead to him having to work with a younger program on what would be called the Star Wars project. Though Douglas did try to argue the fact that uploading CHIEF for the use of guiding a laser could be done, but it require altering some of the parameters and he wasn't sure how well the code would accept this; The young programmer believed he had a solution for this problem..

This solution lead to an argument between the two programmers and Douglas was removed from the project and not shortly after left the military. No one has heard from Douglas since and all his data regarding CHIEF was left in the military's hands along with the younger programmer.

Star Wars Project

Name:Alex Fox
Original Age During Project: 23
Current Status: Deceased
History: Alex Fox was a rather young programmer and top of his class when it came to the engineer and software department. He was brought onto the Star Wars project to work along side Douglas Brier, a man Alex knew had a great deal of reputation in his day for being the best software fixer and maker. A man Alex silently wanted to do better than. When CHIEF was assigned to him along with Douglas, Alex noted Douglas' concerns and in examining the code found how they could make CHIEF not only work well with the laser system but improve the programs calculations performances, along with response time.

This alterations though would me going in, removing some aspects of the original code, rewriting some segments, and installing new code. Douglas was concerned that such a thing could disrupt the original code and cause not only wasted resource time, but could even create process loops. Instead of taking Douglas concerns into mind, Alex went ahead and made the alterations, which proved to work perfectly...

..or perfectly enough. However Douglas was furious when these changes were made and did find places where spots of the code were wasted. This lead the two into a massive argument, and shortly after Douglas was removed from the project because far as anyone else could see, Alex as in the right. The new changes speed up CHIEF's performance and any 'bugs' in the new code be corrected with time. Such things however were over looked as the project was canned and it was not until prototype aerial drones came into the scene did CHIEF resurface once more into the hands of another programmer.

Prototype Aerial Drones

Name:Carol Dorry
Original Age During Project: 32
Current Status: Retired
History: Carol Dorry was one of the very few female progammers for the new prototype Predator drones. The military was having trouble getting the drones to lock onto proper targets, so they pulled out the old Star Wars Project interface; CHIEF; for this purpose. Carol was given the responsibility of not only updating CHIEF to the new system, but also to resetting his systems to handle the sky once more.

Carol was able to find a few of the bugs and repair some of the 'broken' lines, but she found updating the old program was not an easy thing to do. Once she was able to update his code, he was then placed into the prototype drones. Only to find at times, that sometimes there was still a few errors of getting him to locate particular targets. Which meant she had to go back in and build complete new lines; something she was trying to avoid doing much of in fear of breaking something.

In the end, everything looked like it worked and CHIEF helped bring the drones from Prototype stage into real flight as the very tool that allowed the users to find targets, lock onto them, and zoom in for intel gathering. Though this would be improved upon for much darker uses...

Aerial Drones Era

Name: Conner Jackson
Original Age During Project: 26
Current Status: Still in the Airforce
History: Conner Jackson was placed in charge of CHIEF's programming upgrades and calibrations after Carol Dorry. He did not play much of a part of the programs life, as his job was rather easy thanks to Carol's work. However the few things that Conner did alter was speed up CHIEF's ability to process the incoming data and increase the AI in order for CHIEF to locate things without the aid of the user so much, taking him slowly from an interface tool to being one that could almost 'think' on his own.

Including getting CHIEF's targeting knowledge on how to respond to specific shapes of interest and then ability to know some differences on what was a threat and what was not a threat. This was then used when Aerial Drones went from spy fliers to being used as missile firing tools. This is where Conner's alterations started to shine giving this interface now a 99% chance to not only hit dead on, but also locate priority targets to fire upon, by either doing a direct lock-on or showing them marked for the user to determine which one they wanted first and telling CHIEF which to go for first, second, and so on.

Such progression in the program soon got the attention of the Army and CHIEF moved from the hands of the Airforce, over to the Army for use in a new type of project. A project that would soon bring CHIEF closer to the breaking point.

Prototype Ground Units

Name: Ray Smith
Original Age During Project: 25
Current Status: Honorably Discharged
History: Ray Smith was another young progammer that got the responsibility to take CHIEF's progamming from working with the air to working with the ground. The over-haul took a great deal out of the young programmer from very long, frustrating nights to even longer days. To get a program to work on not only acquiring targets for investigation from the ground's point of view, but how to deal with terrain, and when to avoid a dangerous situation, if determine if it was even dangerous at all.

Such purpose was first used in locating hidden weapons in buildings, locating mines in the ground, even to trap wires with the aid of user interface, before then setting it up from a learning behavior to turning CHIEF free at times to use what the program had learned. The time paid off though and with the help of a few other programmers (including some old friends off base), Ray was able to get CHIEF to make the dead-line, if not even before.

Though everything was working beautifully, his code was rushed. Those rushed processes and broken sections would lead up into the end game for the next programmer who took CHIEF to the next stage. From a ground unit that aid not only locate hidden threats, but now could 'aid' in defending troops.

Classified Tank Project

Name:
Original Age:
Current Status:
History:

Relationship Chart

Soundtrack

Logs

Cutscenes