search

Aida-Enna / MognetPlugin

A simple plugin which allows you to send your Final Fantasy XIV parse data as a POST request to your server.
13 stars 20 forks source link

Token Not Working with ACT & Is this bot still being managed?? #4

Closed yoloswaggyx closed 5 years ago

yoloswaggyx commented 5 years ago

When I put in the token into ACT and click apply the token disappear and everything is blank. Also, if the developer is no longer managing this bot please update the description that it's no longer being updated, because I spent time downloading and installing the bot and token just to find out it doesn't work and now I found out your last post was months ago.

castanhob commented 5 years ago

Probably having the solution by today @yoloswaggyx

castanhob commented 5 years ago

@yoloswaggyx Probably solved after 0.2.0 release. Could you please confirm before I close the issue?

luisk2094 commented 5 years ago

For me it works fine, the only thing is the labels on the configuration i think. I use them as follows to get this kind of notifications imagen imagen

yoloswaggyx commented 5 years ago

I will re-download and test. Thanks

yoloswaggyx commented 5 years ago

I am able to connect with token and it shows my discord and channel. Tested on striking dummy and it works. Tested in 24man raid and there is an error. As you can see, first boss it worked but anything after that was getting errors.

capture

castanhob commented 5 years ago

@luisk2094 You mean some of the attributes not showing in the Discord channel? If that's the case, even if an attribute is marked (such as Max Heal, for example) and it sends an empty data (no healing at all during the fight), it won't show in the message. Is that the issue?

castanhob commented 5 years ago

@yoloswaggyx I noticed that there's an issue with 24man raids. Due to the amount of people and information sent to Discord, this error may occur (the log shows a generic error though). The issue is that Discord have a max lenght limit of 2000 characters per message. I'll change the server side, together with the refactoring, so it checks and breaks the message into two pieces in case it exceeds the 2000 characters limit. Since this is not related to this particular issue, I'll open another one, so I remember to fix this. Thanks for the report!

luisk2094 commented 5 years ago

@castanhob no, i meant like to get the max hit displayed i needed to check the critical hit label or something like that, still its not a big issue :D

yoloswaggyx commented 5 years ago

Thank you for the quick response. I will keep testing for any other bugs I find. I will also keep an eye out for the 24 man fix. Thanks!

yoloswaggyx commented 5 years ago

@castanhob Hello, There seems to be an issue with the attribute selection and what is being posted by the bot. We have tried removing the token and creating the token and it seems to not update with the new attribute when selected. I posted screenshot of the discrepancy. As you can see I selected direct hit% and crit% , but the bot post direct hit crit%.

capture capture1

luisk2094 commented 5 years ago

@yoloswaggyx yeah, that was what i meant. What i did to get the ones i wanted was testing one by one the labels until i got the desired values xD

castanhob commented 5 years ago

Thanks @yoloswaggyx and @luisk2094 , I actually identified this issue with the labels. I will keep this issue to track the bug, and will solve it on the next release (together with the auto-updater).

castanhob commented 5 years ago

@yoloswaggyx @luisk2094 the issue is probably solved by the last update (v0.3.0)!. Please let me know if you find any other problems!

luisk2094 commented 5 years ago

yeah, now it works great. Also thanks for the hours filter, that seems useful