[Default events] Writable/readable disk [No named bricks]

[Truce]

Yeah, default events, no named bricks on the disk, and a writable/readable disk.
I made a simple color program to show how it can interface with one of the disks.

Start with your blank canvas:
(Which is what's in place by default when you load the save file.)



Click colors then click pixels to create an image:
(The color selection is at the top; a pretty basic event mechanic.)



Locate a blank disk (provided in the save):
(There's no named bricks on it so you can create infinite of these!)



Move it into the disk slot with the duplicator:
(You don't have to wand the original after, but you can if you want.)



Press the "S" button to write the IDs:
(I moved it out of the slot with the duplicator before taking the pic.)



Similarly, if you put a disk with IDs already written on it and press "L", it will load. Pictures can't really do it justice so take a look at the save file below sometime and try loading the example disk. If you're decent at events, you could even make a program to interface with a disk. Maybe one of those "MIDI sequencers" to save your tracks and share with others? The save file comes complete with a blank disk and a disk with the image above on it.

Pay more attention to the events on the disk, the events on the color program are kind of messy since it's an example.
http://www.mediafire.com/?zoa14pxudc2oocc

EDIT:

Oh right, make sure your schedule/projectile quotas are pretty high (1000 is max). Also, this is an accomplishment because the only inputs I could use to communicate from the program to the disk without named bricks were onProjectileHit and onBlownUp, which I intertwined pretty cleverly if I do say so myself. Check out the events on the disk if you want to see the "protocol" for setting a value on it and asking it to return the value.

[Ad Bot]

[Hugums]

I vouch for the validity of the claims of the use of default events only and I must state that this is pretty forgetin cool

[Butler]

This only uses default events? Holy stuff.

[Caution]

I'm confused.

:c

[Hugums]

This only uses default events? Holy stuff.

That's what i said when i saw it. I stuff myself

[boodals 2]

Hmm.. I probably could do this, but it would take a hell of a lot more bricks than you have..

I am impressed..

[Treynolds416]

This is nice and all, but can it have a significant use? Like what will read the disk and do something according to the info it finds? Computer?

[Truce]

This is nice and all, but can it have a significant use? Like what will read the disk and do something according to the info it finds? Computer?

Yeah, in my post I had only provided pictures of saving, but I had also mentioned how the "L" (load) button is an example of how event contraptions can read from the disk. Specifically, for this one, the "L" button queries what values are in each slot of the disk, and after the disk returning the value, it sets the colors on the screen accordingly.

I guess the overall selling point here is that the disk can be written and read by any event contraption, no matter what it is, without having to change events on the disk to fit that program specifically. And since it uses no named bricks like older scoring-storing systems, users can dupe all the disks they want and it won't cause any interference.

[Doomonkey]

Coolio.

[SpreadsPlague]

I used to think I was good at events

then I looked at this topic. :c

[No2mad2]

I used to think I was good at events

then I looked at this topic. :c

I feel the same way. :(

[Randomguy]

Truce is a wizard.

[Lordy Lord]

You must have access to high magic, good sir.

[Truce]

ribbit ribbit ribbit ribbit

Indeed I am.

[Moybus]

does the painting interface also not use named bricks?