DarkholmeTenk / TardisModIssues

Contains the issues tracker for the private TardisMod
25 stars 8 forks source link

[Enhance] Carpenter's Blocks like functionality #533

Open LatentDesire opened 8 years ago

LatentDesire commented 8 years ago

Basically as the title suggests, if it would be possible to have functionality similar carpenter's blocks while inside the TARDIS.

The way I figure this working would be as follows:

After reaching a certain level (or as a separate upgrade, though levels would be preferred) unlocks the ability.

You would be able to use the sonic screwdriver in configure mode to put a TARDIS block (and/or stairs) in "accepting" mode. You then use the desired block on the said block and the block "melds" (aka uses and holds the block used while changing the texture) with it.

To change it back to the original, use the sonic screwdriver in dismantle mode. Block used is also retrieved.

DarkholmeTenk commented 8 years ago

This isn't going to happen because it requires tile entities for blocks and an optimised as hell rendering system, which is something that I have neither the time nor patience for, I'm afraid.

157 #144

LatentDesire commented 8 years ago

If I knew how to code mods, I'd try helping out with doing this. Maybe someday I will be thus knowledgeable.

Or maybe the dev on carpenters blocks is a Whovian and wouldn't mind sharing their expertise. Lol

AlienXtream commented 8 years ago

the other issue is that tile entities contribute to lag. the more there are the worse it gets

DarkholmeTenk commented 8 years ago

One of the biggest issues with this is becaus of the schema system. In MC blocks in the world are stored as numbers and there's a mapping per world which maps the numbers back to actual blocks. Carpenter's blocks can easily store the block as that number because that number never changes for the world. If I did that and saved it as a number then when you saved the schema and loaded it in another world you'd have the problem that you could end up with a completely block. So I'd have to store it as the actual block id, so instead of having 2 numbers (could probably be stored as 4 bytes), it'd have to be an entire block name (30+ bytes) per block. It's not a huge amount of data still, but it's annoyingly large and inefficient.

AlienXtream commented 8 years ago

So that explains why when i tried using carpenters blocks in a schema it just gave seemingly random results. Thats actually nice to know. I will say this though, my old (declined) proxy blocks would be an alternative to this l. Not saying to do it just saying it would be an alternative :p