No, its intentionally meant to limit vehicle size. The larger and more complex the vehicle, the more processing it is going to require. Offer several sizes of vehicle bay with exponential requirements, e.g. the first vehicle bay is a hollow square of Iron, and each subsequent bay is built out of a hollow square of Vehicle bays of the next smaller size.
@Jamespenny: Correct. I already explained how, with the concept of a "vehicle bay" in which you can build normally, but then using "use" on the bay will convert all blocks within it to an entity. Depending on the special vehicle parts you've got on there is what vehicle (or junk) it is. Placing the entity back in the bay opens it for construction again.
Umm. Notch actually tried something like this. AND it was not working right. It almost made him regret adding stairblocks. You really want it?
Adding new half blocks wouldn't be nearly as hard as when he initially added them. Notch would only have to copy and paste the code from the original stair block, and just make it accept a different material.
Now adding them into the map generator? No.
No. The current half-block code is complete ****. 2 byte format or gtfo. xD
@bidoof: The floating boats health should slowly decrease with movement, (just as a tool does with use) as the floating ore breaks down from being outside of its natural environment.
If you knew you wouldn't have repeatedly insisted that moving blocks have already be implemented unless you were trying to fool the others into believing something you knew was false. Either way, you're rude or dumb. Choose your poison, I suppose?
0
0
0
Double Ninja'd. Holy hell.
0
0
Literally or figuratively? Either way, +1
0
0
0
R35|_|17z 1 - 10 0f 4b0|_|7 25,640,000,000 f0r v* (0.48 53(0|\|dz)
EDIT: Sorry, i'm on Google intl-hacker language. It's readable enough nonetheless.
0
No. The current half-block code is complete ****. 2 byte format or gtfo. xD
0
0
0
0
0
0