+- Goonstation Forums (https://forum.ss13.co)
+-- Forum: Discussion (https://forum.ss13.co/forumdisplay.php?fid=6)
+--- Forum: Bug Reports (https://forum.ss13.co/forumdisplay.php?fid=9)
+--- Thread: Major MechComp powernet networking component doesnt want to work right with the nuke (/showthread.php?tid=10978)
MechComp powernet networking component doesnt want to work right with the nuke - drWoof - 08-23-2018
See title.
I've honestly tried everything.
I connect with the MechNet (mechcomp powernetworking component as said when using term_ping) to the nuke (using term_connect) and ensure that I actually connected.
I send the correct packet (
Code:
address_1=02022e93; data=(command=settime&time=31); command=term_message; sender=02022958;I check the packet sniffer ( comes out as
Code:
address_1=02022e93; data=command=settime&time=31; command=term_message; sender=02022958;Code:
address_1=02022e93; data=command=settime&time=31; command=term_message; sender=0200e1a4;Same applies to trying to activate the nuke. The address_1 and sender are absolutely correct, I used a term_connect command with the same sender and address and it DID connect. I tried sending a packet like
Code:
address_1=02022e93&data=command=act&auth=%some master pass%&command=term_message&sender=02022958Code:
address_1=02022e93; data=command=act; auth=%maste pass%; command=term_message; sender=02022958RE: MechComp powernet networking component doesnt want to work right with the nuke - Mordent - 08-23-2018
Newlines and code tags are a thing, for the sake of the sanity of whatever coder looks at this would you mind editing to use them?
RE: MechComp powernet networking component doesnt want to work right with the nuke - Sov - 08-23-2018
The packet sent to arm a nuke from nukeman is
Command=act&auth=[heads pass]&session=[sessionid]
Where session ID is the time of day modulus 100 and then a number 0-9
You didn't include a session ID at all. No idea if it's actually needed though
RE: MechComp powernet networking component doesnt want to work right with the nuke - drWoof - 08-23-2018
Session ID isn't needed.
I *know* the packet is correct because I sent a packet from the terminal to the nuke and it ACTIVATED it or SET THE TIME. What you sent isn't the full packet, it's just the data part of it. When I do it from the MechNet component - it doesn't do anything. Sure, you can connect, but it WON'T set the time or activate the nuke.
RE: MechComp powernet networking component doesnt want to work right with the nuke - Wilbur Wright - 08-23-2018
It took me a looooong while to figure this out. But, it's totally possible to talk with the nuke using the powernet. It sure is a challenge!
This can all be explained with one word, Dwaine.
RE: MechComp powernet networking component doesnt want to work right with the nuke - drWoof - 08-24-2018
The fact that sending the exact packet needed doesnt yield a reply or anything is still a bug, though.
RE: MechComp powernet networking component doesnt want to work right with the nuke - Wilbur Wright - 08-24-2018
(08-24-2018, 01:35 AM)drWoof Wrote: The fact that sending the exact packet needed doesnt yield a reply or anything is still a bug, though.
It does! You just need to know how, where, from and to send it!
p.s. Disclaimer: Honest opinion here. This is only worthwhile if you're after a mind-numbing challenge. If you really want to blow up the station I suggest just wiring a nuke up directly to the station and setting it off with a terminal as usual. Much less time and effort given that the solution isn't very practical. Alternatively, utilise canbombs.
RE: MechComp powernet networking component doesnt want to work right with the nuke - drWoof - 08-24-2018
Still, looking at the nuke code it doesnt SEEM like there is a reason for it not to work like I tried to make it to work.
Unless the nuke code got changed somewhere along the way.