Serialising blocks & items references in 1.7

[Kinniken]

Hi,

 

I've started working on updating Millénaire to 1.7. Just a question regarding the new system of dropping item and block ids: how does that work for saving and transmitting references to blocks and items? Should I still use ids for that? That's what ItemStack seems to be doing in its readFromNBT method. Is there a guarantee that for the same world ids will be persistent across clients (in MP- and across saves and reloads?

 

Thanks

 

K.

[LexManos]

Serialization to IDs is pretty much garenteed to be consistant with FML's ID management system. When a Client connects to the server it is given the table of names<->ids and syncs it's internal table with that.

And same thing happens when loading a world, the world contains that table, and the client syncs with it.

So yes, serializing to IDs in network communication should be fine.

Serializing to ids on the world save should also be okay as long as the end user doesn't do something to screw up the mapping table that FML adds.

[Kinniken]

Sounds good, that's what I was hoping.

 

The one thing ID-wise that I was doing that no longer seems possible though is for Millénaire content makers to "register" new blocks and items for use by Millénaire via text files, by giving the id and a name for the item/block. Is there any other way to identity an item or block from an other mod?

[LexManos]

You interact with other mods by there block name that they use to register there block.

Example: minecraft:dirt minecraft:sandstone

You can query the block registry by name as shown in the net.minecraft.init.Blocks class.

[Kinniken]

Ok great, that solves it. Thanks.

[Kinniken]

I might be missing something obvious, but is there a way to get the item/block name (the minecraft:sandstone one) from the block or item object? It doesn't seem to get stored in the object itself and it does not always match getUnlocalizedName().

 

BTW, the new gradle setup is excellent. Very easy to setup and clean dev environment.

[Kinniken]

Well, I guess I'll make my own reference table then.

 

I have an other question regarding the life-cycle of the items and blocks objects - are they stable throughout a Minecraft run? With Minecraft only updating the ids if switching to a world that has a different ID config?

 

I'm asking because I'm in the process of switching the references in my Millénaire objects loaded at startup from using ids to using direct references to the items and blocks. Should that be normally safe across worlds? Or should I avoid doing things like this at startup and instead move it to the world loading events?

[Kinniken]

That's exactly what I was looking for, thanks!

[LexManos]

After all mods are loaded and initialized, yes, it should be completely safe across the rest of MC's run.

That is, unless a modder screws it up, in which case we can't do anything.

[Kinniken]

Indeed not.

 

Then I guess the proper way to do things will be to setup my own blocks and items in @Init but build up my datastructures in @PostInit. Works for me.

 

Now only 2000+ compilation errors to go through and I can test it