Slightly shorter than your typical Ewok, Teebu stands at just under 1 meter tall. His long fur consists of white and grey colors, with considerably grey around his eyes and he has a pronounced white beard. He has longer and more pronounced nails on his hands with sharpened edges. He is also slightly on the bulkier side compared to most Ewoks.
His arms have scars running down them from numerous cuts, some older and darker and others newer and lighter.
As Director of Tactical Engineering, Teebu understands that the military is at their best with boots on the ground and fully operational tools in hand. His designs are born from combat experience, built for practical use, and tested under fire. He is often known for cutting through red tape and delivering results long before the Brotherhood military command even finishes its review. This disregard for process often creates tensions as he tends to bypass formal approval channels, push limits without authorization, and act on instinct over instruction. While his initiative can mean the difference between victory and defeat, it also results in strained relationships, internal conflicts, and frequent disciplinary reviews. Enlisted respect his brilliance, often feeling his results justify those methods, but command continuously grows frustrated with his insubordination. In the end, he is a powerful asset whose effectiveness on the battlefield often overshadows the problems he causes.
The battlefield is often a machine. Every unit a cog, every tactic a gear, and the equipment they wield serves as the oil that feeds it. Teebu focuses on that oil, supplementing outcome predictions with crafting strategies based on engineering precision. He is invaluable in identifying inefficiencies, structural weak points, and optimizing maintenance logistics. However, this methodical mindset becomes a liability when reality fails to align with theory. He often obsesses over details, delaying missions for last-minute tweaks or arguing with Thran over minute imperfections. His need for perfection can stifle creativity and initiative in others, and sometimes he can fail to adapt efficiently when the unpredictable happens, too focused on restoring that perfection. While Teebu's clarity of vision is unparalleled, his rigidity in execution can slow down operations and frustrate command. When everything works as planned, he shines. But when things go off-script, the arguments can start to fly.
Teebu is often mistaken for being cold, analytical, or detached. He speaks in schematics and think in variables. But beneath that engineering technical demeanor is a profound care for his team. Teebu design with survival in mind, incorporating safety redundancies, escape options, and stabilization tech even when it compromises firepower. His loyalty runs deep, and he’ll risk themself to protect the Brotherhood. However, this protective instinct can manifest as overbearing control. He doesn't trust others to make the right decisions with his personal projects and often micromanages those specific projects. This undermines autonomy and creates friction when teammates discover hidden features or limitations they weren’t told about, hindering them. While Teebu believes he's safeguarding his own efficiency and perfection, others feel limited or manipulated. Balancing trust with others is a constant struggle. His heart is in the right place, but his execution can alienate the very people he works with.
Teebu treats his gear like sacred artifacts. Every scratch on a casing, every improperly stowed weapon...he notices. And he judges. Harshly. His post-mission debriefs are often lectures in field etiquette disguised as repair sessions. His passive-aggressive maintenance logs are infamous. Yet, this obsessive care means his gear almost never fails unless mistreated. He knows how every weapon ages, how each device behaves after stress, and how to extend their battlefield lifespan indefinitely. But his intolerance for “careless users” limits who gets access to his best creations. He’ll deny requests from agents he deems unworthy of his tech, or send gear that is not the best of the best. His strictness breeds resentment, but also reverence. It's well known: if Teebu gives someone something, it’s because he believes they won’t just use it…they'll respect it. And if they don’t? He might design something that teaches them a more direct lesson instead.
Teebu doesn’t just build war machines, he pilots them. His deep connection with his tech allows them to operate it with unmatched precision, pushing performance past limits others wouldn’t dare attempt. On the battlefield, he becomes a force of nature, wielding space vehicles with expert control and devastating impact. But this level of independence often isolates him from a squad. In combat, Teebu prefers to rely on themselves and their machines, sometimes ignoring orders or abandoning formation to pursue their own objectives. Maybe testing a new targeting array mid-firefight or engaging superior enemies just to see how a prototype holds up. While this self-reliance makes him deadly and unpredictable, it also undermines team cohesion. Allies never quite know what he will do next, and trust in his consistency during combat can waver. His brilliance is undeniable, but so is the danger of his unchecked autonomy in the heat of battle.
Teebu has field-tested countless inventions in the harshest combat conditions, gaining firsthand insight into their function and capability in the chaos of real warfare. His ability to adapt those system under pressure is unmatched, rerouting power, patching systems, or recalibrating a weapon while under fire. Improvisation is second nature, making him incredibly resilient in fast-changing scenarios. Yet this same tendency to innovate on the fly can backfire. He might deploy half-finished gear, overclock energy cores, or test unstable systems in the middle of missions, all in the name of data collection or proof of concept. His need to prove an idea works sometimes outweighs caution. While his battlefield creativity is legendary, it comes with potential volatility - one moment he’s saving a mission with a brilliant adjustment, the next he's causing friendly fire with a misfired prototype. To follow him into battle is to place trust in both genius and chaos.
Master (+5) | |
Adept (+4) | |
Proficient (+3) | |
Trained (+2) | |
Learned (+1) | |
Mediocre (+0) |
Master (+5) |
|
Adept (+4) |
|
Disciple (+3) |
|
Studied (+2) | |
Initiate (+1) |
Languages |
|
Lore |
|
Primary Martial Art | None |
Secondary Martial Art | None |
Primary Weapon Specialization |
Miscellaneous
(Only applies to the Weapon Specialist Discipline and/or Proficiency feat) |
Secondary Weapon Specialization |
Blasters
(Only applies to the Weapon Specialist Discipline and/or Proficiency feat) |
Primary Lightsaber Form | None |
Secondary Lightsaber Form | None |