Author Topic: [Default events] Writable/readable disk [No named bricks]  (Read 4711 times)

i take it as it works by using projectiles? it should work with them, if it is projectiles, i think i know how you did it
i'm thinking of the combo lock you showed me on blobeh's server when i was making mine, with radiowaves and unraycasted bricks with print counts, which means you could fire projectiles from the colored bricks downward, and then that would record it, and then fire it back up to set it?

does the painting interface also not use named bricks?

No, because that was just an example contraption to interface with the disk and I was lazy.

i'm thinking of the combo lock you showed me on blobeh's server when i was making mine, with radiowaves and unraycasted bricks with print counts, which means you could fire projectiles from the colored bricks downward, and then that would record it, and then fire it back up to set it?

Not quite - if it just used radio waves, how would it know if you're setting or reading from it?

so this could be used in a blockland super computer to create pictures, music, and simple text?

just noticed, if you save the same picture over a used disk, it changes the picture, is there any way to make a block, so this doesn't happen?
« Last Edit: August 11, 2010, 07:22:06 PM by fred da kiko »

so this could be used in a blockland super computer to create pictures, music, and simple text?

Yup. For text, you'd dedicate 2 memory cells per character so you can support up to 100 different ones.

just noticed, if you save the same picture over a used disk, it changes the picture, is there any way to make a block, so this doesn't happen?

What do you mean? If you save a picture onto a disk, it's going to overwrite anything already on the disk - that's not a bug. Use the duplicator to move a disk out after you saved to it and then move a new, blank one in if you want to save another picture. Since there aren't any named bricks (more emphasis), you can have as many disks with pictures as you want, so this isn't a problem.

Yup. For text, you'd dedicate 2 memory cells per character so you can support up to 100 different ones.

What do you mean? If you save a picture onto a disk, it's going to overwrite anything already on the disk - that's not a bug. Use the duplicator to move a disk out after you saved to it and then move a new, blank one in if you want to save another picture. Since there aren't any named bricks (more emphasis), you can have as many disks with pictures as you want, so this isn't a problem.
i didn't say it's a bug, i just said that i noticed that...

i didn't say it's a bug, i just said that i noticed that...

What did you mean by making "a block"?

What did you mean by making "a block"?

I believe he means a way to block it from happening.

I believe he means a way to block it from happening.

Block it from writing to the disk? So like a "are you sure you wish to overwrite" kind of thing?
I suppose it could be done, but this isn't to showcase the paint program, so I'm not editing it.

Now make one where each memory cell can only be a 0 or a 1.

x9 size

x9 realistic

Now make one where each memory cell can only be a 0 or a 1.

x9 size

x9 realistic

I actually had made a simple beat looper with either a pause or a note using an 0/1 memory disk (punchcard fashion, so no print counts) before, but I didn't think it was that impressive so I never posted it on the forums. Yet to use that with something like this, combining the values and checking to get the colors of each pixel would be a pain.

So yes, x9 size. Probably more.

Pretty cool idea, I think i see how it works, I just don't really know how to made it assign each tile a number to match it's color.

Super win, also, on Blockland everything loads almost instantly :D

Block it from writing to the disk? So like a "are you sure you wish to overwrite" kind of thing?
I suppose it could be done, but this isn't to showcase the paint program, so I'm not editing it.
i'm saying like a fail safe system, so you can't save over a memory disc twice, i guess you could use a relay wire or a projectile with something in the way. remember, i'm talking about the other uses for this, computers and things like that.


This would be awsome to go with my project of makeing a default event computer

mine is powered by relays and projectiles
basicly i make simple transistors and logic gates where projectiles are fired to enable/disable the ability of another brick to fire relays all synced to a master relay(the only named brick could be replaced with a train of relays but im to lazy)
heres the link
http://forum.blockland.us/index.php?topic=108356.0
although maby my I-event app was newer version meh
may be a bit buggy
but I could also make a 7 segment display
so you can fit one bit of data on one or two bricks!
with my system I could only compress the latch I use for memory to a 1x3 Brick size with all 9 spots being used plus a brick for syncing