|
Size: 1931
Comment:
|
Size: 2010
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was renamed from WhisperPause {{{#!wiki solid '''Special thanks to !SumRandomGuy for this guide.''' }}} |
|
| Line 8: | Line 12: |
| In the following scenario, we have the following actors: SRG is the supporting defender; I'm always online. GBA is the Guy Being Attacked; he's sleeping |
In the following scenario, we have the following actors:<<BR>> SRG is the supporting defender; I'm always online.<<BR>> GBA is the Guy Being Attacked; he's always sleeping. |
| Line 12: | Line 16: |
| SRG issues the following whisper: | SRG issues the following whisper:<<BR>> |
| Line 15: | Line 19: |
| GBA sees in his Commands window: | GBA sees in his Commands window:<<BR>> |
| Line 18: | Line 22: |
| GBA provides this hash to SRG. That's HIS specific key. No one else can use it. Now, when SRG sees GBA being attacked at some later time, he can do this: | GBA provides this hash to SRG. That's HIS specific key. No one else can use it. Now, when SRG sees GBA being attacked at some later time, he can do this:<<BR>> |
| Line 23: | Line 27: |
| Caveats: 1) Whispers can be monitored on the server, think about the implications of using these scripted commands and how easy they are to find in logs. 2) You can't revoke a whisper pause hash. If SRG joins the reds sadness will ensue. Only give a hash to those you trust. 3) 1 hour is the minimum amount of time you can pause a remote bot. |
Caveats: <<BR>> 1) Whispers can be monitored on the server, think about the implications of using these scripted commands and how easy they are to find in logs.<<BR>> 2) 1 hour is the minimum amount of time you can pause a remote bot.<<BR>> 3) You must delete relaykey.sol from the flash storage folder on your computer to remove everyone's access. There is no //delete command.<<BR>> 4) It is also important to note that whisper hashes are not segregated by server number, so if you give SRG a hash key, and both of your user names are the same on a different server, then he can use the same hash code on another server to pause your bot on that server too. |
| Line 30: | Line 35: |
| Note from TOFH: You can reset all your whisper hashes by removing the file "relaykey" from the local shared object. It is also important to note that whisper hashes are not segregated by server number, so if you give SRG a hash key, and both of your user names are the same on a different server, then he can use the same hash code on another server to pause your bot on that server too |
Special thanks to SumRandomGuy for this guide.
I've received questions about this enough times to write it up. Here's the instructions.
OK, sometimes it's necessary to pause someone's bot remotely so it doesn't kick you out while defending.
This HAS to be set up ahead of time; can't just have people pausing other people's bots, can we?
In the following scenario, we have the following actors:
SRG is the supporting defender; I'm always online.
GBA is the Guy Being Attacked; he's always sleeping.
SRG issues the following whisper:
/GBA //pause
GBA sees in his Commands window:
18:08:11 Receive from SRG: pause , hash = e2966f3e
GBA provides this hash to SRG. That's HIS specific key. No one else can use it. Now, when SRG sees GBA being attacked at some later time, he can do this:
/GBA //pause e2966f3e 2
The 2 on the end says to pause for 2 hours. If it went well, SRG will get a whisper back saying "Pausing for 2 hours."
Caveats:
1) Whispers can be monitored on the server, think about the implications of using these scripted commands and how easy they are to find in logs.
2) 1 hour is the minimum amount of time you can pause a remote bot.
3) You must delete relaykey.sol from the flash storage folder on your computer to remove everyone's access. There is no //delete command.
4) It is also important to note that whisper hashes are not segregated by server number, so if you give SRG a hash key, and both of your user names are the same on a different server, then he can use the same hash code on another server to pause your bot on that server too.
The upsides are that a bot with a timing problem won't kick you out when you're trying to defend. People are MUCH better defenders than the bot any day. You also know that when you received the "pausing for 2 hours" message, it was a bot online and not a human.
![[+]](/moin_static/explorer/img/toggle1.png)
![[-]](/moin_static/explorer/img/toggle0.png)
