There should be a jetpack item from Modular Powersuits that is attached directly to the power armour like all the other upgrades for it are. IC2's jetpack taping is unrelated to the rest of MPS and shouldn't really be supported for its power armour. Ultimate Reloaded didn't replace the tape recipe too, so all the recipes that appear use it are a little misleading in that they can't be used as the item (and therefore feature) is disabled.
Posts by Chocohead
-
-
Uh.. How would I craft the lappack if it's not available in IC2 Exp anymore..?
Uhhhh small oversight, although the Ultimate Lappack being made with an Energy Pack is almost as strange.
Why player takes damage when there is a radioactive item in inventory when a player is in gravi armor? (bad english i know=) )
with quantum armor this is not
It was
IC2 doesn't have an API for marking armour as radiation protective, that is planned to be added though
crashes with latest Ic2 release
estebes moved a pair of enums internally which has broken the tools, should be a quick fix
-
You definitely need the EJML-Core jar, IC2 is the one creating that every time Minecraft starts (which is a good sign up to the point that IC2 must be reasonably intact). If it's crashing still though like albijoe says we'll need to see what the crash report says before it's possible to help with it.
-
The newest version for 1.7.10 is here. So long as the extension is a .jar it doesn't really matter what Windows thinks it is opened by.
If it is crashing though the crash report would be helpful (and quite necessary) to be able to help further into why its crashing.You've downloaded the dev version instead of the normal one, replacing it with the one I linked should be all you need. -
You'll want to remove the old version when you add the newer one but otherwise yeah it's that simple. If the modpack is already using the new version it wouldn't have the April Fools switch still in. Theoretically so long as you've got a newer version than the server it would let you in.
Not that is should matter by now as it should have switched back on its own even with the old version.
-
That was last year's April Fool's joke, if you update IC2 it will go away immediately or you can wait until the third.
-
Also, I kinda guessed that this would be a rare request? On the TI Calc forum that I'm also on, there's ususlly an admin or two willing to do your bidding but that forum is active like 24/7
There's a need to move threads every so often, not normally something as drastic as going from support into addons though
-
Once again Speiger has looked but failed to observe. A little like me and the forum
First, you can make your own profiles! Just because IC2 happens to come with only two doesn't mean it's only limited to two. Any profile.xml files in a folder or a zip within an ic2_profiles folder in the root of your minecraft instance (ie the same place where mods, config, logs, etc. is in) will be loaded by IC2. Every file mentioned by the profile is positioned relatively to the profile.xml, so you can pick between organising everything nicely in directories and dumping it all into the root.
Second, a full profile XML is (currently) defined as
XML: profile.xml
Display More<profile> <!-- Profile name, used to tell different profiles apart --> <!-- Case intensively matched so aMaZiNg PrOfIlE is the same as this --> <name>Amazing Profile</name> <!-- Texture additions/changes, used to effectively shim a default extra resource pack --> <!-- Can be three different things: NEW which applies the normal experimental textures onto IC2 OLD which applies the old textures onto IC2 Path to additional assets which can be applied to any mod (just like a resource pack) From a resource pack's perspective the path points to subdirectories of the assets folder --> <textures>NEW</textures> <!-- Mechanics style, influencing things like energy storage, tiering and cells mechanics --> <!-- Can be either NEW for normal IC2, OLD for classic IC2 or BOTH for everything --> <style type="OLD" /> <!-- Individual JEI overrides for blocks, used to mask things --> <blocks> <!-- List of blocks to show in JEI, regardless of the style settings --> <whitelist> <!-- Blocks are listed via stack tags: --> <!-- Stacks are defined either via combined which is the IC2 ini format --> <stack combined="ic2:te#electric_furnace" /> <!-- Or split id, meta and NBT: --> <stack id="ic2:cable" meta="0" nbt="{type:0b, insulation: 1b}" /> </whitelist> <!-- List of blocks to hide in JEI, regardless of the style settings --> <blacklist> <!-- Format matches that of whitelist --> </blacklist> </blocks> <!-- Individual JEI overrides for items, used to mask things --> <items> <!-- Format matches that of blocks --> </items> <!-- Changes to recipes that use the vanilla crafting table --> <crafting> <!-- Changes to shaped IC2 crafting recipes --> <shaped> <!-- All tags are optional --> <!-- Use the recipe changes from another profile --> <!-- Can only extend from a single profile (right now at least) --> <extend profile="profile name" /> <!-- Extra shaped crafting recipes to add to those already loaded --> <additions> <!-- Changes can be file nodes which load additions from the given ini file: --> <file path="path/to/file.ini" /> <file path="path/to/file2.ini" /> <!-- And/or folder nodes which load all ini files in the given directory: --> <folder path="path/to" /> </additions> <!-- Shaped crafting recipes to be removed from those IC2 would otherwise add --> <!-- Can be done via the config, but that removes from all crafting/machine outputs --> <removals> <!-- Changes can be any of... --> <!-- Stack nodes which remove any recipe with that output --> <stack id="minecraft:stone" meta="5"> <!-- Ore dictionary nodes which remove any recipe with the given ore dictionary tag --> <ore_dict tag="oreStone" /> <!-- File nodes of specific recipes to remove --> <file path="path/to/file.ini" /> <!-- Folder nodes of files with specific recipes to remove --> <folder path="path/to" /> </removals> <!-- Shaped crafting recipes to be used instead of IC2's defaults --> <!-- Cannot be used in conjunction with any other extend/additions/removals tag --> <replacements> <!-- Format matches that of additions --> <!-- Note: Leaving an empty replacements tag will result in no recipes being added --> </replacements> </shaped> <!-- Changes to shapeless IC2 crafting recipes --> <shapeless> <!-- Format matches that of shaped recipes --> </shapeless> </crafting> <!-- Changes to IC2's furnace recipes --> <furnace> <!-- Format matches that of shaped recipes --> </furnace> <!-- Changes to IC2's macerator recipes --> <macerator> <!-- Format matches that of shaped recipes --> </macerator> <!-- Changes to IC2's compressor recipes --> <compressor> <!-- Format matches that of shaped recipes --> </compressor> <!-- Changes to IC2's extractor recipes --> <extractor> <!-- Format matches that of shaped recipes --> </extractor> <!-- Changes to IC2's ore washing recipes --> <ore_washer> <!-- Format matches that of shaped recipes --> </ore_washer> <!-- Changes to IC2's thermal centrifuge recipes --> <thermal_centrifuge> <!-- Format matches that of shaped recipes --> </thermal_centrifuge> <!-- Changes to IC2's blast furnace recipes --> <blast_furnace> <!-- Format matches that of shaped recipes --> </blast_furnace> <!-- Changes to IC2's block cutting machine recipes --> <block_cutter> <!-- Format matches that of shaped recipes --> </block_cutter> <!-- Changes to IC2's recipes in the metal former --> <metal_former> <!-- Changes to IC2's cutting mode metal former recipes --> <cutting> <!-- Format matches that of shaped recipes --> </cutting> <!-- Changes to IC2's extruding mode metal former recipes --> <extruding> <!-- Format matches that of shaped recipes --> </extruding> <!-- Changes to IC2's rolling mode metal former recipes --> <rolling> <!-- Format matches that of shaped recipes --> </rolling> </metal_former> </profile>All tags except name, style and extension can be repeated as many times as desired, and only name is technically required to define a valid profile (style and textures both default to NEW).
Additional profiles can be selected within the main IC2 config by their name as it describes (which you'll remember is case insensitive). Duplicate profile names will log a warning and continue to use the first profile registered with the name. If the profile in the config can't be found it will log a warning with all the profiles it has managed to load and will continue using the default (Experimental).
-
Looks like the wiki wasn't taking into account builds failing for links, should be fixed once the cache floods. In the meantime the links at the top of the forum all work.
The dev and api versions are just for mod development and shouldn't ever need to be downloaded/installed by normal users.
-
On 1.7.10 (so long as you're not using IC2 Classic or Uncomplication) the limits are always ignored, you can move as much power as you want using any cable you want. Any limits the tooltips might mention are effectively ignorable.
-
I did add a request in the shoutbox for this to be moved (I thought it would be more of a general thread, but it morphed into this, which then morphed into an addon :P)
Must have missed that
-
If you're using stock IC2 the power limits aren't enforced on 1.7.10 anyway. If you're using Classic or Uncomplication though I don't think there's an option to ignore it whilst still running with any other enet limitations
-
I checked that with the chamber, it returned true for has reactor, but nil for all the get methods, which was what prompted me to post that.
Most strange, if it has an attached reactor to get the values from it shouldn't have trouble doing it. I presume wrapping the reactor itself is getting valid values rather than nil too?
And how would I do the Lua table thing? I'm not really experienced with Lua
That was an idea for the addon to give you a table as a return value for a getReactorStatsesque function. Just a concept to allow much greater monitoring (if you were so inclined) without having to add dozens of individual functions. Although of course individual functions are friendlier to performance when being polled frequently.
-
You should really consider making a place where we can get all your tiny addons and such (like FullDrop and this one), they are REALLY useful!
I don't think I've made that many in the grand scheme of things. Normally it's just a need comes up for something small and I've got time to make it.
hen I wrap a reactor chamber, I can't get any outputs, when I call getEUOutput() on a chamber, I get nil, even though there is a reactor attached. Is it a bug, or 8s this my fault?
What's the result of hasReactor on the chamber? If it's managed to attach properly it should be true (otherwise that would explain why it wasn't getting anything else).
could you also make a method to get the tick remaining on the fuel rods? This would possibly be an average...
Given it's Lua you could get a table of stats like minimum remaining time, time remaining per slot, etc. Maybe that's encouraging micromanaging a little too much though?
-
It's worth noting that if you're not already comfortable with Java making an addon is made harder, as you've got to understand what Minecraft, Forge and IC2 are doing (to varying degrees) to get everything working as it is. Equally if everyone is suddenly into making reactor addons I can make an example mod just to give an idea of how things works; would be more about demonstrating what you need to do to work with IC2 rather than teaching Java but if there's interest I can get around to it.
-
The video was posted a little over a week before the pack was, and there were additional recipes changes between when it was recorded and when the pack was publicly released. Relying on the IC2 wiki using the default recipes therefore is not necessarily the best of ideas when the recipes have been changed (repeatedly) by the modpack; hence blindly aiming for iron plates for example might not actually be what you want to do. I'd strongly recommend looking at the recipes of what you are aiming to make to see how they have changed, rather than the individual components you expect to need (given that said components might well be different).
-
It's not IC2 adding these recipes as far as I'm aware, it is almost certainly Railcraft itself (especially if you're only using IC2 and RC). I would suggest making an issue on the Railcraft Github if this is actually the balance it is currently using given that it is certainly worth double checking to say the least.
-
I didn't make it public because if I did release it, idk about source code publishing rules for addons...
If you've written the class then you're very welcome to open source it, if you've copy-pasted it from IC2 however you shouldn't be making that open source (as it's not really your code
) -
I tentatively agree with the first part of this - in 1.7.10 a simple design with 1 uranium rod and 1 heat vent shows 8 HU/s output (in the reactor gui), but in 1.12.2 is shows 160 HU/s. I was hoping for confirmation from Chocohead, but he has yet to respond in the GitHub issue. Confirmation from someone else who has knowledge of IC2's inner workings for multiple MC versions would be nice - in-game testing doesn't entirely rule out the possibility that the output was buffed while things like HU to EU conversions were nerfed to match.
The fluid reactor output units have been an issue for a long time now. There is disagreement within the code too about whether the value is meant to be in HU/s or HU/t, fairly certain in one 1.12.2 build it was switched from ticks to seconds to account for the fact the output value was 20x too high despite the EU value being correct for being per tick. I'm not aware of any balance changes modifying fluid reactors that much, only the slight rationalisation of the steam boiler which could theoretically have changed the heat consumption rate of designs slightly to be more predicable. I'd presume if 1.7.10 was showing conveniently 20x less than 1.12.2, the 1.7.10 value is in ticks and 1.12.2 in seconds (which I think it is in game, would have to check though).
It seems that Chocohead only goes on the forum every day - He has not replied to anything in IC2 bug tracker for about a week.
I still check the bug tracker daily but often won't flag things unless I've actually looked into them in case someone else beats me to it. There's a collection of things that need fixing that FTB Ultimate Reloaded found too which will probably all get fixed together. Although some of the bugs on the tracker are easier to deal with than others.
-
Since I've seen a couple of requests for this might as well make it a little more official. Tiny ComputerCraft addon that means wrapping a nuclear reactor as a peripheral will now have the following methods:
-
getHeat - The current reactor heat
- getMaxHeat - The heat amount the reactor will explode if reached
- getRawEnergyOutput - The amount of energy the reactor is producing before converted to EU
- getEUOutput - The amount of EU the reactor is producing
- isActive - Whether the reactor is current running
- isFluidCooled - Whether the reactor is fluid cooled
Wrapping a reactor chamber offers all these methods, and hasReactor - whether the chamber can find the reactor it is attached to
-
