Minecraft Forums

After several hours of playing Google&Guesswork, ich have managed to find a solution.

* In the Forge config, set removeErroringEntities = true.
* Load the world.
* Save and exit Minecraft.
* Reset the config setting to false.

Quote from Streetwind»

Just a heads up - I upgraded from 5.0.2 to 5.0.3 and lost all my research. And I mean literally all - even the basic stuff like the aspects directory and such now prompts me to equip scribing tools and paper to unlock the research.

I don't know if this is a known issue or not, I've not had Thaumcraft installed since the early days of v4. I just thought I'd mention in the off chance that I'm helping someone prevent experiencing the same. If there are known fixes - I'd be very interested right now >.<

Update: I managed to fix my problem by setting research to xp levels only in the config file and then going into creative mode ingame.

Honestly I'm in favor of simply not dealing with lighting issues for infinite heights. Cubic chunks has so much else to give us besides infinite height, it would be a shame to can the idea for one special case that can simply be avoided/ignored.

Right now the world is 256 blocks tall. That is a whole lot of blocks, as evidenced from playing in a world with the Alternate Terrain Generation mod, which actually uses the entire available height to produce varied, rolling terrain. It's double to quadruple of what vanilla Minecraft has in terms of landscape above sea level - I was extremely surprised how much of a difference there was despite still being "confined" in "only" 256 blocks vertically. It only shows that if you can do so much with that, you don't need 1000+.

Mojang has always cited performance issues when people wished for more height variation in the vanilla terrain generator, and that is what cubic chunks could handily fix. The point is, you don't need desperately more than 256 build height, when right now you're barely even using half of what's available. You don't need negative y-levels. You don't need to think about changing bedrock or the void or the upper build limit "wall". Keep the world 100% exactly as it is now, and cubic chunks still gives you advantages.

Then maybe, if it is technically feasible, you can think about a second step where you up the world height to 512, and move sea level to 128 instead of the current 63. I imagine that, with that much space available, a terrain generator that actually uses it (the highest peaks stopping somewhere between 400 and 450, I'd imagine), and the performance advantages that cubic chunks bring, you would have a solution that satisfies 99.99% of all people and doesn't break anyone's computer's back with lighting updates. But yeah, even that shouldn't be first priority. Just making it work within the standard confines of the world that we are already used to would be a great start.

Hello all! I know what you may be thinking: oh dear, another noob coming to ask how to mod Minecraft?

Well... not entirely. I generally look stuff up myself. I taught myself the basics of Java, I followed along VSWE's excellent tutorial series, and I google guides. However, I have hit a snag, and I'm hoping you can help me along.

Basically, I don't want to make a content mod. I don't want to add blocks or items or Yet Another Macerator(tm). I know plenty of mods that do this already, and probably far better than I ever could, considering I have the artistic ability of a comatose warthog. No, instead of that, I want to change the underlying rules. I want to generate a config file for vanilla Minecraft, if you will - a config where you can change things that Minecraft normally doesn't expose, like how much hunger it generates to swing your pickaxe at a block, or how many pieces of leather a cow drops.

Unfortunately, I don't even know where to begin googling for info on how I do this. Modifying base classes is of course not the solution - not only does it cause incompatibilities, but Mojang has also made it clear they don't like modders doing it, and that should be respected. But what is it that I do instead? What is the name of the thing I am looking for? And do you guys know any good resources for learning about it?

In other words: "We could attempt to meet the modding community halfway with this, if we wanted to, but we definitely won't do it if that saves us a ton of work and/or compatibility issues."

I'm honestly not sure if you can infer anything good from this statement. Now, you can't automatically infer anything bad either, but what I mean is to not read more into it than it says. That statement gives no actual, hard information on anything other than "the idea used to exist but was sacked and shelved".

I'm all for this concept as much as the next person here, and I'll let Mojang surprise me any day if they like, but I'm certainly not holding my breath for them making a concerted push for it based on that statement alone. Keep your bets with the modding community, folks. And if you're a supporter who can code, consider doing so. Don't wait for one single person to do all the work for everyone else!

Awesome, I've missed this mod so much.

Quote from sh00ter999

Excellent mod but the fact that you have to unequip armor gets annoying :/

You can disable it in the config.

Looks decent - and I applaud your creative usage of 1.6's new health regeneration mechanics (for those who don't read patchnotes: regenerating health rapidly depletes your food bar, making health a lot less "free of charge" than it used to be).

As long as you can avoid any glaring cross-mod exploits, I'm sure this will be an excellent addition to any magic-themed modpack. Might be extra fun with the likes of IguanaMan's Hunger Overhaul, which puts a lot more emphasis on keeping yourself properly fed.

Quote from The_Watchman13

It was a mod, but it hasn't been worked on in over a year. The main focus of this topic is to get Mojang to make this part of Minecraft.

Then I must ask you: have you guys talked to Mojang yet? To an actual dev? Potentially one who's working on rendering revamps already?

The "contact popular youtuber" option doesn't only involve getting the word out to the community, you know. There's this beautiful thing called Forgecraft, where major mod developers using the Forge modding API test out their development builds. And they have at least one Mojang employee (Grum) regularly showing up and playing there, checking out how people mod Minecraft and what modders are looking for in an API.

Forgecraft also has a large number of streamers and youtubers. Direwolf20 is among them, Jadedcat, Eddieruckus, Sotmead... heck, you could go directly to MinecraftForge and hit up the dev community there, too, since this is dealing with the core systems of Minecraft itself. If anything, API devs are going to be even more excited about core system changes than regular players If you managed to get in touch with the right people, maybe they can put a word in with Grum for you, maybe get him to at least give a comment on this suggestion or even discuss it with you. It's probably not going to be easy, but if it works out it'll be worth more than a million upvotes in this forum.


P.S.: Have my +1 anyway.

Quote from Apasz

What is that big yellow thing in the pic?

A phallic symbol Some liquid glowstone. It is lighter than air and flows upwards.

Quote from SirSengir

Usually best to report issues at https://bitbucket.or...new&status=open which I use as a laundry list before doing new releases.

Alright, I'll keep that in mind.

That said, I was able to run a peat bog at maximum efficiency (all mature bog more or less instantly harvested) using two peat-fired engines... while at 400%. That would mean the peat bog consumes so little energy on default that you could run two bog/turbary pairs off of one single peat-fired engine? Guess I should have bothered to build a peat bog sometime in the past... I'll test it out by throwing some really high and low values at it and comparing.

@ weltallofid:
No idea about your fermenter issue, never encountered anything like that. As for biofuel, consider this: 1 bucket of biomass is worth 50,000 MJ in a biogas engine, whereas 1 bucket of biofuel is worth 200,000 MJ in a combustion engine. Both running at 5 MJ/t. Does it seem like a worthwhile investment to you? I personally like using combustion engines, so I often do take the extra step to build a still in order to refine my biomass. Plus, Railcraft liquid fueled boilers take biofuel as well (and give comparable yields) whereas they will not accept unrefined biomass.

Features

• Clean and easy to navigate UI
• Multiple instances
• CraftBukkit, Spigot, PaperSpigot and TacoSpigot compatible
• Organized dashboard & settings
• Built-in updates
• ...

More features: www.mcserversoft.com/features

Downloads

To be clear this program is free to use, without limitations and ads!

Port forwarding is required.

Only for Windows Operating Systems with .NET Framework 4.5 or higher installed.

Changelogs/Documentation

Vote / Comment

This mod adds three blocks that can store items just like a chest. But, barrels can only store one item type, but a lot of it. The quantity that is able to be stored varies by the type of barrel used.

---

Table of Contents:

Overview
Changes in how things work
Frequently Asked Questions
[WIP] The Cubic Chunks Mod!
Gallery
Supporting this suggestion
Special thanks

[spoiler=Tl:dr]Q: Won't this increase lag?
A: Absolutely not. The title of this suggestion and big red letters at the top of this post aren't lying. If you want to know how, then I suggest you actually read this post.

Q: Will this change terrain? Will this break existing worlds?
A: No. Terrain change is not necessary. Existing worlds can be converted fairly easily with a process described later in this post.

Q: How can sunlight or rain work with infinite vertical space?
A: I suggest you read Coping with sunlight, because it's too complex for a tl;dr.

Q: I have a different question but still don't feel like reading this post. What do I do?
A: Too bad, read the FAQ. I put way too much work into this for the entirety of it to be ignored.[/spoiler]

---

Overview:

In Minecraft, the sky is the limit - literally. It doesn't matter how many thousands of blocks a player has traveled, or what dimension they're in, or even if they're playing in creative or survival, the highest they can ever build is up to a height of 256. Why is that? If Minecraft can have a world that's infinite in the north, in the south, in the east, and in the west, why can't that world be infinite up and down too?

In Minecraft's earliest days, in Classic and Indev, the world was not infinite in any direction. This was because the entire world needed to be generated at the same time, and the entire world needed to be simulated at the same time as well. This led to a conundrum - the bigger the world, the more it lagged.
Notch didn't like this. He knew his players liked to explore and build large creations, so he found a way to make the world truly infinite. When the Minecraft '' class='bbc'>Infdev came out, it brought with it truly infinite worlds. Suddenly, players could travel hundreds of thousands of blocks in any direction, and never encounter a barrier, or become too laggy.
The Infdev update brought about a very large change to Minecraft worlds to accomplish this feat. For the first time, instead every world being just a single huge piece, they were broken up into a two-dimensional grid of pieces, called chunks. Through breaking the world up into pieces, this 'chunk system' enabled infinite worlds by letting Minecraft create new pieces and simulate them only when it needs to.

Why does that not apply to the vertical axis? Because the type of 'chunk system' Minecraft uses right now is a linear one, which, by using only a two-dimensional grid to map out chunks, means that it is impossible for chunks to stack on top of one another, and by extension, meaning that a single chunk must cover the entire vertical space. This brings back the problem that the Infdev update was supposed to eradicate, now only with chunks, instead of an entire world; the bigger a chunk is, the more laggy it is. You can't just increase the height limit and make chunks taller, because it will become laggier, and laggier, and laggier to do it.
That's why, to fix this, Minecraft must change over to a cubic chunk system. Under this system, 16³ block chunks are aligned on a three-dimensional grid, completely eliminating maximum height as an aspect of lag.

The immediate benefits:
•Minecraft worlds become as virtually infinite vertically as they are horizontally: The absolute limit being Y = ±30,000,000.
•A large FPS increase: Alpha testers report an FPS increase of 100~200%.
•Increase in running capability: Computers running Minecraft on Tiny render distance will handle only 30% the blocks they do now.

The possible features:
•Spherical render/load distance: Reduce handled blocks by up to 30% by cutting corners made of unneeded chunks.
•Server chunk occlusion/exclusion: Reduce bandwidth usage and defeat hackers by only sending data for visible chunks.
•Three-dimensional biomes: Save biome data per chunk rather than per block column, create volcanoes with magma chambers, underground rivers, tropical skylands floating over icy taigas, and more.

The disadvantages:
•Unloaded gravity-pause: Falling non-player entities and fluids will be forced to pause their fall if they reach unloaded chunks, but will resume falling when those chunks are loaded.
•Slow falling-pause: Players with slower computers and smaller render distances will have falling occasionally paused as they fall into unloaded chunks, until new chunks can be loaded.

The problems:
•Current sunlight and rain calculation methods cannot work with infinite vertical space: The solution to this is described here.
•Current BiomeDecorator cannot work with multiple vertical chunks simultaneously: The BiomeDecorator code must be altered to function correctly with this, or removed.
•Current cave generation method is executed an extra time for each vertical chunk created simultaneously, leading to lag spikes on world generation: Cave generation's method must be altered to suit this system more.
•Current grass/dirt generation algorithm forces additional chunk requests when chunks are loaded, causing chunks to load slower than they should: This algorithm must be replaced with something else.

---

Changes in how things work:

Obviously, the implementation of this new chunk system will change quite a few things. These changes are mostly either necessary or in the interest of increased efficiency. Such changes are categorized and explained below.

How worlds will be stored:
[spoiler]How the current storage works, and what changes:
Interestingly enough, the current method of storage, the Anvil format, is derived from the storage method that the original Cubic Chunks mod used. The Anvil format stores individual chunk as a series of 16³ quasi-cubic chunks. These 'fake' cubic chunks allow for easier reference of specific data, but they still can't be separated from each other, meaning that it fails to reap the full benefits of this system. Even so, the change allowed Mojang to double the maximum height with no performance hit. Chunks are stored in groups of 32², inside 'MCRegion' files, for a total of 1024 chunks.
By nature, cubic chunks does away with the 'quasi-cubic' nonsense. In terms of chunk grouping, instead of using groups of 32³ chunks, new "3DRegion" files would contain groups of 16³. This means each 3DRegion file contains 4096 chunks, four times as many as MCRegion files. However, each 3DRegion contains only one fourth the amount of blocks. For per-chunk positional metadata, 3DRegion files would use the same number of bits as MCRegion files, after compression. Calculations show that the same area encompassed by a single MCRegion file would consume 64 kilobytes of extra space with 4 3DRegion files, which is nothing.

Converting existing worlds:
Most people are probably wondering something like "But won't this totally destroy all existing worlds?". Absolutely not; conversion could not be simpler. When a non-cubic world is loaded after the implementation of this system, a conversion process will begin and convert the entire world at once(To avoid making chunk loading take longer during play). First, all existing MCRegion files will be divided into quarters to create 3DRegion files. Then, all existing chunks are divided into sixteenths using the quasi-cubic properties to identify boundaries. After that, conversion is done.

The "isEmpty" flag optimization:
A 1-bit flag is added to each chunk, named "isEmpty". If the chunk consists of 100% air blocks, this bit is 1, any other case makes it 0. When the bit is 1, all data for the chunk besides the isEmpty flag is deleted and ignored, which reduces filesize. Empty chunks are never loaded, and locations where they occur are merely simulated as entities reside in them. The chunk will only load when something requires saving inside it.[/spoiler]

Changes to terrain, ores, etcetera:
[spoiler]Terrain:
By default, nothing will change. Small bits of terrain generation code need to be reconfigured to work properly with Cubic Chunks.

Biomes:
By default, nothing will change.

Ore generation:
By default, nothing will change.

Structures:
By default, nothing will change.

The Void:
After conversion to Cubic Chunks, the void and bedrock layer will still exist and generate as they always have. However, the void(Not the bedrock layer!) will not exist as a hard limit and is able to be moved, but not removed, by editing an associated NBT data tag inside a world's level.dat. This feature, that allows for increasing the maximum depth, is intentionally disabled without external programs, to prevent terrain change of any sort. It is intended to be used by experienced mapmakers and world generation mods only.

Superflat settings:
Existing superflat worlds will not change. However, new superflat worlds will gain a new decoration parameter, 'void'. Inclusion of this parameter will cause the void to form below the lowest defined layer. Exclusion of it will cause all layers below the lowest defined layer to copy the settings of that layer.[/spoiler]

Coping with sunlight:
[spoiler]There used to be a solution here, but it wasn't deemed good enough by Jeb. Suggest solutions in this thread.[/spoiler]

Changes to servers:
[spoiler]Settings:
There's a setting inside the Server.properties file called 'max-build-height'. The setting makes it impossible for any player to place or remove blocks above that height.
With the implementation of Cubic Chunks, a new setting named "maximum-generation-depth" would be added. The void, bedrock layers, and magma layers will generate normally at and above the Y level designated by the value of this setting.

Chunk occlusion/exclusion:
Using the raytracing methods already available in the code and used for explosion calculations, servers can identify which chunks are visible to a player, within safe assumptions, and only send the data for those chunks. This both reduces bandwidth usage, and cripples the usefulness of X-Ray cheats.[/spoiler]

Render/Load distance alterations:
[spoiler]After the implementation of Cubic Chunks, view distances' radii will apply to the vertical axis too. This reduces handled blocks in the cases of tiny and short render distances, and increases them in the cases of normal and far render distances. This can be optimized by utilizing a spherical render distance instead of a cubic one, which would reduce handled blocks in all distances except Far.[/spoiler]

---

Frequently Asked Questions:

[spoiler=FAQ]Q: This is impossible.
A: No it's not. See below.

Q: Is this available as a mod?
A: Not yet! But it will be!

Q: I like X-ray! What if I don't want it to be broken?
A: First of all, breaking X-ray hacks will only be possible to do in multiplayer. That said, the system that would break X-ray would be possible to disable by the server owner. If the owner doesn't disable the system, then they don't want you using X-ray, and you should not be doing what the server owner doesn't want in the first place.

Q: I play on a PvP/Anarchy/Raid/Faction server. Won't this system let people pillar up into the sky and create a base thousands of blocks in the air and never be found?
A: No.

Q: I like Minecraft's current height limits. What if I don't want to have an infinite sky or infinite underground?
A: If this system is added, all worlds will not automatically gain an infinite underground. As stated below, the Void will remain in all worlds, even after the conversion to Cubic Chunks. The ability to remove the Void will simply be there. As for infinite space in the sky, the current build limit is over one hundred blocks above any terrain that vanilla Minecraft can possibly generate. It is ENTIRELY your decision on whether or not you take advantage of this height. If you play on a server, like stated above, the server owner can set a maximum build height. If s/he doesn't, then don't play on their server - you don't play on servers where the server owners allow things you don't like. Why would you play on an anarchy server if you hate being stolen from and killed?

Q: Will this affect Redstone at all?
A: No. This system will simply make it possible to make larger redstone circuitry than before.

Q: Won't this break existing worlds?
A: No. Existing worlds can be easily converted by dividing each MCRegion file into 4 pieces, then slicing the existing 256 block-high chunks inside them into 16 individual chunks.

Q: Won't this affect mods? Won't mod authors have a hard time updating their mods?
A: The answer to this question depends solely on the answer to the following two questions: Do parts of the modification code rely on chunk data/metadata? Does the mod author want to take advantage of the features of the new chunk system? If the answers to the first and second question are both "No", then updating a mod to this system should be very easy and quick. If the answer to the first question is "Yes", then those parts of the code will need to be rewritten somewhat, but in most cases, the changes should be fairly quick and easy. The only time that it should be hard to update a mod to this system, is if the answer to the second question is "Yes".

Q: Won't this require a total rewrite of the mod API if that's released first?
A: No. Whether or not even a small part of the mod API needs to be rewritten depends on the way that it is implemented and whether or not there are API inclusions for chunk handling and other chunk-related behavior.

Q: Could a player fall into unloaded chunks if chunks aren't loaded fast enough?
A: No, they could not, and for several reasons. Minecraft has a terminal velocity, though it might not seem like it. This velocity is slower than it should take to load new chunks below the player. In cases with exceptionally slow computers, even if the player did manage to reach an unloaded chunk, their fall would be paused until that chunk can be loaded.

Q: What would happen when water, sand, or a mob falls into an unloaded chunk?
A: Nothing. The water/sand/mob would freeze in place until the chunk is loaded and it can continue moving. You can already see this same thing happening on the horizontal axis.

Q: What will happen to the Void?
A: It will still exist, along with all its effects. The only difference is that the Void is no longer a hard limit and it can be moved. After the conversion to Cubic Chunks, the Void's location will be stored in a world's ' class='bbc'>level.dat, and this location can be changed with NBT editing tools. When and where the Void exists, chunks will cease to generate.

Q: Will this affect terrain?
A: No. However, terrain generators will gain the ability to use infinite height.

Q: Will this affect ore generation?
A: No. Ore is a part of terrain generation. As stated above, terrain will not be changed.

Q: Won't all current terrain generators be incompatible with this system and need to be rewritten?
A: No. Terrain generators work independently of chunks. When a chunk is generated for the first time, it calls the terrain generator and receives a specific section of the resultant terrain to save inside itself. Because of this, some custom terrain generators can generate steep terrain all the way to Y256, where you can experience a large, flat cut-off. Since there are no chunks above Y256 to call the terrain generator for terrain, no terrain exists there.

Q: What would happen if there's a huge solid ceiling so far above you that it is unloaded? Wouldn't you just see the sky, just with everything being completely dark?
A: Yes. This already happens on the horizontal axis, and it is an issue with sky rendering, not this chunk system. As such, this has nothing to do with this suggestion. Please do not post about this.

Q: If you go deep underground, will your plants grow/ores smelt/animals grow?
A: No, because those chunks would be unloaded, just as if you had walked far away. This is a flaw with any chunk system, regardless of shape. It is a necessary evil that allows Minecraft to have infinite worlds. The only way to fix this would be to introduce a separate new system that works with chunks as they are loaded and unloaded. This suggestion deals with the chunk system itself, and not sister processes. Because of that, that is outside of the scope of this suggestion. Please do not post about this.[/spoiler]

---

[WIP] The Cubic Chunks Mod! (Tall Worlds Mod):

Cuchaz has taken it upon himself to bring us the glorious Cubic Chunks, since Mojang refuses to do so.

Cuchaz is using a API of his own creation to help assist in the making of this mod, and he's quite far along, as seen in these two tech demo videos:
[spoiler=T-Demo 1: Vertical chunk loading][/spoiler]
[spoiler=T-Demo 2: Broken height cap and no lag!][/spoiler]
With the basic functionality in place - a complete overhaul of the basic chunk system, and height limit removed - this whole concept can already be considered proven. What remains is making sure everything else functions correctly under the new chunk system. In any case, stay tuned for future updates if it interests you(If it doesn't, then you are the weakest link - goodbye!).

You can follow the mod's development in much more depth in its very own topic!

---

Gallery:

[spoiler=A mountainside with an experimental engine using Cubic Chunks designed by Nocte. 960 block view radius, and 30 FPS.][/spoiler]
[spoiler=A different view of the mountainside with the same engine by Nocte. This time, with 1600 block view radius and 15 FPS.][/spoiler]
[spoiler="A video demonstrating Nocte's engine."]

---

Support & Submission to Mojang:

If you support this, hit the rep button in the bottom-left corner of this post. It is the only good way of accurately measuring support here.

If you wish, you can put the following banner, courtesy of laz2727, into your signature. It helps to attract support from all parts of the forum!

 [url=http://www.minecraftforum.net/topic/1707097-cubic-chunks-infinite-height-elimination-of-x-ray-and-more-60-supporters/page__st__0][img]http://img833.imageshack.us/img833/443/hov.png[/img][/url]

Please help us get word out of this suggestion! Share this with your friends, with Minecraft celebrities if you're familiar with them, or even with Mojangsters like Jeb or Dinnerbone! (Do not share this with Notch. Notch doesn't work with Minecraft anymore.)

The purpose of this suggestion is to have Cubic Chunks implemented in Vanilla. Being available as a modification does not fulfill that purpose. The modification featured in this suggestion is to act as a proof-of-concept only(Note: Its being featured here is to act as a proof-of-concept. The modification itself is on its way to becoming a fully fledged modification).

---

Special thanks:
Cuchaz, for taking Barteks' proof and running with it, to give us a truly functional Cubic Chunks mod.
Barteks2x, for updating the Cubic Chunks mod to 1.6.2, proving that it is possible.
Azraile, for posting the original suggestion and allowing me to take ownership of it.
Nocte, for helping resolve flaws and designing Hexahedra.
MineCrak, for a large amount of valuable insight and enthusiasm into the topic of Cubic Chunks.
aaronfranke, for helping resolve flaws.
PanJouda, for creating the original banner.
Flexico, for creating the predecessor to the current banner.
laz2727, for creating the current banner.
Robinton, for creating the original Cubic Chunks mod.
The_Watchman13, for answering all those stupid questions so I don't have to.

---

Note: Many calculations and information can be found among the many posts of this topic. There are too many for me to cite here, but if you wish, you can search for them yourself.

Quote from cocoaguy

Yay the FTB mod pack is out but noooooooooooo TC3 is not in the inital release (crying on keyboard) why do u try what pahimars doing do pre-releases whitch only have a small amount of the planed content but it still satisfied our cravings a little

Not really. The FTB launcher is out today. The modpack isn't. The modpack that comes with it is just an interim modpack containing the mods that are ready to use.

Quote from iamamodder

will thaumcraft 3 be thaumcraft 2

Shame they don't teach algebra in schools.

				  thaumcraft 3 thaumcraft 2
((thaumcraft 3 = thaumcraft 2) = (------------ = ------------) = (3 = 2) = false
				   thaumcraft	 thaumcraft

Where's MathML support when you need it...

yep, its true. a Graphics Processing Unit in minecraft.
currently it runs paint, so you can draw shapes. and unlike all other paint in MC things, this one allows for not just dots, but dots,lines,hollow and fulled boxes! my paint even has a cursor, 4 dots showing the area of selection, to prevent you from acidentaly drawing a shape! (dounload link at bottom of post)
note that this is a GPU, so if you hook it up to a strong enough CPU, you can play games like snake!
video of it running paint:(in the beginning i show the info signs, then i draw shapes, then a liiiitle peak at the size!)
how it works(the GPU):

Quote from specs: »

functions:
draw pixels
vertical line
horisontal line
box (filled)
wireframe box(requires 2 ticks/operations)

memory operations:
enable/disable ram (this stores what it looks like, every draw function adds to this "canvas") (turning it off will make images live, not needing a clock)
write to ram(the current drawing)
clear ram

the inputs:
X1
Y1

X2
Y2

function select
ram function/state select

pics!:(warning: from old standalone GPU!






instructions:(old)
1put in vars(where spawn)note: this is in binary, 1st one=1 2nd=2, 3rd = 4 to get 5, use 101.
use minecart to get to the piece on the side
enter operation code(with torches) combinations:
-01= draw line(i think horisontal)
-10=draw line(i think vertical)
-11=draw filled cube
-00= draw dot(pixel)
next, enter memory commands.
if you wish to use ram, make sure its not off and turn "listen" on, then off.
otherwise,turn off ram and keep listen on
ride the minecart to the screen and stare at the epicness.

i whud appreciate it if you listened to the following

DO NOT DISTRIBUTE

DO NOT COPY

DO NOT CLAIM

new: DO NOT COMPLAIN ABOUT THIS...THING(it is seriously of-topic and annoying)(this isnt too serious,wont get u baned(well,that is the mods choice,not mine))

what this means:
this is simply to prevent some moron from copying my precious work. i hate that guy...
not mutch to worry about, only worry if you are planning to do the things listed.

also, this is NOT a copyright, just something to scare away copyers. seriously.

the download link(just the GPU fore the advanced ppl: only click if you have read the above!


an example running paint!this link is recomended.trust me, this paint thing is VERY fun.
comes with signs with operationg instructions(note: horisontal/vertical is the other way round), but read this post a bit too for a better understanding. only click if you have read the above!