Comments

LBPHacker 8th Mar 2020

Anyway, since most things you can affect with sparks are the subframe infrastructural parts rather than the actual computation parts, it's not surprising that messing with those breaks the computer more spectacularly than you expect. You'd probably have to mess with FILT ctypes instead if you want only subtle malfunctions.
LBPHacker 8th Mar 2020

What's the difference between malfunctioning and being broken though?
JustAPlayer 8th Mar 2020

i've always wanted an eficcient way to get cool glitches on the r2. randomly sparking things just doesnt work and you end up breaking the whole machine. i know how to make the terminal malfunction in a cool way just by sparking it, but i have absolutely no idea how to make the r2 itself malfunction without completely breaking it. it would be cool if LBPHacker decides to help us make a corruptor for the r2.
HuntaBadday 8th Mar 2020

Its not that easy making a corruptor because the computer will need to listen for data first and it has to be synced up, so when the computer dosent want any data it wont listen for data.
JustAPlayer 8th Mar 2020

it doesnt have a corruptor, its just a concept made by me :^)
josha254 8th Mar 2020

why does it have a corruptor
ctOS2 8th Mar 2020

imagine being this smart holy crap
JustAPlayer 5th Mar 2020

but using a single R2 would be a kind of bad idea, because both the corruptor and the program runs on the same R2 and you would end up corrupting the corruptor too, as if the computer was using an uno reverse card xD
JustAPlayer 5th Mar 2020

because it (would be) a real time corruptor, you need to control the corruption intesity, error delay and target component somehow. you need a separate terminal for controlling the corruption settings while the other program/game/whatever in the other ROM slot runs
JustAPlayer 5th Mar 2020

@SpeedyGwen yeah, good idea! you would still need two ROM slots and a separate terminal for the corruptor GUI tho

The Powder Toy

text transfer on the r216 by HuntaBadday

Comments