You know, I agree, Jaune should....We really dont want shouty-maze guy to get the free ride. He goes down first.
I'm fairly sure that Fetches are just the dedicated defence system of the Process, while other Processes can defend themselves, the Fetch branch main function is fighting to drive off threats. That doesn't directly translate to being aggressive towards all humans, just that they will defend the Process and all affiliates (namely us and our team, since we have the Transistor and the Process hasn't gone rogue) against all threats. Also, nothing prevents us from using the Transistor to make it very clear that they have to keep it non-lethal, just put them on the "drive off" mindset rather than the "eliminate" one.You know, I agree, Jaune should....
...
I think I thunk a thought. Use Restore() to turn the arena back the way it was. Good tactical move and it lets us gang up on Saff while he tries to put it back up.
Now then, time for meta: Restore() is a simple application of Cloudbank's self-directed evolution, which was carried out by the Process. We don't need to "accidentally" anything, just look into basic functions!
Also Fetches are human aggressive if I remember Royce's commentary. Miiiiiiiight want to be super careful.
I think you're right about the Fetch's job within the Process, but I'm pretty sure the Fetch are still dangerous. Royce's Fetch sample was aggressive and he wrote them back when he owned the Transistor. Besides, ALL of the Process have combat roles, there's a reason Royce Limited them even when they were under his control.I'm fairly sure that Fetches are just the dedicated defence system of the Process, while other Processes can defend themselves, the Fetch branch main function is fighting to drive off threats. That doesn't directly translate to being aggressive towards all humans, just that they will defend the Process and all affiliates (namely us and our team, since we have the Transistor and the Process hasn't gone rogue) against all threats. Also, nothing prevents us from using the Transistor to make it very clear that they have to keep it non-lethal, just put them on the "drive off" mindset rather than the "eliminate" one.
Also, I don't think using Restore() for such a large area is gonna work. At best it will be denied by safety locks, at worst it won't be blocked and we will end with permanent brain damage due to data overload. Just doing a deep scan of a few people at once is enough to put Jaune near the edge of a cauliflower soup impression, trying to figure out the composition of and where all the pieces of the labyrinth go and putting them back there while fighting against the active efforts of an hostile's semblance isn't gonna go well.
... Ok, yeah, this works, this works fine, I can work with this.The traditional tabletop reward is bonus experience. Since I don't see an experience system, maybe you grant bonuses in this scene or some free progress on Jaune's next Function? Flash of inspiration or something. I'd rather have the latter, if you're willing and if Ridiculously Average Guy okays it.
Nice try, but no cigar, champ. Restore(), and all of your Functions, actually, all work on the same principle-Now then, time for meta: Restore() is a simple application of Cloudbank's self-directed evolution, which was carried out by the Process. We don't need to "accidentally" anything, just look into basic functions!
You could just... do it in chunks. The task is only as big as you make it, mind. And the scanning isn't strenuous, it's just annoying, and an invasion of people's privacy, and... ignorance is bliss, basically.Also, I don't think using Restore() for such a large area is gonna work. At best it will be denied by safety locks, at worst it won't be blocked and we will end with permanent brain damage due to data overload. Just doing a deep scan of a few people at once is enough to put Jaune near the edge of a cauliflower soup impression, trying to figure out the composition of and where all the pieces of the labyrinth go and putting them back there while fighting against the active efforts of an hostile's semblance isn't gonna go well.
@Ridiculously Average Guy, when the time comes for making Functions, you can either make up a Function of your own, subject to veto, or choose one of the Functions on show. Either way, that Function will immediately be shunted into Beta Testing, essentially the middle stage of Function creation, allowing you to shove something along the chain of progress a little.
Make it a good one!
NICE.
In that case I figure either:
Repel/Firewall() Since a defense ability seems to be something lacking in the canon functions (also because there's a semi-popular theory that canon!Jaune's Semblance is Repelling)
Capture/Save() Use the Transistor to capture the force/effects of an attack and launch it back after a delay
NICE.
In that case I figure either:
Repel/Firewall() Since a defense ability seems to be something lacking in the canon functions (also because there's a semi-popular theory that canon!Jaune's Semblance is Repelling)
Capture/Save() Use the Transistor to capture the force/effects of an attack and launch it back after a delay
Well, doing it gradually would allow Seff to counter it quite easily. If he could build the whole thing this quickly, remaking a small part of it should be nearly instantaneous.... Ok, yeah, this works, this works fine, I can work with this.
Panic over! I like the Function thing, actually, especially since this is actually a pretty big thing.
@Ridiculously Average Guy, when the time comes for making Functions, you can either make up a Function of your own, subject to veto, or choose one of the Functions on show. Either way, that Function will immediately be shunted into Beta Testing, essentially the middle stage of Function creation, allowing you to shove something along the chain of progress a little.
Make it a good one!
Nice try, but no cigar, champ. Restore(), and all of your Functions, actually, all work on the same principle-
"Screw The Rules, I Have A Semblance!"
The Process will come. Eventually. Hopefully in a way that's less intimidating than that sentence.
You could just... do it in chunks. The task is only as big as you make it, mind. And the scanning isn't strenuous, it's just annoying, and an invasion of people's privacy, and... ignorance is bliss, basically.
Ok, look, imagine- you're out on a date with someone, real cute redhead, you're getting along, you're chatting away happily, things are comfortable, you're definitely thinking of a second date- symptoms present- stomach cramps, increased rate of peristalsis, diagnosis; Irritable Bowel Syndrome- aaaaand way too much information, you're immediately uncomfortable because you know something they could very well be sensitive about. And that's just situational stuff.
This thing scans people down to the subatomic level, man, who knows what it's gonna tell you?
What if it told you your sister suffered from severe anxiety? What if it told you another sister's pregnant? Neither of them told you these things, so what do you do with that information? Just sit on it? Find a way to bring it up and hope they're just comfortable about it? What about the pregnant one, what if she doesn't know she's pregnant? How do you prance into that minefield?
Jaune doesn't turn it off because it's strenuous, he turns it off because people deserve their privacy, and frankly he doesn't want to know anyway. Ignorance is bliss.
... For Jaune.
Can't blame a guy for trying!Nice try, but no cigar, champ. Restore(), and all of your Functions, actually, all work on the same principle-
"Screw The Rules, I Have A Semblance!"
The Process will come. Eventually. Hopefully in a way that's less intimidating than that sentence.
Don't forget too that there'll be a list of premade Functions to choose from as well. Something like Tap() or Mask() could end up being HIDEOUSLY useful.What about one that works like a capacitor? First it absorbs the kinetic energy (or just plain energy if it's something more exotic like one of those Aura strikes Ren uses or a Dust attack) of an attack/several attacks up to a certain amount, then it releases it at the user's discretion, either as a way to move around or as an attack. Could be an useful way to quickly move allies out of the way of attacks seeing as they don't have Jaunt() nor Turn() to see them coming nor to dodge them.
True, I did forget to add Void() to that list, switched it out for Mask() at the last moment. And oh geez, that Void()+Spark() combo is VICIOUS.
... Ohh. I was thinking of it more as an aftermath cleanup thing.Well, doing it gradually would allow Seff to counter it quite easily. If he could build the whole thing this quickly, remaking a small part of it should be nearly instantaneous.
That being said, if the point is distracting him and tricking him into spending his aura levels that might work. Given that he doesn't bury us alive once he gets fed up, though.
That's called The Process.How about copying Seff's semblance with functions? It is pretty strong and seems like it would be pretty damn useful though I imagine a nerf if we did go for it.
Just have the Transistor say "Hello World." out loud?
Unfortunately, I'm giving up on any kind of update for this tonight. I've got what looks like a rather nastily infected pair of hangnails on my right index and middle fingers, and they're making any kind of typing... incredibly painful.
Hopefully, by tomorrow they'll have healed into numb, unfeeling scabs, enough so that I can get a late one out, but tonight... no bueno.
Apologies.
Printscrn:"Hello_World"
Iiiiinteresting. An expansion on the game's Help() function?So we can propose functions? Here's an idea from programming.
Recursion()
A high cost function that can only be used durring a Turn(). Creates a phantom copy of Jaune that repeats his movement and functions for the duration of the turn but with notably weaker strength. If used multiple times in a single Turn() the first copy will make a copy of itself that is even weaker when it performs the Recursion() function, thus making 3 clones in total. The number of clones expands at a total of 2^x-1 for as many uses he can manage in a Turn(), but the damage falloff makes spamming it largely useless, as does running out of points and not being able to perform other functions to be copied.
That's called The Process.
More seriously, you can copy Semblances, as long as you have a decent idea of the overall effect or mechanics behind it. Especially if they happen to have an actual scientific force behind them. At worst, they're good inspiration for Functions. Saff's... would be a sight more difficult to translate to a Function, and overall would just be less useful than advancing the Process, once you have it.
Don't forget dancing! Now we just need to incorporate it into our fighting style...Huh, thinking about it, Jaune's basically a buff(?) male version of WEISS skillwise. Sword, scifi-magic spells, summoning...
Armor() has potential, but I don't think Jaune wants to tank. The Transistor is a sword(), not a weapon to actually hit things with.
No, not at all. Recursion is when a program spins up another copy of itself to perform its actions again. Breaking out of the loop is infamously difficult for beginning programmers and when you screw recursion up the program will call itself endlessly causing a stack overflow error. In fact it's so infamous that the go to industry help site for programmers is named Stack Overflow, all the other Stack Exchange help sites are modeled after it.