Difference between revisions of "Update Profile Info"
GrumpyGecko (talk | contribs) |
GrumpyGecko (talk | contribs) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | GeckoBot tracks almost all info from the player profiles, if these profiles are updated regularly. There are three different ways to update: | |
| + | # Forwarding the <code>/me</code> output from the game to @Geckos_Bot | ||
| + | # Forwarding the <code>/heno</code> output from the game to @Geckos_Bot | ||
| + | # Using the API and then using the command <code>/up</code> to force a profile info update from the API. | ||
| + | |||
| + | All these things will trigger a reply from GeckoBot, containing the overall lifetime XP-Graph of the player and a message with some info about daily XP gain and an estimate about the time of the next level-up. | ||
=Updating the profile manually= | =Updating the profile manually= | ||
| Line 8: | Line 13: | ||
If you activated the API access with the command <code>/auth</code>, you can PM @Geckos_Bot the command <code>/up</code>. This will trigger the typical reply you'd also get when sending a /me or a /hero, but instead of reading out the info from the messages, the new info comes from the API. It will also stop sending the hint how you can update your profile via API, since you obviously just used the API command. An example output can be seen in the following picture. It is basically the same output you'd get when forwarding your profile messages directly. <b>BUT!</b> Updating the profile via API means that certain values can't be read out. The total mana is not a value that is published via API. This means that the potential mana tracking graph and the corresponding analysis of the mana development will fail, due to missing data. | If you activated the API access with the command <code>/auth</code>, you can PM @Geckos_Bot the command <code>/up</code>. This will trigger the typical reply you'd also get when sending a /me or a /hero, but instead of reading out the info from the messages, the new info comes from the API. It will also stop sending the hint how you can update your profile via API, since you obviously just used the API command. An example output can be seen in the following picture. It is basically the same output you'd get when forwarding your profile messages directly. <b>BUT!</b> Updating the profile via API means that certain values can't be read out. The total mana is not a value that is published via API. This means that the potential mana tracking graph and the corresponding analysis of the mana development will fail, due to missing data. | ||
[[File:Sending up.png]] | [[File:Sending up.png]] | ||
| − | <b>Note</b>: The profile info via API is updated automatically every 8hours. The script that requests all the profile info from the API regularly runs 4hours after the battles (I did not want to create another bot that kills the API directly before and after the battles due to tons of requests. I think updating in the middle of the in-game day is also good. | + | <b>Note</b>: The profile info via API is updated automatically every 8hours. The script that requests all the profile info from the API regularly runs 4hours after the battles (I did not want to create another bot that kills the API directly before and after the battles due to tons of requests). I think updating in the middle of the in-game day is also good. |
Latest revision as of 07:16, 28 June 2021
GeckoBot tracks almost all info from the player profiles, if these profiles are updated regularly. There are three different ways to update:
- Forwarding the
/meoutput from the game to @Geckos_Bot - Forwarding the
/henooutput from the game to @Geckos_Bot - Using the API and then using the command
/upto force a profile info update from the API.
All these things will trigger a reply from GeckoBot, containing the overall lifetime XP-Graph of the player and a message with some info about daily XP gain and an estimate about the time of the next level-up.
Updating the profile manually
You can PM the bot (@Geckos_Bot) your /me or your /hero and you'll get a graph of your all time XP gains and a message with an estimate about the time until your next level up. The next picture here shows an example output of sending a /me to the bot.
Updating the profile via API
If you activated the API access with the command /auth, you can PM @Geckos_Bot the command /up. This will trigger the typical reply you'd also get when sending a /me or a /hero, but instead of reading out the info from the messages, the new info comes from the API. It will also stop sending the hint how you can update your profile via API, since you obviously just used the API command. An example output can be seen in the following picture. It is basically the same output you'd get when forwarding your profile messages directly. BUT! Updating the profile via API means that certain values can't be read out. The total mana is not a value that is published via API. This means that the potential mana tracking graph and the corresponding analysis of the mana development will fail, due to missing data.
Note: The profile info via API is updated automatically every 8hours. The script that requests all the profile info from the API regularly runs 4hours after the battles (I did not want to create another bot that kills the API directly before and after the battles due to tons of requests). I think updating in the middle of the in-game day is also good.
