Forge networked Block mapping suggestion

[AtomicStryker]

With forge (in theory) eliminating all interclass-incompatibilities there is another very major problem the bigger mods face:

 

Block IDs. If you install all major mods, you will most certainly experience some overlap, and already some mods (like Redpower) automatically (and unilaterally) remap their blockIDs.

 

 

Now what if Forge did the mapping - instead of each mod registering it's own BlockIDs globally, they register their needed BlockIDs with Forge (starting with 0, per-mod blabla). Forge then serves as provider for whatever BlockID is needed, and more importantly, what BlockID stands for what Block.

 

What's the use? If a client connects to a server, he gets a one-time transmission of what BlockIDs are mapped to what Block, thus forever eliminating the need to keep server (in some case even world) specific blockID configs.

 

Since BlockID's are the same per-mod, you wouldnt even need to transmit ALL Blocks, just the BlockID at which mod x's range starts.

 

 

 

Here's a simple example: Both client and server have 2 mods, derpcraft and herpcraft.

derpcraft used to occupy Block IDs {100,101,102}, herpcraft occupied {101,102,103}. There was a lot of problems with that, saves got corrupted etc etc

New process:

derpcraft and herpcraft both register mod-specific Blocks of IDs {1,2,3}. Forge serverside starts distributing Blocks at 100, and maps 100-102 to derpcraft and 103-105 to herpcraft.

If a client now connects, he gets a packet telling him: derpcraft: 100; herpcraft: 103. His client then maps 100-102 to derpcraft and 103-105 to herpcraft.

 

 

 

EDIT:

 

Sort of an automatic save converter would be needed aswell. When mods change and for example derpcraft suddenly demands 5 Blocks, forge could rework the world-savefile and move herpcraft's BlockIDs 2 up. And for this, some kind of structure in the savefile keeping track of what the mod-BlockIDs were last mapped to.

 

 

 

This is just a proposal though. If you'd rather wait for the 4k BlockIds to actually happen, then yell at mod makers to keep their shit apart .. i can work with that.

[OvermindDL1]

I think someone is already working on such a pull request, let me see if I can find it.

 

Yep I did, it was immibis, his pull request is at: https://github.com/MinecraftForge/MinecraftForge/pull/27

 

Perhaps commit on that, submit bug fixes or so on that, etc...  Would be a very nice thing to get. 

[gcewing]

This is an excellent idea.

 

I would further suggest that the id mapping should be kept with the world save. That way you can load someone else's world save in single player and get all the right mappings. And Forge could warn you if you are missing the mod corresponding to any of the mappings.

[OvermindDL1]

This is an excellent idea.

 

I would further suggest that the id mapping should be kept with the world save. That way you can load someone else's world save in single player and get all the right mappings. And Forge could warn you if you are missing the mod corresponding to any of the mappings.

It actually already does store IDs per world save in his pull request, it is still being finished.

[calclavia]

I totally agree with this. Maybe forge should also implement more block IDs so it would be a easy to adds more blocks than the limitation. (eg. 4096 fix)

[OvermindDL1]

I totally agree with this. Maybe forge should also implement more block IDs so it would be a easy to adds more blocks than the limitation. (eg. 4096 fix)

 

No, MC is already adding that and mDiyo already has a patch for it for SP.

[calclavia]

I totally agree with this. Maybe forge should also implement more block IDs so it would be a easy to adds more blocks than the limitation. (eg. 4096 fix)

 

No, MC is already adding that and mDiyo already has a patch for it for SP.

 

I thought MC 1.3 is going to add its own API? What would forge be when that happens?

[OvermindDL1]

I totally agree with this. Maybe forge should also implement more block IDs so it would be a easy to adds more blocks than the limitation. (eg. 4096 fix)

 

No, MC is already adding that and mDiyo already has a patch for it for SP.

 

I thought MC 1.3 is going to add its own API? What would forge be when that happens?

 

They are adding their own API in parts, the server part will be first, forge will still be useful for a long long time to come, especially since the API keeps getting pushed off.

[DarkGuardsman]

this is a very good ideal. Running a server one of the hardest parts are configs. If someone even has one setting off they will crash on connect, crafting or using a GUI. This usually scares players off from using mods or playing smp with mods. So I've  been working on in a few of my mods having the config changed by server packets. For example my ComeCloser mod controls render range of the player name. My original way of changing the range setting was with a config and with the mod version containing the config number. Now with packets i can send the range setting when the player logs in, and Since the render player name is called every update it will use the new setting. this way the player doesn't have to change the setting for range ever server he logs into.

    However, i don't think this would work with blocks since there ids are registered when the game starts. Unless someone rewrites the blocks to not be register till the player loads a world. This in mind a mod could be written that would get the config list from a server and send it to the player. Then backing up the old configs first, delete them and write over with a new temp list. The player can then restart his client and connect to the server with the correct settings. Once logged out the mod will then store the server list in a folder called "ServerConfigs/ServerName". Which can be retrieved latter if the player decides to restore the original configs.

  Another option playing on the same ideal is to redirect where minecraft looks for its mod configs to a new folder containing the servers configs. This way the player doesn't have to restart twice after switching the configs folder from the server.