-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Program just is not working. #35
Comments
What version of MC? |
1.7.10 We are using the FTB Infinity Evolved modpack if that helps |
Follow the tutorial https://github.com/acidjazz/drmon#tutorial |
I have, I’ve disassembled and rebuilt the whole setup 15 different times on the server. I’ve built 3 following the tutorial in single player creative and those 3 work fine but the one on the server does not work at all. |
Tomorrow when I am at my computer I will upload screenshots of what’s going on. |
@LegitMyth i wonder if since creative it works so well that maybe some server settings are conflicting timing? what about single player in non-creative mode? |
Also, I noticed how the Output fluxgate also shoots to 900,000 rf/t setting, when in the code, the input fluxgate is the only thing that is supposed to do that. |
https://github.com/acidjazz/drmon/blob/master/drmon.lua#L259..L261 Working as intended. |
Okay, that tells the input fluxgate to put 900,000 rf/t into the reactor core through the energy injector. Atleast that is what it looks like. So why does the output gate, on the side of the computer also shoot to 900,000 rf/t. It doesn’t do that in single player. Yet on the server it does. |
I am playing on a server with some friends, it is just the four of us. I setup the reactor as usual and install everything and it just does not work. The Input and Output shoot up to 900,000 and the reactor does not charge. If we try to kick start it by forcing power in, the program lowers the output and we can't control the reactor. I test all this in creative and everything works just fine. Why is it doing this?
The text was updated successfully, but these errors were encountered: