From 83077d7005f74ad62e29f3b5d38ce24369ea248f Mon Sep 17 00:00:00 2001 From: AardCrowley <12467582+AardCrowley@users.noreply.github.com> Date: Wed, 15 May 2019 17:11:03 -0400 Subject: [PATCH] Update README.md --- README.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 17cf5df..89d8368 100644 --- a/README.md +++ b/README.md @@ -18,28 +18,28 @@ Once he's been added, you'll simply type /newbot in order to create your first b # Getting your Chat ID -The next step will be to get your chat ID. The easiest way I've found to do this is to send a test message in your new Bot channel, then go to the following page: https://api.telegram.org/bot/getUpdates (where is the token you got in the last step). Upon heading to the site, you'll see a JSON-formatted list of information. Look specifically for the table "chat", which has an "id" field. Copy that ID (including any negative symbols). +The next step will be to get your chat ID. The easiest way I've found to do this is to send a test message in your new Bot channel, then go to the following page: https://api.telegram.org/bot<token>/getUpdates (where <token> is the token you got in the last step). Upon heading to the site, you'll see a JSON-formatted list of information. Look specifically for the table "chat", which has an "id" field. Copy that ID (including any negative symbols). # Putting it all together Now, open the plugin and make the following changes. Where it says: -chatID = <your chat ID> +chatID = <your chat ID> -replace with the ID you picked up from the previous step. Where it says: +replace <your chat ID> with the ID you picked up from the previous step. Where it says: -apiToken = "" +apiToken = "<your bot token>" change it to say: -apiToken = "bot" +apiToken = "bot<token>" -where again is what you received from creating your bot. It is imperative that "bot" precedes it. The plugin will not work without it. +where <token> again is what you received from creating your bot. It is imperative that "bot" precedes it. The plugin will not work without it. From here on out, it should work out of the gate. If you're wanting to add new triggers, locate the 'triggerLines' portion, and add your trigger as such: -{name = "", match = "", message = ""}, +{name = "<name of your trigger>", match = "<the trigger pattern to match>", message = "<text you want sent>"}, As long as you follow that format, you should be able to add as many triggers as you like. If you have any questions or difficulties, please feel free to drop me (Crowley) a tell or a note on personal board. \ No newline at end of file