I think it can help (against user reports), and it definitely doesn't harm to do so.
A way I've done it in the past (not really needed as you can pause the bot ofc): Add query box that's toggled up on some key-combo, where you would input text that your bot will then write in the chat. This is also nice to have if you are around when some random "stranger" talks to your bot, could stop it from being reported, that is without having to pause or stop it.
I see some say that it would probably _increase_ the chance of being reported, idk why they say that, I see no obvious reason for that. Say, you meet up with your bot, chat for a little while with it, trade, and leave.. then it goes back to doing whatever. Like if people spotted that conversation, I'd doubt they'd report your bot anytime soon.
This will halt the bot (pause it) when keycombo is pressed, so you don't have to pause it in any other way, so you can easily take control over it (walk it to wherever you are).
Simba Code:
const
CHATCOMB = [VK_CONTROL, VK_SHIFT, VK_I]; //three keys.
{==============================================================================]
|Call this in your main loop
|Note:
| The reason it checks each key three times in diff order is to ensure that all
| the keys are down at the same time.
| This is to work around a limitation of Simba's IsKeyDown function which caches
| the keys pressed until the function is called (aka the key doesn't have to be down)
[==============================================================================}
procedure CheckForUserinput();
var output: String;
begin
if IsKeyDown(CHATCOMB[0]) and IsKeyDown(CHATCOMB[1]) and IsKeyDown(CHATCOMB[2]) and
IsKeyDown(CHATCOMB[2]) and IsKeyDown(CHATCOMB[0]) and IsKeyDown(CHATCOMB[1]) and
IsKeyDown(CHATCOMB[1]) and IsKeyDown(CHATCOMB[2]) and IsKeyDown(CHATCOMB[0]) then
begin
InputQuery('Chat message', 'Chat:', output);
WriteLn(output); //replace with chatbox.send(output) or whatever it's called
end;
end;
begin
repeat
CheckForUserinput();
until False;
end.
Extending on the note in the code, if this is not done, and you pretty much sequentially (in any order) presses "ctrl" "shift" and "i" the query box will pop up.
Simba should export both GetAsyncKeyState, and GetKeyState so that we can work around it as the correct thing for IsKeyDown is to use GetAsyncKeyState, instead of GetKeyState, and Simba doesn't really use GetKeyState correctly anyway.
Happy coding!
Edit: This reminds me when I just for fun sake connected my bot to cleverbot, it would talk as long as someone else was talking (while power-mining), people talked back as if it was human..
it was ridiculous to watch, so much random gibberish, out of context talking.. and people talked back to it.. It said the dumbest shit like "Do you play RuneScape?", lol. PS: Blocked out any text that contained "cleverbot".