Sangar 92 Posted October 18, 2014 Share Posted October 18, 2014 The first beta of OpenComputers 1.4 is now available. There are relatively few gameplay changes, the main reason for the version bump is that the Java API has been cleaned up and expanded a bit, making it incompatible with the 1.3 version. This means combining OC 1.4 with other mods using the OC API will - in most cases - not work well until they update to the new API. There are no breaking changes on the Lua side. Lua programs should continue to work as they are. Even more imporant than usual, remember to make a backup of your world before updating. Seriously. Do it. For downloads see Curse. Modders: if you're using the OC API, please update the the new API at your earliest convenience. For most of you the changes should be relatively painless, and mostly involve adjusting imports due to a bit of refactoring. I tried to document most (all?) of the changes in this wiki article, which also provides information on how to adjust for each individual change. Players: if you know a mod that uses the OC API, please kindly ask the mod's author to update it, thanks! You might want to want to point them to the wiki article mentioned above. It should make updating a bit easier. VERY IMPORTANT No, seriously! The future of the world depends on you reading this part. Well. Your world. Ready? To future-proof things, the way blocks are handled internally has been switched around a bit in 1.4. This means all of the old blocks have to be converted to the new format. For blocks that are in the world this happens automatically. They should keep their inventory and other state information. All you have to do is make the chunk the blocks are in load once. For blocks in inventories, this also happens automatically if they are in a player's inventory. So if you have some OC blocks in chests or an ME system or so, pick them up once, then you can put them back. Keep in mind that this means you cannot downgrade to OC1.3, after loading your world in OC1.4, without losing converted blocks. So what did change? As mentioned, the Java API for one. This has relatively few immediate effects, but will allow for some much more interesting addons in the future. OpenComponents has been discontinued; it is now a part of OC itself. A few things have also been added. Note that recently naming was fixed, so some blocks' components might appear under a different name. They always should have, but I'm afraid there was a small implementation mistake that lead to them having a generated one (e.g. AE2's controller is now properly called `me_controller` again). As for additions, MFR's safari net content is now added to item stack info (unless it's a "mystery" one), and there's now a driver for AE2's export buses. And since this kind of falls into this category: instead of the "unlocalized name", the item stack converter now properly uses an items/blocks identifier (e.g. `minecraft:dirt`) for the name field, now. Power conversion has been reworked a bit. Different blocks now accept external power at different speeds. The exact rate is listed in the tooltips. This should encourage the use of power converters, for example, and will hopefully make it a little more clear which blocks accept external energy, and which don't. Note that access points now also require energy to send wireless message, regardless of the source. So if you have a "solo" one sitting next to a CC computer, you'll now have to connect it to some power. Execution limits have been reworked a bit. Previously the number of operations computers could perform was limited per component. Now they each have a "call budget" that is shared for all components. This makes some neat implementations such as pseudo-SLI (using multiple graphics cards for faster screen updates) less feasible (sorry, it was really cool!) but has the massive advantage of being overall more... consistent. The actual call budget also depends on the CPU installed in the computer now, so better CPUs actually mean faster computers now. More NEI integration. For many blocks and items their component API is now documented in an automatically generated NEI usage page. There's also an additional usage page for many blocks and items that documents their general use and behavior. Adapters have been reworked a bit when interacting with inventories / tanks. They now no longer can access these per default. Instead, they now provide an inventory slots for upgrades. The two upgrades supported for now are the inventory controller and the tank controller upgrades, which provide the functionality that was previously built-in. Eye-candy: disk activity is now not only indicated via sound, it also triggers a disk activity "LED" on computer cases, disk drives and servers. Click here to view the article Link to post Share on other sites
