1.7 brings almost no features to Minecraft and will probably be skipped by mod devs, that's my point of view.
1.7 brings almost no features to Minecraft and will probably be skipped by mod devs, that's my point of view.
That would be a bad idea. If you delete or add a mod, or change the load order, half of the item IDs in the game would change. Worlds would not be compatible from one copy of Ultimate to another, if some optional mods had been enabled on one of them. I can't see an easy solution to the block ID problem.Eventually, probably in 1.8, the old static numeric IDs will be removed and replaced with dynamic numeric IDs internally assigned as blocks are registered when the mod is loaded.
There'd be something to fix that for the modding API, or before that forge could figure it out.That would be a bad idea. If you delete or add a mod, or change the load order, half of the item IDs in the game would change. Worlds would not be compatible from one copy of Ultimate to another, if some optional mods had been enabled on one of them. I can't see an easy solution to the block ID problem.
1.7 sucks arse all it has is big flowers and some shitty mountains to stop easy traverse by horseback making the horse update shit.
Seriously all mods should be perched to release on 1.6 and stay that way at least till 1.8 because for the FTB community 1.7 is horseshit (you saw what i did there ).
That would be a bad idea. If you delete or add a mod, or change the load order, half of the item IDs in the game would change. Worlds would not be compatible from one copy of Ultimate to another, if some optional mods had been enabled on one of them. I can't see an easy solution to the block ID problem.
That would be a bad idea. If you delete or add a mod, or change the load order, half of the item IDs in the game would change. Worlds would not be compatible from one copy of Ultimate to another, if some optional mods had been enabled on one of them. I can't see an easy solution to the block ID problem.
I don't think I do. I'm a data migration programmer. Whilst I don't know all the specifics about Minecrafdt, I understand the principles of IDs, surrogate keys, metadata, relationships, cardinality, and persistence. I have a good instinct for when something is difficult. Of course there is always the possibilty that I am wrong, and that there is some trick that I have not spotted.You wrongly understand name/ids way work.
So if I enable one optional mod in a pack, and you enable a different optional mod, and then we each enable the other, our worlds will not be compatible? This is what I mean by "a bad idea".At _first_ mod load it get free ids for mod blocks/items and name/id mapping stored into world data and at next loads fixed ids used for mod block/items. It's just meaning that for 2 worlds and same mod will be used possible differents ids dependent from order adding mods to world.
Why it is bad idea?? Ids will be insternal data for world. Any mods configs will be must only block names use for any purposes. So from mods/user side will be totally not important what id assigned for block in specific world. Config still be compatible for worlds with same mods list independent from order mods adding to world in each world. This will resolve main problem with mod configuration and configs share: ids conflicts.So if I enable one optional mod in a pack, and you enable a different optional mod, and then we each enable the other, our worlds will not be compatible? This is what I mean by "a bad idea".
1.7 brings almost no features to Minecraft and will probably be skipped by mod devs, that's my point of view.
I don't want the IDs to be consistent just within a world. I want them to be consistent within a modpack, so that worlds created with a modpack will be compatible with other copies of the same modpack.Why it is bad idea?? Ids will be insternal data for world.
The only time I can think of that happening was with the 1.5.x Direwolf20 pack where a mistake was made in the block IDs.By the way.. for people who have been at this longer than myself. Is it worth waiting until 1.0.1 or 1.0.2 of the 1.6.4 modpacks before creating a new world? I assume most major bugs are worked out during the beta stages, but has there ever been a case where people have jumped on a new FTB modpack, only to find their world is buggy/missing features that cannot be fixed?
I don't want the IDs to be consistent just within a world. I want them to be consistent within a modpack, so that worlds created with a modpack will be compatible with other copies of the same modpack.
If server will send list assiged ids to block names before mods loading then local mods will get at loading and id requests exactly same ids as used at server side. Not important in like case order of load/enable mods at client side.If a server enables three optional mods, this suggeston of automatic ID assignment would mean that every user would have to enable the same threee mods in the same order. If you accidentally enable one of them first in the wrong order and load the game, then the wrong IDs will be assigned and you will have to re-install the modpack and start again and enable the right mods in the right order.
It's will be compatible. If ids mapping to blocks names wil be part of world then at mods loading it will be used from world assigned list. Modspack configs will not have any ids in to text. So will be not important what ids used in specific world.I don't want the IDs to be consistent just within a world. I want them to be consistent within a modpack, so that worlds created with a modpack will be compatible with other copies of the same modpack.
That's quite a big change. At present, block IDs must all be known when the game loads. This would require block IDs to only be definitively set when a world is loaded, and all that information has to be sent from the server every time a client logs in. I think it's a very silly suggestion.If server will send list assiged ids to block names before mods loading then local mods will get at loading and id requests exactly same ids as used at server side.
I'm not really worried about 1.7 packs any more. I accept that it won't be for quite a while. I'm just trying to work out what all this speculation about automatic block IDs is, as there is no basis for it whatsoever in what Mojang have said or done, CMIIW.Why are you worying about 1.7 packs when 1.6.4 aren't right now - you can make your own and it's stable but almost everyone is lazy and wait for someone do the work I will stay in 1.6 pack due to old laptop with 2 G of ram and on-board graphics.
That would be a bad idea. If you delete or add a mod, or change the load order, half of the item IDs in the game would change. Worlds would not be compatible from one copy of Ultimate to another, if some optional mods had been enabled on one of them. I can't see an easy solution to the block ID problem.
“You wrongly understand name/ids way work.I don't think I do. I'm a data migration programmer. Whilst I don't know all the specifics about Minecrafdt, I understand the principles of IDs, surrogate keys, metadata, relationships, cardinality, and persistence. I have a good instinct for when something is difficult. Of course there is always the possibilty that I am wrong, and that there is some trick that I have not spotted.
“At _first_ mod load it get free ids for mod blocks/items and name/id mapping stored into world data and at next loads fixed ids used for mod block/items. It's just meaning that for 2 worlds and same mod will be used possible differents ids dependent from order adding mods to world.So if I enable one optional mod in a pack, and you enable a different optional mod, and then we each enable the other, our worlds will not be compatible? This is what I mean by "a bad idea".
On the other hand, as long as it is an optional system, and basically a better kind of "auto assign", and as long as the existing manual ID assignment is still poissible, I don't have a problem with it. At present, compatible packs are possible. With fully automatic block IDs, they are not possible, and I would not like to see such a retrograde step. Better that something be difficult than it be impossible.
Let me clue you in... If every block from every mod had to be registered using the old system there would be no more new mods, ever. There are no more available blocks to cover all the mods.
Of course, nobody would ever load every available mod, but the fact that every Mod creator has to pick a range of IDs to use leads to the problem that was just remedied between unleashed and Direwolf's pack here on FtB... Duplicate ID use.
Let me give you a real life parallel. When the IP address system, now called IPv4, was created, it was determined that 32 bits would give all the addresses anyone would ever need. 32 bits = 4,294,967,296, minus a few for sub-netting overhead.
At the time. there were no personal computers. Address subnets were assigned to maybe a dozen University mainframe computers and an unknown number of military mainframes., but nowhere near 4 billon.
The last available address using this scheme was assigned in the late 90's, if I recall correctly, during the web boom. There was already an effort in place to create a bigger address range which was actually rolled out a year ago to replace IPv4... IPv6. This has a 128 bit range and a better management infrastructure to streamline various services unavailable when IPv4 was designed, such as Streaming Video/Audio, VoIP and e-mail. I cannot give an exact number right now because it overflows my calculator, but I've seen claims that it amounts to 16 addresses for every square centimeter of dry land on earth.
What did we do in the meantime? There are certainly more than 4 billion computers and other devices connected to the web...
We use local "public" networks, behind personal routers, that are reserved for personal use and not allowed outside the personal router. The router translates these to valid "private" addresses for use on the "internet". These routers are usually set up to assign IP addresses to new computers, because that's easier for John Q. Public. These private networks, and IPv4 in general, are slowly being phased out, allowing people and organizations to upgrade their infrastructure, much like Mojang is allowing Mod developers to do here. The new system will assign BlockIDs the way personal routers assign IP addresses.
As I understand it, Each client will maintain it's own internal Block ID registry, based on the order the blocks are loaded when the game starts up. Think of how DHCP and DNS work to make it easier for you to access the web. Think of each block as needing an address, like your computer needs an IP address.
When the game loads, it builds a database file, probably stored with the Saved World information. The records, if I were to build such a system, would include the Mod name and version number, followed by the Block name, then the first available numeric ID. This would allow the loader to check if that mod version had been loaded before. If so, it skips registration. If not it registers the new mod. Assigning the first available Block number works like DHCP automatically assigning the next available IP address to a new computer on the network.
In practice, this would emulate the process used in every computer, called DNS, or Domain Name System. In the computer, it allows you to access a website just by knowing it's name and not have to memorize it's IP address. Here it sees "minecraft:stone" and returns the numeric block ID to the renderer.
Each PC could have completely different ID registries, since they are completely client based.
Also, this system would allow Mojang to increase the total blockID count at any time, if needed, because the names would remain the same and who cares about what numeric ID "stone" has anyway?
Tl;dr:
The new system should free up what seems to be one of the major incompatibilities between Mods.