Not strictly with NEI... it's the one where you feed the ThaumCraft ores through the extractor, and it does the normal ore > dust > slurry > solution > flakes process, then cook the flakes to get an "item" which should craft into TC shards/amber/quicksilver... but instead it just crafts into fire.
Not strictly with NEI... it's the one where you feed the ThaumCraft ores through the extractor, and it does the normal ore > dust > slurry > solution > flakes process, then cook the flakes to get an "item" which should craft into TC shards/amber/quicksilver... but instead it just crafts into fire.
OK, that means something else is editing my recipes, presumably deliberately to break them. Please list all mods and versions you have, and post a copy of your loading log (set to maximal logging).
Sunstrike is saying they will list your mods as "unsupported" if you go through with this "DRM-like code". Can I ask what support/compatibility there is between your mods and TCon?
I assume by "unsupported" he meant "crash game if detected", like it does for GT.
Rollback Post to RevisionRollBack
I am the developer of many mods, most famously RotaryCraft and ChromatiCraft.
Feel free to support me and my mods via PayPal or Patreon
I am pretty sure he means that if one of Reikas mods is detected then they will not accept any crash reports as they do with Gregtech, Even if the crash is a known TiC bug, as they consider it an "unsupported environment", much like some authors will not deal with crash reports dealing with MCPC+.
Now, I happen to have both GT and TCon installed on my private modpack, and I do not get a crash.
Not be rude, but you did not answer my question of what support/compatibility there is between your two mods. Though, by your lack of answer, I take that to mean "none"?
The Meaning of Life, the Universe, and Everything.
Location:
Cakeville
Join Date:
10/22/2012
Posts:
430
Member Details
Sorry for going really off topic here. I've been reading some more comments about Tinkers Construct and those guys really need to give it a break.
Sure, GregTech modifies a ton of recipes in vanilla Minecraft and a bunch of mods. The changes in the mods you can disable. If you don't like the changes in vanilla Minecraft, then don't install the mod. Every mod you install changed things in vanilla Minecraft, that's the essence of mods. You can not however, with any serious argument, blame GregTech for doing anything wrong since you can undo all of the changes it makes in other mods. They are completely voluntary.
Tinkers Construct on the other hand introduced an infinite resource exploit which is a really bad thing for any mod to do. They took metal blocks, from GregTech, and gave the player the ability to break those blocks in more then 9 ingots. There was no way to disable this exploit. GregTech then posted a warning telling players Tinkers Construct introduced this exploit. Still people blame GregTech for wanting to change the way Tinkers Construct handled the blocks from GregTech. Which is completely insane. Tinkers Construct broke the game, plain and simple. They did this by changing the behavior of another mod... which is what people are accusing GregTech of mainly. The difference is GregTech doesn't create exploits, it makes things harder and you can disable the changes if you so choose.
Later Tinkers Construct added code that unregistered GregTech's ore dictionary handler. Effectively this broke GregTech and can't be seen as anything else but a direct attack on GregTech. It wasn't a bug. Their "piece of mind" feature's sole purpose was to break GregTech. After this was discovered they quickly removed this code from their mod. However their attitude towards other mods hasn't changed. Their current "warning" towards Reika's mods is proof of this.
Whatever mDiyo and the other people working on Tinkers Construct may say, they are the bad guys for doing such things. And them accusing other mod(authors) of doing things that are wrong is just hilariously ironic.
Rollback Post to RevisionRollBack
HappyDiggers is a small Minecraft community with several different servers: Adventure, Arena PvE, Feed The Beast, Skyblock, Small World, Towny, Prison, Vanilla and Snapshot.
OK, that means something else is editing my recipes, presumably deliberately to break them. Please list all mods and versions you have, and post a copy of your loading log (set to maximal logging).
The Meaning of Life, the Universe, and Everything.
Location:
Cakeville
Join Date:
10/22/2012
Posts:
430
Member Details
@ChrisGryph
The file is called: ForgeModLoader-client-0.log and it's located in the Minecraft directory.
Open it with notepad and copy/paste the contents to a site like http://paste2.org
Then after you click the submit button it will forward you to the result.
Next copy/paste the URL from your browser into a forum post and people can see the contents of your log.
HappyDiggers is a small Minecraft community with several different servers: Adventure, Arena PvE, Feed The Beast, Skyblock, Small World, Towny, Prison, Vanilla and Snapshot.
The file is called: ForgeModLoader-client-0.log and it's located in the Minecraft directory.
Open it with notepad and copy/paste the contents to a site like http://paste2.org
Then after you click the submit button it will forward you to the result.
Next copy/paste the URL from your browser into a forum post and people can see the contents of your log.
Now, I happen to have both GT and TCon installed on my private modpack, and I do not get a crash.
Not be rude, but you did not answer my question of what support/compatibility there is between your two mods. Though, by your lack of answer, I take that to mean "none"?
I have the following:
Ore handling for extractor
Tool handling to allow his picks to harvest my machines
On the talk of reactorcraft, any plans for gas cooling.
High-Temperature Gas Reactors? Not really.
EDIT:
I talked with a couple mod authors:
The fire crafting glitch is apparently an ID conflict. If the recipe system cannot find an item, it loads fire.
My guess is some other mod is overwriting one of my items. Check your configs. In the meantime, I will write an overwrite tracker to disallow this, as there is no reason for any mod to overwrite my items.
I'll point out that TiC never crashed GregTech. Look up the history GregTech put a measure in to stop TiC messing with a crafting recipe (ironic, right?) which caused a crash.
Edit: Hmm, this seems to be null and void now, anyway, since Reika PR'd to remove the warning.
They later retracted this comment and removed the breaking "piece of mind" feature from Tinkers Construct because a lot of people were unhappy with the way the Tinkers Construct devs were acting.
And now they are doing it to Reika. If they disagree with how Reika does things, that's perfectly fine. If they don't want their mod to be used along with any of Reika's mods, that's fine also and easily done by refusing to load the game if they detect Reika's mods. But the attacks and accusations they make really need to stop. They're not helping anyone by giving out a "warning" about a feature that may or may not be implemented.
We're on a forum right now. This is a place where opinions meet and people discuss their points of view. If people can't talk about these kinds of things but feel the need to attack each other, then something is very wrong.
HappyDiggers is a small Minecraft community with several different servers: Adventure, Arena PvE, Feed The Beast, Skyblock, Small World, Towny, Prison, Vanilla and Snapshot.
..a link to a nonexisting thread? This'd deserve a doge-meme right here. ;P
I"m not sure what this is referring to, but if it's about the message in the log, then it seems you're looking at it from a really weird angle. The log actually helps people that have crash problems (it tells them that mod X and Y is incompatible). And anybody who doesn't will never read the log anyway. Crashing the game on purpose should never be a solution. A preferred solution would be a more general one, some kind of compatibily list in forge or so maybe.
Whoops, links fixed.
The last incident between Tinkers Construct and GregTech was about GregTech making suggestions to mod authors about following Forge's guidelines about ore dictionary names.
The result was Tinkers Construct attacking GregTech with their "piece of mind" code. They apparently take the log files and messages printed in them seriously. So I don't think it's strange to look at their warning and be worried about what they're going to do next.
If you read after that, there is some constructive discussion between Greg and mDiyo where they "solve" the issue (solve as in "they won't touch each other").
Also, here we don't have to blame mDiyo but that other coder. I hope the issue is solved soon. The worst that could happen is TiC not accepting bugs while RC is installed. Not a big deal anyway.
And no, the only one that designed crashing code was Greg. TiC devs never released an official version with crashing code, they just detect a list of incompatible mods.
I know they solved the issue. That's what I've said before. They removed the "piece of mind" code and retracted that statement. The problem is with their apparent hostile attitude towards other mods and mod authors.
Them not giving support when GregTech and Reika's mods are installed would actually be a big deal if you ask me. A lot of mod packs have those mods, they don't exist in empty space but interact with each other.
Also with excluding mods like this: which one will be next? How about NEI, or Buildcraft? It's completely ridiculous to flat out ignore people just because they use a mod you don't like which may not even be causing any problems at all.
HappyDiggers is a small Minecraft community with several different servers: Adventure, Arena PvE, Feed The Beast, Skyblock, Small World, Towny, Prison, Vanilla and Snapshot.
Everything I read about the tokamak and about superconductive magnets suggested stable magnetic fields and currents, also because a sudden spike in current would heat the superconductor and put it back into its resistive state.
However, scratch the Van de Graaf idea. An homopolar generator is far more effective and in line with rotarycraft. It requires a static magnet, but those can be naturally found or induced (rotarycraft already has a machine to magnetize things ).
A homopolar generator is a conductive disk perpendicular to a static magnetic field, and two electrical contacts, one on the middle part and one on the edge of the disk. The formula for the potential difference is: v = Bwr^2 where B is the magnetic field strength, w is the angular speed and r is the radius.
Now, for the good news: an homopolar generator is EXACTLY the kind of generator we want for both electrolysis and the superconductive magnets!! It generates a very low potential difference but huge currents! (up to 2 MA) Wooh!
Well, I am implementing a Van De Graff into RotaryCraft anyways (think IC2 tesla coil), but is this homopolar generator not just another way of "adding electricity"?
Not as hard to find as you could think. It's extracted along with natural gasses and petroleum deep underground, and there are various methods of cooling it, even simple ones like a Joule-Thompson refrigerator, based on a piston and some valves.
However, coding it in game may be another thing.
That means I would have to add more worldgen for it, something I do not want to do.
Well, I started with a chekerboard pattern, but that was quite ineffective too.
I was basing this design on a real life BWR, with the water used to produce steam external to the core, with heat cumulating to the side and transmitting to all the water around the core (Now that I think about it, it would be quite impossible to code, silly me XD). I'll change my reactor design and see if it works. Anyway I had another weird issue with steam: it looks like if you make it go directly on the turbine center it'll make the turbine disappear
And that meltdown was caused by me on purpose, trying to see what was the largest aumout of cores I could use before triggering a meltdown
The ideal design is to use a sort of gridlike arrangement of fuel rods with boilers making contact with several fuel rods.
However, could I suggest you to also make steam boilers explode during meltdown? In a real reactor hydrogen accumulates on top of the steam chamber, along with very high pressure steam if there is excessive heat, and explodes causing heavy damage to everything (The roof of Reactor 4 in Cernobyl was launched several meters high during the meltdown)
That hydrogen explosion is actually already implemented; it is why the blocks fly like sand.
Following your suggestions I'm now using a reactor with 38 steam boilers, all in contact with one or more fuel cores filled with uranium. However, still not going past the 16,896 kW. Seriously, it looks capped at that number! If you or someone else could give me a working reactor design I could test it.
This is very strange, considering I usually have trouble making a reactor produce less than a megawatt.
I was thinking more along the lines of magnox/agr, I see your point though, no real need for them.
Also as for your issue with sodium, why not molten lead.
Because the real reactors use sodium. Lead nuclei are too big, and would absorb a good portion of the neutrons that otherwise would convert U238 to Pu239.
Rollback Post to RevisionRollBack
I am the developer of many mods, most famously RotaryCraft and ChromatiCraft.
Feel free to support me and my mods via PayPal or Patreon
@ChrisGryph The file is called: ForgeModLoader-client-0.log and it's located in the Minecraft directory. Open it with notepad and copy/paste the contents to a site like http://paste2.org Then after you click the submit button it will forward you to the result. Next copy/paste the URL from your browser into a forum post and people can see the contents of your log.
OK, that means something else is editing my recipes, presumably deliberately to break them. Please list all mods and versions you have, and post a copy of your loading log (set to maximal logging).
Time: 11/22/13 10:29 PM
Description: Initializing game
java.lang.NoClassDefFoundError: net/minecraftforge/event/entity/living/LivingSpawnEvent$AllowDespawn
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Unknown Source)
at java.lang.Class.getDeclaredMethods(Unknown Source)
at cpw.mods.fml.common.FMLModContainer.gatherAnnotations(FMLModContainer.java:324)
at cpw.mods.fml.common.FMLModContainer.constructMod(FMLModContainer.java:512)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.common.eventbus.EventHandler.handleEvent(EventHandler.java:74)
at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:45)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:313)
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:296)
at com.google.common.eventbus.EventBus.post(EventBus.java:267)
at cpw.mods.fml.common.LoadController.sendEventToModContainer(LoadController.java:194)
at cpw.mods.fml.common.LoadController.propogateStateMessage(LoadController.java:174)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.common.eventbus.EventHandler.handleEvent(EventHandler.java:74)
at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:45)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:313)
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:296)
at com.google.common.eventbus.EventBus.post(EventBus.java:267)
at cpw.mods.fml.common.LoadController.distributeStateMessage(LoadController.java:105)
at cpw.mods.fml.common.Loader.loadMods(Loader.java:510)
at cpw.mods.fml.client.FMLClientHandler.beginMinecraftLoading(FMLClientHandler.java:181)
at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:470)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:796)
at net.minecraft.client.main.Main.main(SourceFile:101)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:57)
at net.minecraft.launchwrapper.Launch.main(Launch.java:18)
Caused by: java.lang.ClassNotFoundException: net.minecraftforge.event.entity.living.LivingSpawnEvent$AllowDespawn
at net.minecraft.launchwrapper.LaunchClassLoader.findClass(LaunchClassLoader.java:179)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
... 37 more
Caused by: java.lang.NullPointerException
at net.minecraft.launchwrapper.LaunchClassLoader.findClass(LaunchClassLoader.java:171)
... 39 more
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Stacktrace:
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Unknown Source)
at java.lang.Class.getDeclaredMethods(Unknown Source)
at cpw.mods.fml.common.FMLModContainer.gatherAnnotations(FMLModContainer.java:324)
at cpw.mods.fml.common.FMLModContainer.constructMod(FMLModContainer.java:512)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.common.eventbus.EventHandler.handleEvent(EventHandler.java:74)
at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:45)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:313)
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:296)
at com.google.common.eventbus.EventBus.post(EventBus.java:267)
at cpw.mods.fml.common.LoadController.sendEventToModContainer(LoadController.java:194)
at cpw.mods.fml.common.LoadController.propogateStateMessage(LoadController.java:174)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.common.eventbus.EventHandler.handleEvent(EventHandler.java:74)
at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:45)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:313)
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:296)
at com.google.common.eventbus.EventBus.post(EventBus.java:267)
at cpw.mods.fml.common.LoadController.distributeStateMessage(LoadController.java:105)
at cpw.mods.fml.common.Loader.loadMods(Loader.java:510)
at cpw.mods.fml.client.FMLClientHandler.beginMinecraftLoading(FMLClientHandler.java:181)
at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:470)
-- Initialization --
Details:
Stacktrace:
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:796)
at net.minecraft.client.main.Main.main(SourceFile:101)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:57)
at net.minecraft.launchwrapper.Launch.main(Launch.java:18)
-- System Details --
Details:
Minecraft Version: 1.6.2
Operating System: Windows 7 (amd64) version 6.1
Java Version: 1.7.0_13, Oracle Corporation
Java VM Version: Java HotSpot™ 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 219076056 bytes (208 MB) / 490602496 bytes (467 MB) up to 954466304 bytes (910 MB)
JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx1G
AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
Suspicious classes: FML and Forge are installed
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
FML: MCP v8.04 FML v6.2.55.842 Minecraft Forge 9.10.0.842 13 mods loaded, 13 mods active
mcp{8.04} [Minecraft Coder Pack] (minecraft.jar) Unloaded->Constructed
FML{6.2.55.842} [Forge Mod Loader] (coremods) Unloaded->Constructed
Forge{9.10.0.842} [Minecraft Forge] (coremods) Unloaded->Constructed
mod_bspkrsCore{v3.03(1.6.2)} [bspkrsCore] ([1.6.2]bspkrsCorev3.03.zip) Unloaded->Constructed
TreeCapitator{Forge 1.6.2.r04} [Treecapitator] ([1.6.2]TreeCapitator.Forge.1.6.2.r04.Universal.jar) Unloaded->Constructed
craftguide{1.5.2} [CraftGuide] (CraftGuide-1.6.7.4.zip) Unloaded->Constructed
LomLib{1.0.6} [LomLib] (LomLib-universal-1.0.6.jar) Unloaded->Constructed
diving{2.0.0} [Diving Gear] (DivingGear2PreRelease.jar) Unloaded->Constructed
DragonAPI{release} [DragonAPI] (DragonAPI v6 1.6.zip) Unloaded->Constructed
excessivefoods{1.6.2} [ExcessiveFoods] (ExcessiveFood V3.zip) Unloaded->Constructed
wuppy29_harderpeaceful{1.6.0} [Harder Peaceful] (Harder Peaceful 1.6.0.zip) Unloaded->Constructed
MinersDeluxe{2.2.2} [MinersDeluxe] (MinersDeluxe-v2.2.2.zip) Unloaded->Constructed
SpiderPet{beta} [Spider Pet] (SpiderPet v6 1.6.zip) Unloaded
Launched Version: 1.6.2-Forge9.10.0.842
LWJGL: 2.9.0
OpenGL: ATI Radeon HD 4250 GL version 3.2.9606 Compatibility Profile Context, ATI Technologies Inc.
Is Modded: Definitely; Client brand changed to 'fml,forge'
Type: Client (map_client.txt)
Resource Pack: Default
Current Language: English (US)
Profiler Position: N/A (disabled)
Vec3 Pool Size: ~~ERROR~~ NullPointerException: null
That hydrogen explosion is actually already implemented; it is why the blocks fly like sand.
If I may opine. I would say that for realism's sake not all meltdowns should actually cause an hydrogen explosion. Thee Mile Island is an example of a reactor design which was resistant to the hydrogen explosion because it was made as an PWR (Pressurized Water Reactor) which is, by definition, an NTC (Negative Temperature Coefficient) reactor.
As you probably already know (so I am stating this for those that don't), for fissil fuel to react the neutrons must be slow moving. In a PWR, the coolant (water) is also used as the moderator (slows fast moving neutrons down) so that more fissils may take place. However, as the temperature of the coolant increases pockets of steam are created, thus preventing the moderation of more and more neutrons, causing the reactions to lesson as temp increases. This is why reactor 2 on Three Mile Island only partly melted down even though it pretty much ran dry. The inside of the reactor is a ruined mess, but there was never any danger of hydrogen explosions.
On the other hand, Chernobyl was an RBMK (Reaktor Bolshoy Moshchnosti Kanalniy), or "High Power Channel-type Reactor" in English. These use water for cooling, and graphite as a moderator. This design is known as a PTC (Positive Thermal Coefficient) reactor, and as the name implies it increases its reactions as the temperature rises. Because the water was counted on for the cooling, and graphite to moderate the neutrons, reactions not only continue as the water begins to vaporize, but continue to increase. With Chernobyl, this continued until the reactor was hot enough to crack water (separate the hydrogen from the oxygen. I would say the rest is history, but what happened after (Biorobots) was an atrocity in its own right.
See 55 minutes into this documentary if you want to learn more about biorobots. Also, the entire documentary is about the Chernobyl incident and might be of interest to those reading this thread anyways.
The issue I am getting at though, is not every reactor will have the ability to reach the temp to crack water and cause a hydrogen explosion. Well designed reactors will actually start to taper down as they get hotter, although they will also damage themselves and become useless structures when that happens.
I would quit wikipedia also. It is an unreliable source. I actually got my information from an NE class I took in college. Here is a better source for information on the TMI incident.
Quote from world-nuclear.org »
The Hydrogen Bubble
When the reactor's core was uncovered, on the morning of 28 March, a high-temperature chemical reaction between water and the zircaloy metal tubes holding the nuclear fuel pellets had created hydrogen gas. In the afternoon of 28 March, a sudden rise in reactor building pressure shown by the control room instruments indicated a hydrogen burn had occurred. Hydrogen gas also gathered at the top of the reactor vessel.
From 30 March through 1 April operators removed this hydrogen gas "bubble" by periodically opening the vent valve on the reactor cooling system pressuriser. For a time, regulatory (NRC) officials believed the hydrogen bubble could explode, though such an explosion was never possible since there was not enough oxygen in the system.
Now, the incident at Fukushima was a special case, as the explosions would not have occurred over the natural course of the disaster except for the damage caused from outside source. Now, using Fukushima to justify such an event in ReactorCraft would be applicable if Reika plans to implelent earthquakes and tsunamis as natural disasters. On the other hand, creeper damage, and griefing endermen might be cause for this to happen.
The point is that a BWR does not run the danger over the coarse of its natural cycle to overheat and detonate a hydrogen bubble. Fukushima had damage which allowed excess oxygen into the area around the hydrogen.
Edit: I should state an adequately designed BWR does not run said risk.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumOK, that means something else is editing my recipes, presumably deliberately to break them. Please list all mods and versions you have, and post a copy of your loading log (set to maximal logging).
Digital Reality Private Pack - 200+ Mods, Dedi Server
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI assume by "unsupported" he meant "crash game if detected", like it does for GT.
Digital Reality Private Pack - 200+ Mods, Dedi Server
delete privat modpack
Sure, GregTech modifies a ton of recipes in vanilla Minecraft and a bunch of mods. The changes in the mods you can disable. If you don't like the changes in vanilla Minecraft, then don't install the mod. Every mod you install changed things in vanilla Minecraft, that's the essence of mods. You can not however, with any serious argument, blame GregTech for doing anything wrong since you can undo all of the changes it makes in other mods. They are completely voluntary.
Tinkers Construct on the other hand introduced an infinite resource exploit which is a really bad thing for any mod to do. They took metal blocks, from GregTech, and gave the player the ability to break those blocks in more then 9 ingots. There was no way to disable this exploit. GregTech then posted a warning telling players Tinkers Construct introduced this exploit. Still people blame GregTech for wanting to change the way Tinkers Construct handled the blocks from GregTech. Which is completely insane. Tinkers Construct broke the game, plain and simple. They did this by changing the behavior of another mod... which is what people are accusing GregTech of mainly. The difference is GregTech doesn't create exploits, it makes things harder and you can disable the changes if you so choose.
Later Tinkers Construct added code that unregistered GregTech's ore dictionary handler. Effectively this broke GregTech and can't be seen as anything else but a direct attack on GregTech. It wasn't a bug. Their "piece of mind" feature's sole purpose was to break GregTech. After this was discovered they quickly removed this code from their mod. However their attitude towards other mods hasn't changed. Their current "warning" towards Reika's mods is proof of this.
Whatever mDiyo and the other people working on Tinkers Construct may say, they are the bad guys for doing such things. And them accusing other mod(authors) of doing things that are wrong is just hilariously ironic.
HappyDiggers is a small Minecraft community with several different servers: Adventure, Arena PvE, Feed The Beast, Skyblock, Small World, Towny, Prison, Vanilla and Snapshot.
Uhh... okay, how do I get my loading log? >.>
The file is called: ForgeModLoader-client-0.log and it's located in the Minecraft directory.
Open it with notepad and copy/paste the contents to a site like http://paste2.org
Then after you click the submit button it will forward you to the result.
Next copy/paste the URL from your browser into a forum post and people can see the contents of your log.
HappyDiggers is a small Minecraft community with several different servers: Adventure, Arena PvE, Feed The Beast, Skyblock, Small World, Towny, Prison, Vanilla and Snapshot.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI have the following:
High-Temperature Gas Reactors? Not really.
EDIT:
I talked with a couple mod authors:
The fire crafting glitch is apparently an ID conflict. If the recipe system cannot find an item, it loads fire.
My guess is some other mod is overwriting one of my items. Check your configs. In the meantime, I will write an overwrite tracker to disallow this, as there is no reason for any mod to overwrite my items.
Perhaps you should look up the history yourself because I think you are very wrong. Here's Greg's explanation of what happened last time Tinkers Construct attacked GregTech: http://forum.industrial-craft.net/index.php?page=Thread&threadID=9955
Also this was their reaction to people complaining about Tinkers Construct purposefully breaking GregTech.
source
They later retracted this comment and removed the breaking "piece of mind" feature from Tinkers Construct because a lot of people were unhappy with the way the Tinkers Construct devs were acting.
And now they are doing it to Reika. If they disagree with how Reika does things, that's perfectly fine. If they don't want their mod to be used along with any of Reika's mods, that's fine also and easily done by refusing to load the game if they detect Reika's mods. But the attacks and accusations they make really need to stop. They're not helping anyone by giving out a "warning" about a feature that may or may not be implemented.
We're on a forum right now. This is a place where opinions meet and people discuss their points of view. If people can't talk about these kinds of things but feel the need to attack each other, then something is very wrong.
HappyDiggers is a small Minecraft community with several different servers: Adventure, Arena PvE, Feed The Beast, Skyblock, Small World, Towny, Prison, Vanilla and Snapshot.
Whoops, links fixed.
The last incident between Tinkers Construct and GregTech was about GregTech making suggestions to mod authors about following Forge's guidelines about ore dictionary names.
The result was Tinkers Construct attacking GregTech with their "piece of mind" code. They apparently take the log files and messages printed in them seriously. So I don't think it's strange to look at their warning and be worried about what they're going to do next.
I know they solved the issue. That's what I've said before. They removed the "piece of mind" code and retracted that statement. The problem is with their apparent hostile attitude towards other mods and mod authors.
Them not giving support when GregTech and Reika's mods are installed would actually be a big deal if you ask me. A lot of mod packs have those mods, they don't exist in empty space but interact with each other.
Also with excluding mods like this: which one will be next? How about NEI, or Buildcraft? It's completely ridiculous to flat out ignore people just because they use a mod you don't like which may not even be causing any problems at all.
HappyDiggers is a small Minecraft community with several different servers: Adventure, Arena PvE, Feed The Beast, Skyblock, Small World, Towny, Prison, Vanilla and Snapshot.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumWell, I am implementing a Van De Graff into RotaryCraft anyways (think IC2 tesla coil), but is this homopolar generator not just another way of "adding electricity"?
That means I would have to add more worldgen for it, something I do not want to do.
The ideal design is to use a sort of gridlike arrangement of fuel rods with boilers making contact with several fuel rods.
That hydrogen explosion is actually already implemented; it is why the blocks fly like sand.
This is very strange, considering I usually have trouble making a reactor produce less than a megawatt.
Because the real reactors use sodium. Lead nuclei are too big, and would absorb a good portion of the neutrons that otherwise would convert U238 to Pu239.
http://paste2.org/xYPExOwe
Mods are as follows:
Optifine_1.6.4_HD_C6
Minecraft Coder Pack 8.09
Forge Mod Loader 6.4.38.942
Minecraft Forge 9.11.1.942
Chemcraft Core 1.5.8
CodeChicken Core 0.9.0.6
Not Enough Items 1.6.1.5
Chicken Shed 1.1.2
bspkrsCore v5.0
CrystalWing 1.6.4.r04
Treecapitator 1.6.4.r06
Backpack 1.18.17
The Barrels Mod 3.2
BiblioCraft 1.4.1
BuildCraft 4.1.0
Colourful Portals Mod 1.2.2
Immibis Core 57.0.0
Dimensional Anchors 57.0.0
DragonAPI v6
Equivalent Exchange 3 pre2-19
Enchanting Plus 1.16.5
Ender Forest v6
LomLib 1.0.6
Equivalency 1.5.4
Exp Chest v3.1.40.--
GeoStrata v6
Gravestone 1.6.2 v5.2
iChunUtil 2.3.0
Iron Chest 5.3.14 build 512
Liquid Fuels 2.2.0
NEI Addons 1.9.0.r40
NEI Plugins 1.1.0.1
Peacefulpack 1.1.6.1
ReactorCraft v6
RotaryCraft v6
Spider Pet v6
Teleport Pipes 1.0.0
Thaumcraft 4.0.4c
Torched 2.0.0
Useful TNT v6
Balkon's WeaponMod 1.13.6
Xplosion Core 1.0.0.0
Zan's Minimap 1.0
Chemcraft Network 1.0.2
That's everything that shows up in my mod list in the game menu.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumNo obvious offenders in the mod list, and the logs contain nothing.
It may be an ID conflict as others have suggested. Try the new version when it comes out and let's see.
Time: 11/22/13 10:29 PM
Description: Initializing game
java.lang.NoClassDefFoundError: net/minecraftforge/event/entity/living/LivingSpawnEvent$AllowDespawn
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Unknown Source)
at java.lang.Class.getDeclaredMethods(Unknown Source)
at cpw.mods.fml.common.FMLModContainer.gatherAnnotations(FMLModContainer.java:324)
at cpw.mods.fml.common.FMLModContainer.constructMod(FMLModContainer.java:512)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.common.eventbus.EventHandler.handleEvent(EventHandler.java:74)
at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:45)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:313)
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:296)
at com.google.common.eventbus.EventBus.post(EventBus.java:267)
at cpw.mods.fml.common.LoadController.sendEventToModContainer(LoadController.java:194)
at cpw.mods.fml.common.LoadController.propogateStateMessage(LoadController.java:174)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.common.eventbus.EventHandler.handleEvent(EventHandler.java:74)
at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:45)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:313)
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:296)
at com.google.common.eventbus.EventBus.post(EventBus.java:267)
at cpw.mods.fml.common.LoadController.distributeStateMessage(LoadController.java:105)
at cpw.mods.fml.common.Loader.loadMods(Loader.java:510)
at cpw.mods.fml.client.FMLClientHandler.beginMinecraftLoading(FMLClientHandler.java:181)
at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:470)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:796)
at net.minecraft.client.main.Main.main(SourceFile:101)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:57)
at net.minecraft.launchwrapper.Launch.main(Launch.java:18)
Caused by: java.lang.ClassNotFoundException: net.minecraftforge.event.entity.living.LivingSpawnEvent$AllowDespawn
at net.minecraft.launchwrapper.LaunchClassLoader.findClass(LaunchClassLoader.java:179)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
... 37 more
Caused by: java.lang.NullPointerException
at net.minecraft.launchwrapper.LaunchClassLoader.findClass(LaunchClassLoader.java:171)
... 39 more
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Stacktrace:
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Unknown Source)
at java.lang.Class.getDeclaredMethods(Unknown Source)
at cpw.mods.fml.common.FMLModContainer.gatherAnnotations(FMLModContainer.java:324)
at cpw.mods.fml.common.FMLModContainer.constructMod(FMLModContainer.java:512)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.common.eventbus.EventHandler.handleEvent(EventHandler.java:74)
at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:45)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:313)
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:296)
at com.google.common.eventbus.EventBus.post(EventBus.java:267)
at cpw.mods.fml.common.LoadController.sendEventToModContainer(LoadController.java:194)
at cpw.mods.fml.common.LoadController.propogateStateMessage(LoadController.java:174)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.google.common.eventbus.EventHandler.handleEvent(EventHandler.java:74)
at com.google.common.eventbus.SynchronizedEventHandler.handleEvent(SynchronizedEventHandler.java:45)
at com.google.common.eventbus.EventBus.dispatch(EventBus.java:313)
at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:296)
at com.google.common.eventbus.EventBus.post(EventBus.java:267)
at cpw.mods.fml.common.LoadController.distributeStateMessage(LoadController.java:105)
at cpw.mods.fml.common.Loader.loadMods(Loader.java:510)
at cpw.mods.fml.client.FMLClientHandler.beginMinecraftLoading(FMLClientHandler.java:181)
at net.minecraft.client.Minecraft.func_71384_a(Minecraft.java:470)
-- Initialization --
Details:
Stacktrace:
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:796)
at net.minecraft.client.main.Main.main(SourceFile:101)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:57)
at net.minecraft.launchwrapper.Launch.main(Launch.java:18)
-- System Details --
Details:
Minecraft Version: 1.6.2
Operating System: Windows 7 (amd64) version 6.1
Java Version: 1.7.0_13, Oracle Corporation
Java VM Version: Java HotSpot™ 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 219076056 bytes (208 MB) / 490602496 bytes (467 MB) up to 954466304 bytes (910 MB)
JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx1G
AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
Suspicious classes: FML and Forge are installed
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
FML: MCP v8.04 FML v6.2.55.842 Minecraft Forge 9.10.0.842 13 mods loaded, 13 mods active
mcp{8.04} [Minecraft Coder Pack] (minecraft.jar) Unloaded->Constructed
FML{6.2.55.842} [Forge Mod Loader] (coremods) Unloaded->Constructed
Forge{9.10.0.842} [Minecraft Forge] (coremods) Unloaded->Constructed
mod_bspkrsCore{v3.03(1.6.2)} [bspkrsCore] ([1.6.2]bspkrsCorev3.03.zip) Unloaded->Constructed
TreeCapitator{Forge 1.6.2.r04} [Treecapitator] ([1.6.2]TreeCapitator.Forge.1.6.2.r04.Universal.jar) Unloaded->Constructed
craftguide{1.5.2} [CraftGuide] (CraftGuide-1.6.7.4.zip) Unloaded->Constructed
LomLib{1.0.6} [LomLib] (LomLib-universal-1.0.6.jar) Unloaded->Constructed
diving{2.0.0} [Diving Gear] (DivingGear2PreRelease.jar) Unloaded->Constructed
DragonAPI{release} [DragonAPI] (DragonAPI v6 1.6.zip) Unloaded->Constructed
excessivefoods{1.6.2} [ExcessiveFoods] (ExcessiveFood V3.zip) Unloaded->Constructed
wuppy29_harderpeaceful{1.6.0} [Harder Peaceful] (Harder Peaceful 1.6.0.zip) Unloaded->Constructed
MinersDeluxe{2.2.2} [MinersDeluxe] (MinersDeluxe-v2.2.2.zip) Unloaded->Constructed
SpiderPet{beta} [Spider Pet] (SpiderPet v6 1.6.zip) Unloaded
Launched Version: 1.6.2-Forge9.10.0.842
LWJGL: 2.9.0
OpenGL: ATI Radeon HD 4250 GL version 3.2.9606 Compatibility Profile Context, ATI Technologies Inc.
Is Modded: Definitely; Client brand changed to 'fml,forge'
Type: Client (map_client.txt)
Resource Pack: Default
Current Language: English (US)
Profiler Position: N/A (disabled)
Vec3 Pool Size: ~~ERROR~~ NullPointerException: null
-
View User Profile
-
View Posts
-
Send Message
Curse Premium1. Use spoilers or pastebin.
2. Your Forge is out of date.
If I may opine. I would say that for realism's sake not all meltdowns should actually cause an hydrogen explosion. Thee Mile Island is an example of a reactor design which was resistant to the hydrogen explosion because it was made as an PWR (Pressurized Water Reactor) which is, by definition, an NTC (Negative Temperature Coefficient) reactor.
As you probably already know (so I am stating this for those that don't), for fissil fuel to react the neutrons must be slow moving. In a PWR, the coolant (water) is also used as the moderator (slows fast moving neutrons down) so that more fissils may take place. However, as the temperature of the coolant increases pockets of steam are created, thus preventing the moderation of more and more neutrons, causing the reactions to lesson as temp increases. This is why reactor 2 on Three Mile Island only partly melted down even though it pretty much ran dry. The inside of the reactor is a ruined mess, but there was never any danger of hydrogen explosions.
On the other hand, Chernobyl was an RBMK (Reaktor Bolshoy Moshchnosti Kanalniy), or "High Power Channel-type Reactor" in English. These use water for cooling, and graphite as a moderator. This design is known as a PTC (Positive Thermal Coefficient) reactor, and as the name implies it increases its reactions as the temperature rises. Because the water was counted on for the cooling, and graphite to moderate the neutrons, reactions not only continue as the water begins to vaporize, but continue to increase. With Chernobyl, this continued until the reactor was hot enough to crack water (separate the hydrogen from the oxygen. I would say the rest is history, but what happened after (Biorobots) was an atrocity in its own right.
See 55 minutes into this documentary if you want to learn more about biorobots. Also, the entire documentary is about the Chernobyl incident and might be of interest to those reading this thread anyways.
The issue I am getting at though, is not every reactor will have the ability to reach the temp to crack water and cause a hydrogen explosion. Well designed reactors will actually start to taper down as they get hotter, although they will also damage themselves and become useless structures when that happens.
I would quit wikipedia also. It is an unreliable source. I actually got my information from an NE class I took in college. Here is a better source for information on the TMI incident.
Source: http://www.world-nuc...sland-accident/
Now, the incident at Fukushima was a special case, as the explosions would not have occurred over the natural course of the disaster except for the damage caused from outside source. Now, using Fukushima to justify such an event in ReactorCraft would be applicable if Reika plans to implelent earthquakes and tsunamis as natural disasters. On the other hand, creeper damage, and griefing endermen might be cause for this to happen.
The point is that a BWR does not run the danger over the coarse of its natural cycle to overheat and detonate a hydrogen bubble. Fukushima had damage which allowed excess oxygen into the area around the hydrogen.
Edit: I should state an adequately designed BWR does not run said risk.