But in so doing, she violated safety rules calling for a swift evacuation of all personnel in "criticality" events, because bodies - and even hands - can reflect and slow the neutrons emitted by plutonium, increasing the likelihood of a nuclear chain reaction. It's Physics 101 for nuclear scientists, but has sometimes been ignored at Los Alamos.Īs luck had it that August day, a supervisor returned from her lunch break, noticed the dangerous configuration, and ordered a technician to move the rods apart. So keeping bits of plutonium far apart is one of the bedrock rules that those working on the nuclear arsenal are supposed to follow to prevent workplace accidents. The resulting blue glow - known as Cherenkov radiation - has accidentally and abruptly flashed at least 60 times since the dawn of the nuclear age, signaling an instantaneous nuclear charge and causing a total of 21 agonizing deaths. When too much is put in one place, it becomes "critical" and begins to fission uncontrollably, spontaneously sparking a nuclear chain reaction, which releases energy and generates a deadly burst of radiation. But plutonium is the unstable, radioactive, man-made fuel of a nuclear explosion, and it isn't amenable to showboating. Why that flux gate simply stopped working, I still do not know to this day, but perhaps maybe it has to do something with the reactor exploding in the first place on server restart? Or maybe it stopped working after we turned the reactor off manually in server files?Īpologies for the wall of text - just trying to tell my side of the story to help you understand where the problem might lay, and to even fix a possible bug that might exist.Technicians at the government's Los Alamos National Laboratory settled on what seemed like a surefire way to win praise from their bosses in August 2011: In a hi-tech testing and manufacturing building pivotal to sustaining America's nuclear arsenal, they gathered eight rods painstakingly crafted out of plutonium, and positioned them side-by-side on a table to photograph how nice they looked.Īt many jobs, this would be innocent bragging. The reactor did not receive absolutely any kind of input power whatsoever, which caused it to drop from 50% to 0% shields and explode (even though the reactor managed to raise shields and warm up perfectly fine prior to starting it up).Īfter a ton of troubleshooting, it seems that the input flux gate has simply not worked - destroying it and replacing it with a new one with the same amount of RF/t fixed the issue. However, there was a hiccup that we encountered only one time after fiddling with server files to shut the reactor off manually - we mined the core out and replaced it with a new one, had the same exact setup and we turned the reactor on. That's how we've been doing it so far and that has worked. Though that kind of a shutdown system is not something we'd prefer, as we need to wait a good couple of minutes for the reactor to be stable enough with shield and low enough in temperature to shut it off without an issue. We've found a temporary solution, and that is to go in the server config files and manually turn off the reactor, then hop into the server - the reactor is then turned off and poses no threat. The reactor is chunk loaded using an IC2 Chunk Loader - unfortunately ATM 3 modpack doesn't leave us much of a choice, so we have to use that one, as we've got no alternatives. But for long-term, we would like to know if this issue happened before and if there is a fix for it. Right now we have to keep the server offline until we find a fix, and if the fix even includes just deleting the reactor from the world prior to starting the server, we will take that. Is there a way to fix this issue? We had a fully stable reactor that only explodes because of the server restarting, and our reactor is placed under our base for convenience sake, as we know how to properly manage the reactor, but wouldn't ever think that the reactor would explode due to a server restart. Upon starting the server, we are either greeted with the reactor status of "Explosion Imminent" on the reactor or just a big boom when we connect to the server. I have managed to kick it to 1,6M RF/t, fully stable (similar stats to the picture above) before the server had to be restarted. The above picture is the latest picture I have of our reactor being stable. ( If the above picture doesn't load, the link to it is here - ) The Draconic Reactor keeps exploding whenever the server restarts, even though it was perfectly stable prior to the server shutting down.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |