Hold It In (RWBY/Transistor)

PsyFarrow said:

[x] It's heavy handed intervention from beyond the fourth wall inexplicably shifting the flow of the narrative. Cultures differ, but in mine, that's unspeakably gauche. And, to be clear - the DoMT has a well earned reputation as a ruiner of campaigns. No, I'll maintain my decision to leave, that much I'm sure of.

I actually kinda liked these snippets, since I figured it was Prok having trouble writing J-Crew and taking a break from it while still giving us content.

Even if that wasn't the case and I misunderstood, this has been an interesting encounter.

Click to expand...

Click to shrink...

Function Suggestions

Just fill out the form, slick.

Function Name*: self-explanatory, the more computer-y, the better.
Function Category*: Utility/Combat/Other, delete as appropriate
Function, er, Function*: What does it do on its own, what does it do as a passive, and what does it do as an upgrade to another Function? Fill out at least two.
Projected MEM Cost: Also self-explanatory, but be reasonable.
Function Discovery: This isn't strictly necessary, but if you want to put in a little note on what inspired Jaune to code this, go right ahead.

*Mandatory

This outline is subject to change, depending on what's needed, and I'll update it as necessary. All suggestions are subject to change by the QM.

The maximum number of Functions to be suggested at any one time by a person is three (3), and the max number of Functions to occupy it is a soft limit of 'as many as it takes for me to open this tab and then watch my computer burn.'

|||

Spoiler: Recursion(), Tiypo

Function Name: Recursion()
Function Category: Combat/Other
Function, er, Function:
---Stand-alone: As a stand-alone function Recursion() can only be used during a Turn(). When used a phantom copy of Jaune will be created that will repeat any functions that he does for the remainder of the Turn() at a lessened power a split second after he does. If used multiple times the first copy will make an even weaker copy when it performs Recursion(), creating a trail of Jaunes performing a flurry of weak but distracting functions. The phantom copies are fragile and an opponent sufficiently fast enough to strike one will easily break it.
---Upgrade: When used as an upgrade to another function Recursion() creates a undamaging illusionary copy of the upgraded function a split second after it is performed, attempting to trick opponents into reacting to an attack that is not coming.
---Passive: As a passive function Recursion() causes functions that are repeated to cost 1 MEM less after they are first performed.
Projected MEM Cost: Medium
Function Discovery: Recursion is often viewed as the first step into more advanced programming and a rite of passage for those learning computer science. In the process of creating the Transistor Jaune has managed to twist his mind around the bizarre behaviours of what happens when a program must create another instance of itself to complete its goals and overcome the infamous stack overflow error, where the program never stops creating copies until all available memory is used. With the memories of that indispensable but troublesome programming concept in mind, Jaune has created this function.

Spoiler: Block(), Shell(), Shield(), ConfusedPotato, QM Meddling: Mild-Middling

Function Name*: Block()
Function Category*: Combat/Other
Function, er, Function*:
Active: Creates a 1m³ invisible solid block at the desired location, can be dismissed at will. Passive: Your attacks can now be used to block other attacks.
Upgrade: turns a single target function into an AOE.
Projected MEM Cost: 3 MEM
Function Discovery: After seeing what Saff did with his maze it is rather obvious how being able to rearrange the battlefield is an advantage. Granted, one block is hardly battlefield mastery, but IT'S A START DAMMIT-

Function Name*: Shell()
Function Category*: Utility
Function, er, Function*: Acts as a one-hit shield, designed to completely block the first attack that hits it before going down, takes time to recharge, prevents surprise attacks but is otherwise useless in combat.
Function Discovery: Jaune's first attempt at a force field after a night of watching too much anime and drinking way too much soft drink, he found this partially programmed the next morning after.

Function Name*: Shield()
Function Category*: Combat
Function, er, Function*:
Active: Creates a shield around a target that will have to go down first before they can be hurt.
Passive: same as active but for yourself only, slightly stronger due to resource efficiencies. Upgrade: makes the attack unblockable.
Projected MEM Cost: 3 MEM
Function Discovery: After the events that led to Shell() Jaune decided to create a function that actually works as a shield in combat situations.

Spoiler: Pipe() and Derivatives, mastigos, QM Meddling- Middling-Major

Function Name: Pipe()
Function Category: Attack/Utility/Other
Function:

• Passive: On its own, this Function allows designated allies nearby the use of a SEVERELY cut back version of Inform, projected onto their field of view via ScreenCopy. They don't get localized omniscience but instead have an AR HUD that can retrieve information from the Transistor's localized omniscience. Things like highlighting enemies, chat screens, ammo tracking, asking what temperature the food is, etc. So Inform() but ratcheted down to a level they can actually process.
• Active: Subjects an enemy to information overload and blinds them with ScreenCopy filling their heads with random data from their environment, or specific data, depending on preference.

Projected MEM Cost: 2

Network(): an originate the function from allies (ex. launch a Bounce() from Ada's weapon) which, combined with Inform() effectively means they can launch it off by saying a trigger. But also means Jaune can launch it off arbitrarily without warning them.

• Allies can participate in Turn() planning but purely as a planning session, instead of bonuses they get a -1 headache penalty

Projected MEM Cost: 4

Function Discovery: ScreenCopy is a cludgy hack and he finally got around to fixing that because now he has friends this would be helpful for, then he kind of wandered off in a tangent during implementation

Spoiler: Pointer(), Pyrotech51

Function Name: Pointer()
Function Category: Utility/Combat
Function, er, Function:
Primary - Pointer() serves as a target designator in its primary form, marking the location of the enemy it strikes and guiding any further attacks towards itself. The projectile is extremely fast and difficult to dodge due to inherent aim correction, but only has a moderate effect on corrections to all other Functions.

Upgrade - adds a much more significant aim correction to that specific function.

Pointer()+Bounce() - Marks main target then marks all targets in range of jump as secondaries. All secondaries within range are hit by a % of the damage taken by the main target.

Passive - repeated functions during Turn() use less processing power after the first use. Breaking the chain resets the effect

Projected MEM Cost: 3

Function Discovery: I really don't know what fits for this, beyond some sort of frustration over excessively evasive targets anyways....

The active uses are based around the nature of pointers telling you where a specific thing is located, and then letting you interact with it directly.

The passive is instead based around the fact that passing a pointer to a function takes less memory than passing in a raw value.

Spoiler: Hold(), Blam(), Get() (formerly SweepUp()), MoonSerpent, QM Meddling- little to none

Function Name*: Hold()
Function Category*: Combat
Function, er, Function*: The upgrade of Freeze()! Now works against biological targets, Grimm
Projected MEM Cost: ?
Function Discovery: When at the end of turn(), Jaune realises it isn't enough to account for every enemy wanting to dome him and the team. Or when he just wants to lock that one enemy out of combat for a time. Further upgrades add AOE, removes protective stasis so attacks now actually damage targets.

Function Name*: Blam()
Function Category*: Combat
Function, er, Function*: A Modified Ping. Instead of a burst of fire, the energy is transferred into a concussive blast, best used for striking armoured targets. Highly synergies with Crash().
Projected MEM Cost: 1
Function Discovery: Sometimes you just need one good hit instead of many tiny ones.

Function Name*: SweepUp()
Function Category*: Combat/Utility
Function, er, Function*: Creates a pulling vacuum from swinging The Transistor, pulls light to medium sized enemies into the range of your sword. At the very least, stagger enemy movement.
Projected MEM Cost: ?
Function Discovery: Observing the use of Pyrrha's Polarity in pulling, pushing people around, The frustration to just wanting to hit Grimm hordes all at once.

Spoiler: Shunt(), Drive(), Port(), BlackCoat13

Spoiler: New Function Idea: Shunt()

Function Category: Combat

Function: Target and remove a enemy / target from the field, shoving them into a twist of space for a time (8 seconds base). Similar to the currently Beta Function Cache() or completed Function Freeze(), Shunt() is intended to be usable in combat due to targeting enemies instead of objects. Shunt() can target beings with Aura (or not) below a certain size threshold (Nothing bigger than a regular Ursa without modification). Shunt() cannot be used in its base forms against buildings, obstacles, or terrain.

-Function, Modified: Shunt() can be modified for a variety of effects. Shunt() can be improved to effect an area instead of just a single target, to Shunt() larger targets, Shunt() terrain away for a time leaving a smoothed landscape without obstacles, or to Shunt() the target for longer. Additionally, if paired with a DoT (Damage over Time) Function (Like Purge()) Shunt() can be used to do DoT, or certain Functions can cause Shunt() to do some damage immediately or upon release to the target as well as its base effects.

Spoiler: Example List for Shunt with Upgrades

Bounce(): When Shunt()+Bounce() is used the Bounce() is sent out to deal damage to a target. Upon hitting a target, Shunt() is then applied for 4 seconds. Bounce() then seeks out and hits a second target if one is within range, applying Shunt() again for 4 seconds.

Breach(): When Shunt()+Breach() is used, Shunt() deals the damage of Breach() to the target at that is Shunted() at the start of Shunt().

Crash(): When Shunt()+Crash() is used, Shunt() applies first, dealing Crash's() damage at the end of the Shunt(), any target released from Shunt() to takes more damage for 6 seconds.

Cull(): When Shunt()+Cull() is used, at the end of Cull's() damage is applied during Shunt(). If Overkill is applied, Shunt() explodes in an area at the end of Shunt(), dealing the overkill damage in an area around the Shunt() target's location.

Flood(): When Shunt()+Flood() is used, the area of Shunt is increased, turning from effectively a small target area into a medium. Increases size of Shunt() area.

Get(): When Shunt()+Get() is used, enemies and targets are pulled towards the Shunt() for 2 seconds before the Shunt() is applied. Minor Get() damage is inflicted at the end of the Shunt().

Help(): Shunt()+Help() creates a Shunt() that can remove obstacles and terrain. The area left behind is flattened. Doesn't work if an object inside the effective Shunt() terrain would be destroyed by the absence inflicted by Shunt().

Jaunt(): Shunt()+Jaunt() lengthens the time of Shunt from 8 seconds to 16 seconds.

Load(): Shunt()+Load() causes immense damage at the end of Shunt() to any enemies near the end of the Shunt() and to the target of the Shunt(). 4 second Shunt() duration.

Mask(): Shunt()+ Mask() causes User to become intangible but able to reposition about the battlefield. Essentially Ada's semblance without the Telefragging damage ability.

Ping(): Shunt()+Ping() causes Shunt to recharge quicker, enabling a Shunt to be used while another Shunt() is on the field.

Purge(): Shunt()+ Purge() causes Purge() damage to be done for the entire duration of Shunt() and for 3 seconds after Shunt(). Vicious combo.

Spark(): Shunt()+Spark() causes Shunt() to apply in many smaller areas, clustered together, enabling an entire Beowolf pack to be Shunted() at once. Deal no damage, lasts for 8 seconds. Large area effect.

Switch(): Shunt()+ Switch() causes Shunt() to effect a larger area for a shorter period of time.

Tap(): Shunt()+Tap() causes any enemy target Shunted() away to take damage for the 8 second duration and the User to get minor Aura restoration as life heal from the Shunted Target. Works on Grimm, may be partially magic rather than pure Aura / Science?

Void(): Shunt()+Void() causes Shunt() to reduce the attack and defense of the target caught by Shunt() once Shunt() is over for 6 seconds. Effectiveness reduced on Aura users.

Slice(): Shunt()+Slice() causes Shunt() to lock the enemy in place, but not place them in a special warp. Essentially a murder hold. Less effective on targets with Aura. Very high MEM cost. Base duration lasts for 4 seconds.

Spin(): Shunt()+Spin() turns the target area for Shunt() into a horizontal column of area in front of the user to be locked away for 15 meters and 6 seconds. Does not lock away terrain or obstacles, blocked by terrain and obstacles.

Drive(): Shunt()+Drive Increases the size of Shunt() the largest of all Shunt() size increases. You want to lock away the Grimm dragon for exactly 3 seconds? Increase the cooldown length of Shunt() based on the area locked away.

Shunt(): Shunt()+Shunt() Increases the size and length of the Shunt(). Time up to 14 seconds. Area up to medium.

-Function, Passive: As a passive, Shunt() wraps Jaune in what is effectively a damage mitigation aura that reduces all incoming physical based attacks before Aura damage. Shunt() could also be used to 'dodge' large attacks by using Shunt on Jaune himself, though this would not be used as a 'Passive' Function effect.

-Function, Upgrading: Used attached to other Functions Shunt() locks the target of the Function away for a few seconds on hit (based on what Function Shunt() was attached to), useful on close range Functions to prevent attacks or counter-attacks. Used on ranged Functions Shunt() can be used to lock away pesky ranged fighters for the time needed to close in on them or to remove them from attacking while you do something else. Used on some Functions, Shunt() no longer locks the target away but can somehow bypass physical resilience or armor, or possibly even Aura if you dare. Paired with Directory_Repair() Shunt() would shove the target (hopefully an ally) away into the spatial twist to heal them for 14 seconds, providing protection and healing. Attaching Shunt() to certain other combat Functions removes the effects of Shunt() entirely an instead freezes the target in place spatially, leaving them stunlocked and available to be damaged, but this has high MEM cost.

Spoiler: Example List for Upgrading with Shunt()

Bounce(): Bounce()+Shunt() causes Bounce to be able to target enemies over a larger area between bounces.

Breach(): Breach()+Shunt() causes all enemies hit by Breach() to take Breach() damage and by locked away in Shunt() for 3 seconds.

Crash(): Crash()+Breach() causes the target to be stunned by Crash() and left more vulnerable more much longer.

Cull() Cull()+Shunt() causes any enemy hit by Cull() to be thrown much higher into the air from Cull, increasing damage and causing the enemies thrown by Cull() to take 3 seconds to come back down.

Flood(): Flood()+Shunt() causes any enemy hit by Flood to be unable to move while taking damage from Flood().

Get(): Get()+Shunt(), any enemies drawn by Get() take damage and are locked away inside Shunt() for 2 seconds. Enemies drawn by this combo take doubled Get() damage at the end of the Shunt(), perfect for a light hit to kill them at the end of the combo.

Help(): Help()+Shunt() causes Luna to become intangible while moving, allowing Luna to have what is essentially Ada's Semblance.

Jaunt(): Jaunt()+Shunt() causes Jaunt() to enable User to Jaunt() through solid objects.

Load(): Load()+Shunt() causes enemies hit by Load() to take increased damage. Shunt() effects cause targets hit by the Load() to be paralyzed in place for 2 seconds.

Mask(): Mask()+Shunt() [Strike-Dependant] Hitting an enemy deals damage and causes them to be Shunted() for 8 seconds. User gains slight damage reduction for 5 seconds after becoming visible once more.

Ping(): Ping()+Shunt() enables Ping() to stop a target in its tracks for .3 seconds. Low MEM usage.

Purge(): Purge()+Shunt() causes Purge() to last longer.

Spark(): Spark()+ Shunt() causes an enemy hit by Spark() to be stunned for longer.

Switch(): Switch()+Shunt() causes Switch() to last longer.

Tap(): Tap()+ Shunt() causes an area around the User to be locked away in Shunt() but not the User. Useful as a panic move against enemy groups who have closed on the User. In addition, it does Tap() damage first and still heals the User for 1% of Tap() damage.

Void(): Void()+Shunt() causes an enemy caught within Void's() area to move slower for 2 seconds.

Slice(): Slice()+Shunt() causes an vertical arc of energy that deals Slice() damage but slows enemies hit by it for 4 seconds.

Spin(): Spin()+Shunt() increases the 'drag' Spin() has on things caught in the projectile of Spin().

Drive(): Drive()+Shunt() [Strike-Dependant] causes Drive() to stop at the first enemy hit and Shunting() that enemy for 5 seconds. Turns Drive() into a melee counter-attack.

Shunt(): Shunt()+Shunt() Increases the size and length of the Shunt(). Time up to 14 seconds. Area up to medium.

Projected MEM Cost: As a solo Function Shunt uses 3 MEM, as a passive Shunt uses 2 MEM, as an Upgrade Shunt() costs 3 MEM.
Function Discovery: Inspired by Ada, without scanning her Semblance, but based off her '4th dimensional being' state. An idea to weaponize Freeze() based on what scans the Transistor had already taken of Ada's Semblance.

Tl:dr: Temporary target removal. Like banishing your opponent's monster face down. Can be modified to adapt how it operates pretty extensively, useful for targeting big enemies who would otherwise be really nasty to have on the field but are too tough to kill outright where there's minions on the field.

Spoiler: New Function Idea, Drive()

Function Category: Combat

Function: A straight charge, similar but much slower than Jaunt(). Drive() maps poorly to Turn(), leaving its use best used without Turn(). On its own Drive() does decent damage, but it's real usage is hooking other Functions on it, making it a slower but much more damaging cousin to Jaunt().

-Function, Upgraded: Hook nearly any Function to Drive() to cause Drive() to perform that second Function either during or at the end of Drive(). Attach Crash() to Drive() to cause damage, stun, and leave vulnerable any target hit by the Function. Attach to Breach() to cause even more damage along the Drive() Function's length. Attach Jaunt() to Drive() to extend the length and speed of both but do only limited damage. Attach 2 Jaunt() to Drive() to hit Mach 1.

Spoiler: Example List for Drive() with Upgrades

Bounce(): Drive()+Bounce() [Strike-Dependant] upon hitting a target with Drive(), Drive() is aimed for the next closest enemy after trampling through the first enemy.

Breach(): Drive()+Breach() Increase the speed and length of Drive().

Crash(): Drive()+Crash() any enemy hit by Drive() is stunned for 3 seconds and left vulnerable for 4 seconds.

Cull(): Drive()+Cull() massively increase the damage of Drive().

Flood(): Drive()+Flood() causes Drive() to have a corona of Plasma generated just in front of the User during Drive(), increasing damage.

Get(): Drive()+Get() Enemies are drawn to the front of Drive() as the User charges forwards.

Help(): Drive()+Help() transforms Drive() utterly, turning a charge the user performs into creating and then launching a duplicate of the User to perform the Drive(), leaving the User free to act.

Jaunt(): Drive()+Jaunt() increases the speed of Drive() to instantaneous speed.

Load(): Drive()+Load() build up a load as the User travels with Drive() to explode at the end of Drive(). Massive damage.

Mask(): Drive()+Mask() causes the User to become temporarily invisible at the end of Drive() for 3 seconds, enabling retreat or further attacks.

Ping(): Drive()+Ping() causes Drive to be more efficient in Turn() and recharge faster.

Purge(): Drive()+Purge() causes any enemies still alive at the end of the Drive to be afflicted with a Damage over Time effect.

Spark(): Drive()+Spark() causes Drive() to explode at the end of the Drive(), dealing more damage than a regular Drive() but costing significantly less than Drive()+Cull().

Switch(): Drive()+Switch() causes any enemies alive at the end of Drive() to be Switched() for 3 seconds.

Tap(): Drive()+Tap() causes you to heal for a third of the damage inflicted to enemies by Drive().

Void(): Drive()+Void() causes any enemy alive at the end of Drive() to be weakened, having less Attack, Defense, and increasing incoming attack's powers.

Slice(): Drive()+Slice() widens Drive's() width by double.

Spin(): Drive()+Spin() causes a trail to be left behind by Drive() that yanks the enemies crossing the trail towards the end of Drive(). Trail persists for 4 seconds.

Shunt(): Drive()+Shunt() causes any enemies alive at the end of Drive() to be Shunted() for 4 seconds, enabling retreat.

Drive(): Drive()+Drive() causes Drive() more damage and move the User faster, but also take longer to cooldown.

-Function, Passive: Drive() gives a boost to your movement speed and increases damage from non-Function attacks User performs.

-Function, Upgrading: Causes the Function Drive() is attached to do more damage and also move forward on most Functions. Functionally little difference whether Drive() is the one being Upgraded or the one Upgrading.

Spoiler: Example List for Upgrading with Drive()

Bounce(): Bounce()+Drive() causes Bounce() to do more damage and move faster as a projectile.

Breach(): Breach()+Drive() causes Breach to be much wider, enabling more enemies to be caught in Breach().

Crash(): Crash()+Drive() causes Crash() to do more damage and have slightly longer range.

Cull(): Cull()+Drive() causes User to charge forwards using Drive() for a short distance, 'scooping' enemies before completing Cull() by throwing the gathered enemies into the sky.

Flood(): Flood()+Drive() causes Flood() to have more velocity and damage by a moderate amount.

Get(): Get()+Drive() causes Get() to draw enemies more fiercely and to increase Get() damage.

Help(): Help()+Drive() causes Luna to charge about with Drive() rather than attack by biting.

Jaunt(): Jaunt()+Drive() causes all enemies passed through with Jaunt() to take minor damage.

Load(): Load()+Drive() causes Load() to explode if an enemy touches the Load() bomb.

Mask(): Mask()+Drive() causes Mask() to do proximity damage to any enemy close to you while invisible. Duration of Mask changes to 4 seconds.

Ping(): Ping()+Drive() causes the User to kick with the force of Drive() without moving. Low MEM usage.

Purge(): Purge()+Drive() causes any enemy to take greatly increased Damage over Time over a shortened duration. Base damage of Purge() 120 over 3 seconds. Purge()+Drive() causes 160 damage over 2 seconds. High MEM usage.

Spark(): Spark()+Drive() is very similar to a Crash()+Spark() or Spark()+Crash(), being a three pronged near-melee attack. The user does not move during Spark()+Drive() but instead throws out three Sparks() that push enemies away from the user with Drive()-like force.

Switch(): Switch()+Drive() causes the enemy affected by Switch() to move much faster towards other enemies.

Tap(): Tap()+Drive() causes Tap() to have a greatly increased area. As Tap() causes the user to slam the Transistor into the ground at their feet and unleash a pulse of damaging energy that also heals the User by 1% of the Tap damage, this attack changes only a little by increased area of attack.

Void(): Void()+Drive() causes the enemies hit by Void() to have their defenses and attack reduced even further.

Slice(): Slice()+Drive() causes Slice() to be wider and thicker, and deal more damage on impact with enemies.

Spin(): Spin()+Drive() causes the Spin() to have more velocity and deal more damage.

Shunt(): Shunt()+Drive() Increases the size of Shunt() the largest of all Shunt() size increases. You want to lock away the Grimm dragon for exactly 3 seconds? Increase the cooldown length of Shunt() based on the area locked away.

Drive(): Drive()+Drive() causes Drive() more damage and move the User faster, but also take longer to cooldown.

Projected MEM Cost: As a solo Function, Drive() costs 4 MEM, as a Passive Drive() costs 3 MEM, as a upgrade Drive() costs 3 MEM.
Function Discovery: Created after witnessing Xanadu and his bullshit Inertia Semblance from Signal's Final and deciding, you know what? You want that. And so it was. It's nowhere near as impressive as the original, but it's still something that could be used to charge straight through a Beowolf pack, and with the right Upgrades attached to it you'll be able to charge straight through Ursa Majors.

Tl:dr: Drive is a damaging version of Jaunt. Slower, but rather than just being disorientating it incorporates damaging elements that can be further modded with other functions, such as Crash or Spiral, or by leaving a trail of Process matter behind us to spawn a small or medium unit behind us after we've already charged through an enemy.

Spoiler: New Function Idea: Port(), non-combat Function

Function Category: Utility / Other

Function: Teleportation. Yeah seriously. It's done in Transistor towards the end with the doors that link to other doors with weird spatial stuff. To pull it off a certain level of Process density has to have been achieved, so it's not like you'll be able to go just anywhere at will, you'll have to do work with the Process to set up 'Gates', stationary portal locations. Done right, you might even be able to bring other people with you. Who needs Raven?
Create those teleport gates in combination with the Process to create remote teleport marks and teleport to them. Not a combat skill.

Projected MEM Cost: Arbitrarily large MEM costs don't matter because it's not a combat Function so you could swap it in and out as needed with the help of the Process teleport gates. High research costs and time, but once it's done... teleport places, because travel makes us sick and we've got the capability by that point, so why not? May need to somehow capture and Trace() Raven to pull it off unless we want to spend 8 turns researching just this one Function though.

Function Discovery: You asked yourself, could it be done? You needed to fulfill that promise to fix the moon for Weiss, right? How would you even get the Process up there? This might not be the method due to needing a Process Gate on the other side, but you considered it.

Alpha Functions

Alpha Functions are the start- unsafe for use, and usually useless anyway. Worth a flat rate of 700 Code Points to shove into Beta or about three weeks on average. Two if you're lucky. One if you crit every single roll.

[] Lift()- You realised, with some... a lot... ok, if you butcher the Transistor's telekinesis code, you can... maybe... apply that to other things? It wouldn't be useful for too much, anything much larger than the sword itself is out, but you think you can probably find something for this.
Progress: 250/700

[] Directory_Repair()- A Function created from the Semblance scan of Professor Mary Edwards Teal, your old teacher and school nurse. Heals everything. Everything. Including the things that really kinda need to die off if you want to keep a person alive.
Progress: 538/700

Beta Functions

Now you're cooking with gas! Beta Functions are... technically usable, but prone to backfiring. Horribly.

... That poor cat never stood a chance- ER, TIDDLES JUST WENT TO SEE HIS FAMILY IN THE AGRICULTURAL DISTRICT. NOTHING BAD HAPPENED TO HIM AT ALL. HONEST.

[] Cache()- You're not sure where this one came from, honestly. Must've been one of those '4 am and your seventh cup of coffee' Functions. Looking it over, you think it would let you hide the Transistor in a small pocket dimension. As well as, other things, but mainly the Transistor. It wouldn't occupy space, or, actually have mass, but you would still be able to communicate with it, and it would still be able to float and follow you around. At least you can have it around without breaking any laws! Or, at least, breaking a different set of laws.
Progress: 0/1200

[] Slice()- It's like Breach(), a stream of high-energy particles, but more... focused. Instead of a wave, it comes as more of a slice. It's less of a shotgun, and more of, well, a sword-slice.
Progress: 1000/1500

Completed Functions

This is where all the Functions you've actually completed go. These are 100% safe to use, so long as you're not a moron with them.
Combat Functions:

Combat Functions are exactly that- Functions, for combat. However, some of them have a minor caveat- they require physical contact with a surface or opponent to trigger. This is usually a sign that the Function in question is meant to be used in close-quarters, not at range.

Crash(), 1 MEM: A weak, short-range attack that exposes weaknesses and leaves opponents open for a follow-up attack. Best used in a combo. (Strike-Dependant)

Breach(), 3 MEM: Creates a stream of high-energy particles that form a sideways pillar of death. (Strike-Dependant)

Spark(), 2 MEM: Launches unstable projectiles that split into explosive particles.

Jaunt(), 3 MEM: Transports User to a location directly ahead. Essentially a short-range teleport.

Bounce(), 2 MEM: Creates a ricocheting bolt that jumps from target to target.

Load(), 3 MEM: Creates a volatile Packet that, when struck, releases a violent explosion. Can be designated as a target.

Ping(), 1 MEM: Low-damage, low-MEM cost, low Turn() cost, high rate of fire. It's like a minigun made by Derringer!

Spin(), formerly known as Spiral(), 3 MEM: Fires a projectile that seems to barrel through everything, dragging along what it cannot destroy. Automatically dissipates after 8 seconds.

Freeze(), 1 MEM: Freezes an object at its current XYZW axes for 30 seconds, with compensation for Remnant's celestial movement so they don't just launch into space. During this time, it's impossible to affect the object in question during this period- you could crash a car into it, and the car would lose. Most likely.

List of Utility Functions: (Utility Functions do not count towards overall MEM, as they are base parts of the Transistor's programming, or otherwise of negligible MEM Cost.)

Restore(): Allows you to return an object to a former state as long as the Transistor has said state logged. {I'll even do things I don't have a former state for, but it might take a while.)

Search(): Highlights objects within a radius around the user according to certain criteria. {You'll never lose your keys again.}

Inform()- The Transistor is constantly feeding you information about the world around you, streamed directly into your eyeballs. Essentially, functional omniscience about everything within your direct line of sight. And everything not, it just chooses not to tell you about that stuff. FOR GOOD REASON.

Bridge(): You work with lots of different computers. But as it turns out, hypercomputers summoned out of pure math don't naturally fit standard I/O ports. This initially started as a simple means of using the Transistor to transfer data, but you've been continually iterating upon it for years. For simple magnetic drives or transistor {Lowercase!} chips, high fidelity scans combined with directed physical manipulation let you read and write arbitrary data to and from any section, without even requiring the device to be powered. Unfortunately, (or perhaps not, given the power it'd give you...) Dust based systems are far more difficult to manipulate in such a way. Still, the control chips of toasters everywhere cower in fear!

Antenna(): A minor sub-function piggybacking off of Inform(), which streamlines the process of interpreting separate data streams out of the radio noise around you, and making transmissions of your own. Theoretically, you made this thing able to pick up just about every communications standard in use on Remnant. Practically, you've actually finished coding the backend for about three of them.

ScreenCopy(): This copies the display of Jaune's scroll and imposes it onto his field of view. By default, it's set to be a page display that can be moved and have its opacity adjusted. ...Yes, it's a cludgy hack, okay!? Do you feel like working out all the garbage needed to make multimedia work properly?

FakeInput(): This translates mental commands into simulated synaptic touchpad inputs, which are then fed to Jaune's scroll in place of the data from the touchscreen. A surprising amount of the code was copy-pasted from the control scheme for the Transistor's 'telekinetic' movement. {It's almost impressive how little effort went into this.}