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

Energy Meter bug #508

Closed
yannic312 opened this issue Aug 19, 2016 · 4 comments
Closed

Energy Meter bug #508

yannic312 opened this issue Aug 19, 2016 · 4 comments
Assignees
Labels
Milestone

Comments

@yannic312
Copy link

I just discovered this bug while building my house: I have an Energy Meter, set it to "prepay mode", enter an energy value and let some power run through it. As long as I'm playing it works normally, but when I leave and re-enter the world and look at the Meter, it is set to "counter mode" again!

@AMIDIBOSS
Copy link
Contributor

This is a bug, and i needs to be fixed. It's very anoying,especially on a server. I try to sell power and make my players pay from energy i sell them. It seems I'll use counter mode anyway i prefer prepay. If u can tell me why u need this meter, i may tell you how to use it with counter mode/CPU/some other special devices if u wish

@yannic312
Copy link
Author

I need the prepay mode because I am making a world for a server where players must pay for electricity, and if they dont pay, their power should get cut off! There are already like 10 meters and it's really annoying to reset them each time the world gets reloaded... It would be really useful if you could tell me how to use it with counter mode :)

@bookerthegeek
Copy link

You can set up a counter circuit that turns on when a specific number of pulses have passed. Then have a switch turn off the power to the counter.

cm0x4D pushed a commit that referenced this issue Aug 22, 2016
@cm0x4D cm0x4D added the bug label Aug 22, 2016
@cm0x4D cm0x4D added this to the 1.12.0 milestone Aug 22, 2016
@cm0x4D cm0x4D self-assigned this Aug 22, 2016
@cm0x4D
Copy link
Member

cm0x4D commented Aug 22, 2016

Issue is fixed in branch develop and will be part of the 1.12.0 release.

@cm0x4D cm0x4D closed this as completed Aug 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants