-
Notifications
You must be signed in to change notification settings - Fork 433
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
Ability for Robots to turn on PC´s #1505
Comments
You could always use wake on redstone or network message via a wireless network card |
Could you explain this to me? |
I want this to work with a brand new PC(neither OS nor anything) |
i just checked some code ( component/NetworkCard.scala ) |
Ports are closed when the device is off, anyway. But you don't need an open port when doing the wake bit. Not sure how to do what you're doing with it offhand, it's late and I've been awake entirely way too long. |
No, you should be able to turn a robot on with another robot. I was able to On Tue, 27 Oct 2015 4:37 pm Kodos Macarthur notifications@github.com
|
I.e. using the use command. When I did it was before the scrench however, On Tue, 27 Oct 2015 4:42 pm Sandra Nicole gjgfujb@gmail.com wrote:
|
@MyNameIsKodos Could you please tell me what has to be done in order to "wake-on-message" a computer in detail, so that i can figure out wether or not a robot could do it? @gjgfuj "empty-handed" robot.use() (normal and sneaky) does nothing to a PC, havent tested it on a robot jet. |
I GOT IT!! |
It is possible for a player to sneak-activate a PC with a Screwrench, which causes the PC to turn on.
But I haven´t been able to make a robot do it.
(i used: component.robot.use(sides.front,front,true) )
I believe this is the correct way, but maybe it takes a player to boot a computer.
If that is the case, than the robot could act as a proxy for the player who build it.
If a robot could boot a PC, it could become possible for a robot to replicate on its own.
-> robot can controle an assembler via self build PC...
The text was updated successfully, but these errors were encountered: