jakj

History with GregTech? I have nothing against the mod: I just use it as a touchstone for "holy shit hardcore" from what I've heard about it. If enough people are using GregTech and want a hardcore version using it, then I'll take a look.

Yes, Thermal Expansion (Induction Smelter, Magma Crucible, and Liquid Transposer) is my favourite, followed closedly by IndustrialCraft (Extractor, Compressor, and Macerator). People really don't take full advantage of these machines. So many people haven't even thought about the fact that the Liquid Transposer works on any combination of items, and it's not just for getting liquid in and out of containers. I have all kinds of recipes in my head, where you craft things together, then transpose liquid into them, smelt them (essentially boiling them), then transpose them back out to make a whole new liquid. Some day I'm going to work on a mod called "Emulsion", which basically lets you make liquids out of a lot of filler blocks like dirt, stone (no, not lava: a cool liquid), clay, and such, pour it into holes, and cure it, thus filling in the holes. Kind of like the BC filler except easier to setup and a whole lot cooler. (That's the future, though. Yes, there's a 90% chance that the hardcore mode will require other mods. If things keep going at the rate they're going, I figure I'll work on that mode in a few weeks to a month.)

1) You should move discussion to the actual release thread so it's easier to track. 2) That's basically what I'm going to do (except for all three axes of motion, since the carriages can move in all six directions), and hopefully it doesn't introduce any sync issues.

Adding a "hardcore" mode is on the table for the future, but only after the rest of the mod is fleshed out. Overpowered-ness is subjective, after all, and there's no way (that I know of) to use this mod to break blocks or otherwise automatically mine without the appropriate tools or other mods present. All this mod really does is move the blocks. The recipes might be super-cheap compared to a lot of stuff, but just wait until you decide to use a structure carriage to move your entire house, and realize how many trees you have to chop down to make the frame. In vanilla without any additional mods, that's a lot o' fuckin' wood.

Version 0.0.1.0 now available. http://j-a-k-j.com/RedstoneInMotion_0.0.1.0.zip Known issues: Blocks that schedule updates for themselves (like buttons) do not receive those updates after being moved. Forge information file (mcmod.info) not yet implemented. Blocks drop in creative mode. Some blocks in-transit are not yet rendered. Drives will not work on structure carriages when placed on an edge instead of a corner. Native-resolution texture option not yet implemented. ComputerCraft support not yet implemented. Omni-Wrench support not yet implemented. Recent changes (full list in "Changes.txt"): 0.0.0.0 -> 0.0.1.0 -- fixed a crash in WorldUtil . SneakySetBlock -- drives now indicate when they are active -- fixed some crashes related to missing tile entities -- improved shading during rendering of in-transit blocks -- added in-transit rendering for the following blocks -- (note: transparency (like for ice) will not be implemented) -- *) carriages -- *) carriage drives -- *) stone -- *) dirt -- *) cobblestone -- *) planks -- *) sand -- *) gravel -- *) gold ore -- *) iron ore -- *) coal ore -- *) logs -- *) sponge -- *) glass -- *) lapis ore -- *) lapis block -- *) dispenser -- *) sandstone -- *) note block -- *) wool -- *) gold block -- *) iron block -- *) brick block -- *) TNT -- *) bookshelf -- *) mossy cobblestone -- *) obsidian -- *) diamond ore -- *) diamond block -- *) crafting table -- *) farmland -- *) idle/burning furnaces -- *) redstone ore -- *) ice (no transparency) -- *) snow block -- *) clay block -- *) jukebox -- *) pumpkin (without stem) -- *) netherrack -- *) soul sand -- *) glowstone -- *) jack 'o th' lantern -- *) stone brick -- *) melon (without stem) -- *) nether brick -- *) end stone -- *) unlit/lit redstone lamps -- *) wooden double-slabs -- *) emerald ore -- *) emerald block -- *) command block -- *) redstone block -- *) nether quartz ore -- *) nether quartz block -- *) regular torches

There are two types of drives: "Carriage Engine" which moves with the structure, and "Carriage Motor" which stays where it is but cannot push blocks away from or toward itself. In your example, Carriage Motor would work fine because it's to the side and moving them up/down. If you want to replicate Redpower frame behaviour, you want to use Frame Carriage: They will connect to single blocks on their sides, and not beyond that. Using a screwdriver on their sides will open/close that side: This is exactly like putting covers on Redpower frames. In your example, you'd just use a screwdriver on all those sides (which will be a lot of clicking, but still easier than placing covers was by a margin). A closed side will not connect to anything, although an Engine/Motor can still move it just fine even if the side touching the drive is closed. I actually never used RP frames: I just saw them used in videos. Since you have experience with them, I reocmmend just trying to use Carriage Motor and Frame Carriage and seeing if it works. I intend that combination to be 100% accurate to the old RP frames, so if it's not, report it as a bug. The other types of carriage and drive give functionality beyond what RP offered.

I'm using a tile entity instead of a regular entity, which provides easier and simpler sync. I am serializing TE data during motion. I am bypassing block updates until all blocks in the group are set, then running them all at once. The first thing I am going to try is to read the positions of connected entities at the start and set them once per tick to their new positions. If sync becomes an issue, I will begin to examine the minecart code. The first way is better, though, if it ends up working. I can't mark the player entity as a child since I'm not making an entity. I could create a fake entity though if needed. Prefer to not make a chair since it restricts mobility and changes the player's pose. Do note that I'm not trying to recreate that Ugocraft thing: That is more a combination of airships and hangar doors. I'm thinking about eventually allowing you to use the structure carriages to package up a block of the world as an item, take it somewhere else, and redeploy it, but I'm not going to make it like actual rideable airships with motion controls. Someone else is free to take my code and do that if they wish, but it would have to be refactored to be a regular entity instead of a tile entity.

Yes: The only added block accesses from the current method would be putting the placeholders in the spots the carriage is moving to, that previously were air. Right now, it leaves them as air (does nothing) and then sets them when the carriage is finished moving. Actually, wait...sand/gravel couldn't fall in those situations anyway, because it already would have fallen through the air. And we don't care if it falls through places where the carriage is leaving behind air. So...I can put placeholder blocks anywhere the carriage is going to move -to- that wasn't already air? That would add no extra block accesses at all. Then again...adding the extra placeholder blocks -would- allow better collision detection, especially if the player is standing at the very leading edge of the platform as it moves. Placeholder blocks would allow there to be a steady floor there. Hmm........... Then again again, let's say the player is standing on the carriage, and instructs it to move upward. Adding leading placeholder blocks would actually embed the player in one to the waist. I'm going to let this percolate in my mind for a while. If you think up any additional points, I can factor them in.

That's another option. Yet another option is to put placeholders only in the final positions but still put air where blocks are vacating, which would reduce the extra block-access count to half. That would mean a properly-roofed mining machine would have the sand just slide along the roof until the machine is past it, and then fall. It would appear to fall through the carriage if things update quickly enough, but it couldn't fall into a position that'd be occupied by a new block. Checking specifically for gravel/sand sounds like a good idea, until you think about also having liquids flow downard during transit, as well as having to add every mod block that also is a liquid or falls. I'm thinking placeholder blocks is the only solution that can (in theory) handle every contingency without having to maintain yet another list of exceptions.

Hmm, that is a good point, but examining the code of BlockSand shows that it simply checks for air/fire/liquid below itself in order to fall, and doesn't check for collision with an entity. The only way to prevent the sand/gravel from falling in that situation is to put down invisible placeholder blocks in every single spot. Maybe I should start considering that option. I keep rejecting it because it would slow down the entire process since changing blocks in the world is the most expensive part. (Using extra invisible blocks would add one additional block access for each coordinate that either has a block before but not after movement or has a block after but not before movement.) I'm told that Redpower used the placeholder blocks, though, so...hmm. As I say, I'll think about it. Maybe I should just do it, and see if it's too slow, instead of just assuming it will be.

I will experiment with the collision box to see if it will work for living-entity collision. Meaning, I should be able to make the player not able to walk through the blocks in-transit, but sand and gravel will fall regardless. (If you notice, even now, falling sand and gravel will bury a player, not just stop on top of their head.) The way it's done right now, there is no risk of falling blocks displacing the motive spectre and making your carriage disappear, because the placeholder block counts as solid and unbreakable. Nothing will stop the sand or gravel from being overwritten, though, if it lands somewhere the carriage is about to occupy. I just think that's too much of an edge case, and that people just need to take the consequences if they have sand or gravel on their stuff that isn't attached. (It's not like sand and gravel are rare, anyway.) I can add a "hardcore" mode at some point if there's demand for it, that you could select in the config. Other features first, though.

Never mind, I know what the button bug is. The block is scheduling an update but it's firing on the old position during transit. I can extract pending updates when pulling the blocks and re-issue them on completion.

Being able to stand on moving frames will come eventually but is of medium priority. Explain or screenshot the button bug in more detail. Rendering is coming along, and will be partially implemented in less than a day. Hit box soon after, thank you for reminding me. I can include a native-res texture option at some point. Blocks dropping in creative will be fixed as soon as I think of a cleaner way to do what I'm doing. I'll check the computers. That kind of thing is what needs testing most, finding the mod blocks that don't behave well after motion. Explain or screenshot the flowing water bug so I can track it down.

Also, immibis just started a reimplementation of redpower wire and logic circuitry if you don't like the mfr style .

Yeah, that's just crashing because the block disappeared mid-transit. If you're not in creative mode, it's unbreakable, so that's another "don't do that". It won't corrupt anything.

Did you use the screwdriver to put the engine in continuous mode? If so, that's supposed to happen. If not, I'll need a screenshot of your setup. You're not breaking the lever: You're in creative mode, and you're breaking the invisible block that holds the block data as the carriage is moving. That's exactly what's supposed to happen: When the carriage begins moving, empty air is left behind, so the sand falls through the empty air, since the top sand block is not connected directly to the side of a frame carriage. To fix that, I could replace everything with fake invisible blocks during transit, but then I'd have to remove them again when transit is finished. Changing blocks in the world is the #1 slowest part of the entire operation, so I don't think making the whole process slower is worth making sand/gravel/liquids behave a little better. For now, I'll just have to say "don't do that". Damn, I was hoping I would be able to leave that null-check out for consistency. I'll have to check deeper into the code to make sure that doesn't happen again.

You'll have to provide a screenshot of what you're trying to do, because I can't reproduce this. Remember that Frame Carriage blocks attach only to blocks directly touching them, though, so if you have one sand block on top of another sand block but the top sand block isn't touching a Frame Carriage, it will be left behind (and therefore fall down). In that situation, you'd want to use either a Platform Carriage (which will keep looking for blocks to move until it finds air) or a Support Carriage facing up (which will move everything in a direct line out from it, so in that case, it'd move everything in one vertical column).

Oh, I'm sure I'll hook into it at some point. I'll put it on the to-do list to remind myself, though.

The first beta release is here! Please move all discussion to this thread: http://forums.technicpack.net/threads/1-5-x-redstone-in-motion-redpower-frames-0-0-0-0-june-16-beta.47048/ I decided to simplify the mod: Tiers are now gone. The screwdriver is now required to maniuplate carriages and drives; Sneak-activating with an empty hand will no longer work. CC peripheral support not yet implemented. I removed the tiers because I feel that the mod should be focused more on what you can do with the frames than any sort of balancing factor of making using frames more difficult. I want to see interesting and complex structures unhindered by difficult materials or energy management.

A reimplementation of Redpower frames, with more flexibility and functionality, and including many new types of frames. The information in this main post is woefully out-of-date, so read the changelog in the .zip file to understand the new features since the 1.1-ish releases. Documentation of this mod will switch to an easier-to-manage wiki at some point in the near-ish future. Wiki-in-progress (just a bit over half done, right now) is here: https://github.com/jakj/Redstone-In-Motion/wiki/_pages POST BUG REPORTS IN THIS THREAD, NOT ELSEWHERE ON THE SITE. 2.3.0.0 - MC 1.6.x https://www.dropbox.com/s/iriq2spgf4vblo8/RedstoneInMotion_2.3.0.0_mc1.6.zip http://j-a-k-j.com/RedstoneInMotion/RedstoneInMotion_2.3.0.0_mc1.6.zip 2.3.0.0 - MC 1.5.x https://www.dropbox.com/s/0tgr1vl7rsnwzxo/RedstoneInMotion_2.3.0.0_mc1.5.zip http://j-a-k-j.com/RedstoneInMotion/RedstoneInMotion_2.3.0.0_mc1.5.zip Older Versions http://github.com/jakj/Redstone-In-Motion/wiki/Releases SPOTLIGHT VIDEOS IceDrug20 (August 14, 2013) MrTheWhiteShadow (August 5, 2013) Neo39 Gaming (July 29, 2013) (French) SilverContrail (July 7, 2013) VIDEO DEMONSTRATIONS Playlist: Frame Carriage Demonstration Platform Carriage Demonstration Structure Carriage Demonstration Support Carriage Demonstration Template Carriage Demonstration Demonstration of Engine, Motor, and Controller Demonstration of Some Neat Stuff Demonstration of Rendering Update Translocator Test AVAILABLE TEXTURE SETS (all included in main download) (The active texture set can be chosen by editing the configuration file before opening Minecraft.) Default 256x textures: 16x textures by cubemelon: 16x textures (with support for colourblindness) by JustHev: 16x wood-style textures by uberifix: 16x metal-style textures (with support for colourblindness) by uberifix: 16x Dynasty-based textures by Lethosos: LICENSE All artwork pulled from other sources is licenced under various open-community licenses and is attributed and redistributed inside the texture directories. All original work by me in this project is licensed under the WTFPL (http://www.wtfpl.net/). The full license text is located in the file "License_WTFPL.txt". The following are ENCOURAGED (that means just do it and tell me afterward; don't bother asking first): Usage of this mod both publicly and privately. Distribution of this mod in both public and private modpacks. Usage of this mod on servers both public and private. Alteration and modification of this mod. Linking to and discussing this mod elsewhere on the Internet. The production of videos (such as Let's Plays and Spotlights) including this mod. Everything else. The following are DISCOURAGED: [This space intentionally left blank.] The following are PROHIBITED: Claiming this work as your own without first changing its name to make it clear your changes are your own and not mine. RECENT CHANGES (full list in "Changes.txt"): Carriage frameworks are the base item for crafting carriage blocks. The screwdriver is the tool used to manipulate carriages and carriage drives. It does not take damage when it is used, so it will last forever. It is used for opening and closing the sides of carriages, and for turning on and off the continuous mode of carriage drives. You can open/close the carriage side opposite the one you are actually using the screwdriver on, if you are sneaking while you use the screwdriver. This is useful when you place a carriage against another block, and can't get to that side to use the screwdriver on it. Frame carriages act just like the Redpower frames used to: They will connect to any block that is directly touching one of their sides, and nothing else. This allows for precise control of exactly what is picked up and moved. To prevent a frame carriage from trying to pick up blocks on a particular side, use the screwdriver to close that side. Platform carriages act like frame carriages, except they pick up not only what is directly touching them, but also anything that is touching those blocks, and anything touching those blocks, et cetera, until it reaches empty air (or it finds more than 5000 blocks to move, which is its maximum, to prevent trying accidentally to move an entire continent). To prevent a platform carriage from trying to pick up blocks directly or indirectly connected to a particular side, use the screwdriver to close that side. Structure carriages are rather special: If you place them in a cuboid wireframe (eight corners and twelve edges) around anything, they will pick up the entire structure inside that cuboid region and move it. Effectively, this lets you move your entire house elsewhere. For the structure carriage to function properly, all sides of all carriage blocks must be closed except for the sides touching other structure carriages. To make this easier, using the screwdriver on the side of a structure carriage will properly configure the sides of the structure carriages in a straight line out from the one you used the screwdriver on. That means you need to use the screwdriver only twelve times to configure a structure carriage. Image gallery of how to configure a structure carriage: http://imgur.com/a/jFySc Support carriages are also a bit special: They can be only one layer thick, and they can all have only one side open at a time which for the entire support carriage must all be the same side. In the direction of the open sides, the support carriage will support the entire structure it finds, all the way out to air (just like a platform carriage), except it is limited to the spaces in a straight line from any support carriage. This means if it's against a wall, it won't try to pick up that wall, even if blocks on the support carriage are touching that wall. Using the screwdriver will change which side is the open side, but they must be done one-at-a-time. Image gallery of examples of support carriages: http://imgur.com/a/xHEeh Template carriages are another special type of carriage: These let you lay out a block-by-block pattern with surgical precision, and thereafter will move those block positions (relative to itself), and only those block positions, never connecting to anything you don't intend to move. Place down template carriages in the shape you want to have blocks move, and place down a template carriage to serve as the anchor for future movement. (The entire assemblage must be contiguous to be recognized.) Use the screwdriver on the anchor block, and it will absorb all the other contiguous template carriages into itself, and its sides will close (showing its decoration if you have applied any). Now, just move the patterned template carriage block with any carriage drive, and watch the magic happen. If you break a patterned template carriage, it will lose its pattern, so all patterns must be assembled in-place; The only safe way to move a patterened template carriage is via a carriage drive. Image galleries of how to configure and use a template carriage: http://imgur.com/a/nV970 http://imgur.com/a/ygZH1 Carriages of any type can be decorated/disguised to look like other blocks without otherwise affecting their function, in order to make carriages look prettier. Only closed sides of carriages will display with their decoration; Open sides will continue to use the normal texture for that carriage type. Any block of any kind (including blocks from any mod) can be used in this recipe, as long as the block doesn't rely on special rendering or embedded information for its appearance. Note that this recipe will work even for blocks that don't make any sense, such as torches, so be sure to experiment with your desired decoration before throwing away an entire stack of it. If you wish to change the decoration, just put it back in the crafting grid with the new decoration: You do not need to remove the decoration first. Decorations are removed simply by putting the decorated carriage block on its own in any crafting grid. Carriage motors are like the old Redpower frame engines, except they don't require any sort of fuel. Apply a direct redstone signal to the motor in any direction, and it will grab the entire carriage structure (determined by which type of carriage block was used) and move it one block in the direction opposite the direction of the redstone signal. So, if you want to move a carriage up, apply a signal from below, and if you want to move a carriage north, apply a signal from the south. Carriage motors cannot handle more than one signal at a time, nor more than one frame at a time: Only one signal and one carriage may be touching any of the six sides of the motor in order for it to activate. Movement takes one full second at normal speed: If you are experiencing lag of any kind (local or remote), it will take longer. During motion, all nearby entities (such as players, animals, monsters, ender crystals, minecarts, and loose items dropped on the ground) will be locked to the carriage and move along with it. If the chunk unloads and is reloaded, if the world is closed and reopened, or if the server shuts down and reboots, the entities will no longer be carried by the carriage, so you should not have something like a mobile chicken farm with an engine in continuous mode and no supervision. You can change which types of entities are grabbed by editing the config file. In normal mode, the motor will move the carriage one block, then wait for the redstone signal to be removed and reapplied. In continuous mode, the motor will keep moving the carriage block-by-block for as long as it is able, without any pause between, as long as the redstone signal is being steadily applied. Carriage motors cannot push carriages away from them or pull them towards themselves: Motors can move carriages only parallel to the side of the motor to which they are attached. Carriage engines are exactly like carriage motors, except they can move in all six directions, and they move with the carriage instead of staying put. Be careful! If you are standing on a carriage with a carriage engine in continuous mode, and you activate that engine, you will not be able to escape the carriage's grasp and you will not be able to stop the carriage's motion until it reaches the top of the sky or hits an obstruction. If you close the world and reopen it, or you log off the server and log back on, you will be free of the carriage's motion. You can also try to disable the continuous mode of the carriage's drive in-between motions; By default, you have 1/4 of one second of delay between motions in which to act. Carriage engines make it super-easy to create airborne contraptions, like the famous UFO of Direwolf20. You can have more than one engine to make it easier (so you aren't trying to signal all six sides of an engine alternately): Try having one engine for N/S/E/W movement, and one for U/D, or whatever configuration suits you best. Remember: Continuous mode is dangerous while standing on engine-driven carriages! Carriage controllers are a modified form of carriage engine/motor that interface with the ComputerCraft mod via its peripheral API instead of responding to redstone signalling. (If you do not have the ComputerCraft mod installed, these will simply not be available.) Controllers expose one command to ComputerCraft: "move". It has three parameters: Which direction to move the carriage, whether to actually perform the motion or to just simulate it, and whether or not to move the controller along with the carriage (meaning whether or not the controller is anchored). (Simulating the movement lets you check whether a movement is possible without changing anything.) Examples: 2.2.0.0 -> 2.3.0.0 -- fixed typo in config file ("BlockIds" -> "Block IDs") ** YOU NEED TO CHANGE THIS MANUALLY BEFORE RUNNING THIS UPDATE ## if you do not, the block IDs will reset to the default ones ## in your config file, look for the line that says this --> BlockIds { ## change it to this --> "Block IDs" { ** (sorry for the inconvenience, but I am way too anal-retentive to leave that wrong now that I noticed it) -- fixed bug with multipart blocks disappearing due to a change in Forge ** all version combinations of multipart/forge should work now ## subpart tick scheduling still isn't handled correctly though -- fixed bug with rendering template ghosts that span more than one chunk -- eliminated the caching of world objects for loaded translocators -- improved in-transit rendering of translucent things like liquids -- removed legacy conversion of item forms of decorated carriage blocks and labelled translocators -- redid the packet code to use tag compounds -- added slightly more redundancy to rendering code KNOWN ISSUES *-*-* THINGS THAT ARE BUGS THAT WILL DEFINITELY BE FIXED *-*-* Multipart blocks that need scheduled world ticks (such as buttons that need a tick to pop back out) aren't receiving their ticks properly. *-*-* THINGS THAT ARE FLAWS THAT WILL HOPEFULLY BE FIXED AT SOME POINT *-*-* Anything that already uses a display list to render will not properly render in-transit. When translocated, some entities (especially chest-carts) behave strangely, but nothing major (so far). *-*-* THINGS THAT ARE NOT BUGS BUT HOPEFULLY WILL EVENTUALLY BE FIXED *-*-* Portal spawners from iChun's "Portal Gun" mod do not yet work on carriages. Try finding some way (possibly using additional mods) to activate a portal gun directly instead. "Billund" blocks have been reported to be wonky when moved by carriages. Anything else that caches 'x/y/z' values for any reason (possibly some chunkloaders, likely anything that does teleportation) has a strong chance of misbehaving. These should be reported to me as bugs. *-*-* THINGS THAT ARE NOT BUGS THAT PROBABLY WILL NEVER BE FIXED *-*-* If you are using Optifine and get an error with the word "ConnectedTextures" in it, either disable connected textures in Optifine or disable/remove Optifine. ComputerCraft programs that are carried by carriages and interact with the carriage's drive, need to have a delay added to their "startup" program to give time for things to settle before trying to interact again. Try "os.sleep(0.1)", and increase that number if it still doesn't work. (The more overloaded your machine or Minecraft is at the time, or the more computers or turtles you have on the same carriage, the higher this number will need to be. Making the number higher than it needs to be is fine: Too much won't hurt, but too little will.) Computers on carriages that are running at the time of motion will reboot after motion, and run their 'startup' program. (Computers that are off at the time of motion will remain off.) If a carriage is moving continuously, and the continuous-mode delay is set to 0, tile entities (like chests) will not render properly after the first motion until the carriage stops. This is purely cosmetic, and does no harm. To prevent this, make sure the continuous-mode delay is greater than zero. (The more Minecraft, your system, or the server is overloaded, or the longer delay there is between you and the server, the higher this number will need to be.) PLANNED FEATURES *-*-* THINGS HIGH ON THE PRIORITY LIST *-*-* Redoing translocator labels and other things to use a GUI instead of trying to draw on the block. An optional "hardcore" mode involving tiered crafting and power consumption, for people who want this mod to be expensive to use. *_*_* THINGS TO BE WORKED ON LATER *-*-* The ability to prevent individual blocks/items from being registered. A config option to let a carriage treat blacklisted blocks as simple obstructions instead of completely aborting the motion. The ability to selectively whitelist/blacklist blocks in-game for each drive, in addition to the overall config-file blacklist. These blocks will always be treated as simple obstructions instead of completely aborting the motion, regardless of the setting in the config file. A form of "sticky carpeting" to allow finer control over where on a carriage entities are grabbed. Different styles of controlling player position during carriage movement, to try to allow more freedom. CRAFTING RECIPES peripheral.call("left","move",2,true,false) drive=peripheral.wrap("left") drive.move(3,false,true) For directions, 0 is down, 1 is up, 2 is north (-Z), 3 is south (+Z), 4 is west (-X), and 5 is east (+X). For the simulation flag, true is simulate (don't actually move anything) and false is don't simulate (actually move the carriage). For the anchoring flag, true is the controller will stay where it is, and false is move the controller with the carriage. If the command is not issued with correct syntax, or if the carriage is somehow obstructed or malformed, an error will be printed; If the carriage is not configured properly, the return code will be "false" and a plain-English error message; If the carriage is obstructed, the return code will be "false", a plain-English error message, and the X/Y/Z coordinates of the obstruction; Otherwise, the return code will be "true". If you want wireless control of the carriage, you will need to connect a computer with wireless support to the carriage controller and interface with the network in that way: The carriage controller does not natively interact with the network, acting only as a peripheral. In addition, if the controller is instructed to move with the carriage, the computer will not be able to command it again without also being moved, so in that case, the computer would need to be connected to the carriage (and have an appropriate "startup" program that will re-connect with the controller). ADDITIONAL NOTES You can blacklist blocks in the config file, to prevent them from being moved, in the standard ID:Metadata format: "88,546:13,1010:8". By default, bedrock is permanently blacklisted. The config file also specifies the maximum number of blocks that be carried at a time by platform and support carriages (default 5000). This is for safety, so if you screw up and it tries to move an entire continent, it will abort instead of blowing away every bit of your computer's memory. Servers can also set the maximum size of any carriage of any type, to prevent users from lagging the server by moving an entire mountain at once. The version number has four elements: "A.B.C.D". Put simply, A is the most important number, D is the least important number, and bigger numbers are newer. (If you don't care about the details, just skip the rest of this paragraph.) D is the "patch" index, as in a simple bugfix release that really doesn't change anything will increase this number. "C" is the "minor release" index, as in small changes that don't really break anything but are nonetheless more-significant than simple bugfixes will increase this number. "B" is the "major release" index, as in big changes like adding a new block type or reworking a major algorithm will increase this number. "A" is the "version" index, the most-important number, which in most software products would mean massive overhauls (for example, if you consider the original World Of Warcraft to be version 1.0, the release of Burning Crusade would be 2.0, Wrath Of The Lich King would be 3.0, and so forth), but for this mod just means "Minecraft bumped up a major release" (as in the change from Minecraft 1.5.x to 1.6.x). All feedback is welcome: Modders exist to make mods for the community, not fluff up their own egoes. I won't guarantee I'll implement every suggestion, but I will consider every suggestion, and whenever possible and practical I will include options for configuration to suit player taste. And if nothing else, it is an open-source mod, so if I won't do something you want me to do, try asking around and see if anyone else is interested in doing it. And do note that not all mod blocks are guaranteed to work safely with this mod. I will make every effort to make them work well, and you should report all non-working mod blocks as bugs with my mod for me to handle, but ALWAYS be prepared to either lose what you are moving or to cheat it back in if it gets lost, and always test a mod block (preferably in a testing world with cheats on) before trying to move something valuable in your main play world. I hope you enjoy playing with this mod, and don't be afraid to tell your friends about it too!

A snake's head is the part on the front before the uniform body starts, and a snake's tail is the part on the end after the uniform body ends and it starts tapering or has a rattle. You're loopy.

That's actually the interior of the slime without the outer gel. The only one that's whole is the magna cube, and I have an idea for that one.

First beta version now released. http://forums.technicpack.net/threads/1-5-x-essentia-vitae-soul-shards-0-0-0-0-june-15-beta.47018/ Please move all discussion to that thread.

First beta version now released. http://forums.technicpack.net/threads/1-5-x-essentia-vitae-soul-shards-0-0-0-0-june-15-beta.47018/ Please move all discussion to that thread.

My entry for competitor to Shadow Dragon's "Soul Shards" mod is here with its first beta release! POST BUG REPORTS IN THIS THREAD, NOT ELSEWHERE ON THE SITE. http://j-a-k-j.com/EssentiaVitae_0.0.0.0.zip LICENSE All artwork pulled from other sources is licenced under various open-community licenses and is attributed and redistributed inside the texture directories. All original work by me in this project is licensed under the WTFPL. http://www.wtfpl.net/ The full license text is located in the file "License_WTFPL.txt". The following are ENCOURAGED (that means just do it and tell me afterward; don't bother asking first): *) Usage of this mod both publicly and privately. *) Distribution of this mod in both public and private modpacks. *) Usage of this mod on servers both public and private. *) Alteration and modification of this mod. *) Linking to and discussing this mod elsewhere on the Internet. *) The production of videos (such as Let's Plays and Spotlights) including this mod. *) Everything else. The following are DISCOURAGED: [ This space intentionally left blank. ] The following are PROHIBITED: Claiming this work as your own without first changing its name to make it clear your changes are your own and not mine. Include FULL logs when reporting bugs. Don't truncate them in an attempt to help. Use pastebin or a similar service if necessary, or send them to me in a private message. Screenshots are also encouraged when appropriate. Known issues: Forge information file (mcmod.info) not yet implemented. Blocks drop in creative mode. Lighting on Tropaeum Mors has an unpredictable delay in activating. *) Eventually, the lighting should update. *) Sometimes, but not always, walking around the block while facing it helps to speed this process. *) If the lighting has not updated, Tropaeum Mors on the ground will not be shaded, and Tropaeum Mors drawn inside Essential Genesis spawners will flicker. GETTING STARTED General crafting items: 1 lapis piece surrounded by 8 nether quartz pieces -> 1 crystalline housing 1 sugar + 1 gunpowder + 1 redstone dust + 1 glowstone dust -> 4 modicum vitae 1 sand + 1 gravel + 1 clay block + 1 soul sand -> 1 granulated soul sand smelt 1 granulated soul sand -> 1 potentium vitae 1 modicum vitae + 1 potentium vitae + 1 charcoal -> 1 sothom spice 1 nether quartz block + 2 modicum vitae + 2 potentium vitae -> 1 luminescent crystal shard Tropaeum Mors: These are trophies (usually severed heads) that drop randomly from vanilla mobs. Heads drop more commonly from rare mobs, and less commonly from common mobs. An item is already being implemented to cause guaranteed trophy drops, to be included in a future version of the mod. The trophies can be placed on the ground in any of 16 directions, and can be rotated by sneak-activating them with an empty hand. They respond best to an axe. Combine 1 tropaeum mors with 1 luminescent crystal shard to get an attuned crystal shard to that mob type. Find a mob of that type in the world, use the shard on it, and you will take half of your current health or 2 hearts (whichever is more). The damage you take will charge the shard. The charge stays on the shard, so you don't have to do it all at once. A fully-charged shard becomes a vital crystal shard. Combine 1 vital crystal shard with 1 crystalline housing to make 1 essentium vitae. (This is the soul shard.) As you kill mobs (by any means, as long as you are credited with the kill), the essentium vitae charges up. The charge per kill depends on the rarity of the mob as well as its value. Once an essentium vitae is fully charged, it begins to shimmer and will accept no more charge. At this point, it must be upgraded with another vital crystal shard of the appropriate type to move it to the next tier. There are 8 tiers in total. You can craft upgrades for the essentium vitae that will make it gain charge faster, all the way to 1000% speed. Combine 1 crystalline housing, 1 sothom spice, 3 potentium vitae, and 4 of various materials to form the 7 tiers of upgrade, called "Sothom Core". Combine the cores with the essentia to upgrade them. Upgrades will be LOST when your essentium moves up to the next tier, so they must be reapplied. If an essentium has charge at the time it is upgraded, it retains that charge. Essentium vitae can be upgraded to the next tier and have a sothom core upgrade applied at the same time, if you so desire. Any essentium vitae that is at the top of any of the 8 tiers (meaning ready to be upgraded but not upgraded yet) can be turned into a monster spawner. All monster spawners can be disabled by applying a redstone signal. Surround 1 crystalline housing with 8 iron grates to make 1 essential focus. This is an empty mob-spawner cage, and can be used as decoration if desired. Combine 1 sothom spice with 1 tropaeum mors to make 1 essential impetus for that mob. To upgrade the essential impetus to tier 2, craft it with 2 more tropaeum of the same time, and so forth, up to 8 more tropaeum to upgrade to the final (8th) tier. To make the mob spawner (called "essential genesis"), combine 1 essential focus, 1 essential impetus, and 1 charged essentium vitae. The essentium vitae and the essential impetus must be the SAME TIER to craft successfully. Higher tiers of essential genesis have greater statistics: They spawn mobs more quickly, they attempt to spawn more at a time, they work in a greater radius, they allow the player to be further away, and they allow more entities to exist nearby at a time. The final (8th) tier will allow the player to be any distance away and still get spawns (as long as the chunk remains loaded). (No provisions are made to change Minecraft despawning mechanics: If the mobs are not killed quickly enough, they may rapidly appear and disappear.) The final tier will also allow the mobs to spawn independent of their normal requirements: Passive mobs will spawn without grass and in darkness, hostile mobs will spawn in daylight, nether-only mobs will spawn in the overworld, and so forth.