Skip to content
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

Stop overzealous controlRodAdjustAmount adjustment amount adjustment #56

Merged
merged 9 commits into from
Apr 8, 2015

Conversation

thetaphi
Copy link
Contributor

@thetaphi thetaphi commented Apr 7, 2015

The amount of the words "adjustment" and "amount" in the title needs to be adjusted.

Nevertheless, from the commit message:

It makes one reactor mess with the others. I guess it makes sense for
one reactor setups to carry over between cycles, but as soon as there's
more, you're in for surprises. More so since that variable is also used
for the manual adjustment amount.

Figured that out while I was testing the new UI handlers from thetaphi/minecraft_bigreactor_control@669e079

Instead of looking for activly cooled reactors, I simply took the list
size. Untested code, late night brainfart fix.

TODO: Same for turbines.
This reverts commit 9fe6ed98194212bcf8c34063586e1b8ef3ebf375.
Instead of looking for activly cooled reactors, I simply took the list
size. Untested code, late night brainfart fix.

TODO: Same for turbines.
This reverts commit 9fe6ed98194212bcf8c34063586e1b8ef3ebf375.
It makes one reactor mess with the others. I guess it makes sense for
one reactor setups to carry over between cycles, but as soon as there's
more, you're in for surprises. More so since that variable is also used
for the manual adjustment amount.
@mechaet
Copy link
Collaborator

mechaet commented Apr 7, 2015

Wait, what? The individual reactors are all supposed to be loading and saving their own variables from their own config files. Was there a regression in config file functionality somewhere??

Date: Mon, 6 Apr 2015 22:26:54 -0700
From: notifications@github.com
To: minecraft_bigreactor_control@noreply.github.com
Subject: [minecraft_bigreactor_control] Stop overzealous controlRodAdjustAmount adjustment amount adjustment (#56)

The amount of the words "adjustment" and "amount" in the title needs to be adjusted.

Nevertheless, from the commit message:

It makes one reactor mess with the others. I guess it makes sense for

one reactor setups to carry over between cycles, but as soon as there's

more, you're in for surprises. More so since that variable is also used

for the manual adjustment amount.

Figured that out while I was testing the new UI handlers from thetaphi/minecraft_bigreactor_control@669e079

You can view, comment on, or merge this pull request online at:
#56

Commit Summary

Count active reactors for steam capacity calculation
Revert "Count active reactors for steam capacity calculation"
add *.swp to .gitignore
Count active reactors for steam capacity calculation
Revert "Count active reactors for steam capacity calculation"
add *.swp to .gitignore
Merge branch 'master' of https://github.com/thetaphi/minecraft_bigreactor_control
Don't manipulate controlRodAdjustAmount

File Changes

M
.gitignore
(1)


M
lolmer_bigreactor_monitor_prog.lua
(10)

Patch Links:

https://github.com/sandalle/minecraft_bigreactor_control/pull/56.patch
https://github.com/sandalle/minecraft_bigreactor_control/pull/56.diff


Reply to this email directly or view it on GitHub.

@thetaphi
Copy link
Contributor Author

thetaphi commented Apr 7, 2015

AFAICT, that particular reactor setting slipped through the cracks from the start. I tried bisecting but couldn't find a good revision.

So from what you say, a better approach than always leaving the adjustment value at 1 would be to a) kill the global and b) put the setting in the config file for each reactor via _G?

Use the controlRodAdjustAmount value only as a default. Save it to the
_G reactor options under "controlRodAdjustAmount", and use that instead
for changing values.
@sandalle sandalle added the bug label Apr 8, 2015
@sandalle sandalle added this to the 0.3.17 milestone Apr 8, 2015
sandalle added a commit that referenced this pull request Apr 8, 2015
Stop overzealous controlRodAdjustAmount adjustment amount adjustment
@sandalle sandalle merged commit f2e707c into sandalle:master Apr 8, 2015
sandalle added a commit that referenced this pull request Apr 8, 2015
… amount adjustment Issue #56 thanks to @thetaphi (Nicolas Kratz).
@thetaphi thetaphi deleted the fix-overzealousRodAdjust branch April 10, 2015 09:56
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants