Update: I fixed a few parsing bugs.
Heyo, I just finished up on the main functions of my rom loader so I thought I should share it here.
It isn't the fastest thing in the world, as it can only go as fast as minecraft can process commands+text. Nevertheless, it is faster than doing it by hand!
How to use:
1) Open the MCRomWriter folder and make sure that in the folder there is:
MCRomWriter.jar
config.txt (With your rom's configuration saved in it)
source.txt (This file should hold the binary data you want to write)
2) Open MC, and stand at your writing coordinates, according to how you set up your config file (writing is done relative to your position).
3) Go back to the MCRomWriter folder and double click the jar. There is a 5 second wait before the process starts.
4) Switch back to the MC window, and unpause the game. Wait for the writer to start. DON'T TOUCH ANYTHING AFTER THIS
5) ....
6) Profit.
[video=youtube]http://youtu.be/ZTHjz9Cp0k0[/video]
--------------------------------------------------------
It uses java's Robot class to simulate keyboard presses, and types /setblock commands into your active minecraft window. You simply run it and switch to your minecraft client within the 5 seconds I set it to delay for.
Due to the fact that keyboard presses are sent directly to the active window, you can't do anything with your computer until the thing's done passing the data. I recommend running this in a VM so you can minimize it.
You need to fill out a config file to tell the bot how to write to your rom. Here's an example config file:
That file is configured for your standard torch rom with 16bit words and that is 16 words deep and stacked up 8 times.
There is a full description of how to edit the config file in the attached folder.
------------------------------------------------------------
Included is the .jar and an example world with two different roms and the corresponding config files. (the roms have no decoders attached. They're just for show anyways)
Heyo, I just finished up on the main functions of my rom loader so I thought I should share it here.
It isn't the fastest thing in the world, as it can only go as fast as minecraft can process commands+text. Nevertheless, it is faster than doing it by hand!
How to use:
1) Open the MCRomWriter folder and make sure that in the folder there is:
MCRomWriter.jar
config.txt (With your rom's configuration saved in it)
source.txt (This file should hold the binary data you want to write)
2) Open MC, and stand at your writing coordinates, according to how you set up your config file (writing is done relative to your position).
3) Go back to the MCRomWriter folder and double click the jar. There is a 5 second wait before the process starts.
4) Switch back to the MC window, and unpause the game. Wait for the writer to start. DON'T TOUCH ANYTHING AFTER THIS
5) ....
6) Profit.
[video=youtube]http://youtu.be/ZTHjz9Cp0k0[/video]
--------------------------------------------------------
It uses java's Robot class to simulate keyboard presses, and types /setblock commands into your active minecraft window. You simply run it and switch to your minecraft client within the 5 seconds I set it to delay for.
Due to the fact that keyboard presses are sent directly to the active window, you can't do anything with your computer until the thing's done passing the data. I recommend running this in a VM so you can minimize it.
You need to fill out a config file to tell the bot how to write to your rom. Here's an example config file:
Code:
keyDelay 15
commandDelay 150
xyz_Rel_Pos_From_Msb 1 -1 -2
bitSeek -2 z
byteSeek -2 x
slideSeek -4 y
wordSize 16
wordsPerSlide 16
totalSlides 8
one minecraft:redstone_torch 1
zero minecraft:air
colon S;
tilde S#
underscore S-
That file is configured for your standard torch rom with 16bit words and that is 16 words deep and stacked up 8 times.
There is a full description of how to edit the config file in the attached folder.
------------------------------------------------------------
Included is the .jar and an example world with two different roms and the corresponding config files. (the roms have no decoders attached. They're just for show anyways)