SRL Archive - Research & Development Lounge

These functions could be used in the empty AutoTalk.scar located in the Core file of your SRL Include's Folder.

TypeTalk (Normal Speed):

{*******************************************************************************
procedure TypeTalkNS(SentenceOne, SentenceTwo, FKey1, FKey2: Integer);
By: IP-Drowner
Description: Using TypeSend, press your select FKey number to type that sentence.
*******************************************************************************}

procedure TypeTalk(SentenceOne, SentenceTwo, FKey1, FKey2: Integer);
begin
 if(IsFKeyDown(FKey1)) then
  begin
   TypeSend(SentenceOne);
   repeat
     Wait(1)
   until(not(IsFKeyDown(FKey1)))
  end;
 if(IsFKeyDown(FKey2)) then
  begin
   TypeSend(SentenceTwo);
   repeat
     Wait(1)
   until(not(IsFKeyDown(FKey2)))
  end;
end;

TypeTalkSS (SpamSpeed):

{*******************************************************************************
procedure TypeTalk(SentenceOne, SentenceTwo, FKey1, FKey2: Integer);
By: IP-Drowner
Description: Using TypeSend, press your select FKey number to type that sentence.
*******************************************************************************}

procedure TypeTalkSS(SentenceOne, SentenceTwo, FKey1, FKey2: Integer);
begin
 if(IsFKeyDown(FKey1)) then
  begin
   SendKeys(SentenceOne + Chr(13));
   repeat
     Wait(1)
   until(not(IsFKeyDown(FKey1)))
  end;
 if(IsFKeyDown(FKey2)) then
  begin
   SendKeys(SentenceTwo + Chr(13));
   repeat
     Wait(1)
   until(not(IsFKeyDown(FKey2)))
  end;
end;

Well, at least it is something to add into the AutoTalk.scar file.

procedure TypeTalk(SentenceOne, SentenceTwo, FKey1, FKey2: Integer);

Sentence one and Sentence two should be strings, not integers. You'll get a type mismatch.

Sorry, no offense, but its not auto-talking if a human interferes…

EDIT: (still no offense)

SendKeys(SentenceTwo + Chr(13));

HOLY SHIT GET THE BOMB SQUAD!

I highly… Extremely… Ultimately… recommend using just the TypeSend :p

Auto-talking should not include a human to do anything. Autotalk should be something with GetTextAtEx, finding the writer, answering humanly (Cases with different versions of the word) and stuff like that.

-Knives

I thought Auto Talkers had to press buttons to send a sentence. Because when i see Auto Talker scripts they request to press an FKey to type that sentence.

From: King of Knives
Auto-talking should not include a human to do anything. Autotalk should be something with GetTextAtEx, finding the writer, answering humanly (Cases with different versions of the word) and stuff like that.

-Knives

That's called Auto-Responding…not Auto-Talking.

From: Santa_Clause
That's called Auto-Responding…not Auto-Talking.

Thank you! I knew it was the right title.

But this part of code could help beginners a lot when they're creating some basic autotalking scripts.

Bah, Santa. I think SRL's AutoTalk is meant to be AutoRespond. AutoTalkers are pretty (no offense) useless, since it would require the user to sit next to the computer at all times. Which is what we don't want to :D

From: IP-Drowner
But this part of code could help beginners a lot when they're creating some basic autotalking scripts.

This would basically be their entire script…

-Knives

From: King of Knives
Bah, Santa. I think SRL's AutoTalk is meant to be AutoRespond. AutoTalkers are pretty (no offense) useless, since it would require the user to sit next to the computer at all times. Which is what we don't want to :D


This would basically be their entire script…

-Knives

Yes I think its what they mean. After all there is a procedure called AutoRespond in AutoTalk.scar. I wonder if anyone is actually building that?

Well, at least it is something to put in there. As i think there'll be nothing in there either.