Detailed View in JOBs to show response coder error.

Cyogenus commented 4 months ago

This feature request respects the following points:

[X] This is a feature request, not a question or a configuration issue; Please visit our forum first to troubleshoot with volunteers, before creating a report. The links can be found here.
[X] This issue is not already reported on GitHub (I've searched it).
[X] I'm using an up to date version of OpenBullet2. We generally do not support previous older versions. If possible, please update to the latest version before opening an issue.
[X] I agree to follow OpenBullet's Code of Conduct.
[X] This report addresses only a single feature request; If you have multiple feature request, kindly create separate reports for each one.

Description of the feature request

Rurri it would be nice in the detailed view of the bots to show The response Code like 429 or Ban or To many tries instead of showing BOT ENDED WITH STATUS: ERROR. This would be a easier to see what's going on with the bots instead of debugging every portal.

Is your feature request related to a problem

NO

Describe the solution you'd like

More Detail in the Detailed view.

Describe alternatives you've considered

No response

Relevant screenshots or videos

No response

Additional information

No response

ghost commented 4 months ago

you can do this enabling Bot Logging on settings,

however it is RAM intensive, so you should enable it only when debugging a config.

with it enabled, you can see every hit, custom or TO CHECK(error/no defined keycheck) complete responses clicking on the button designed for it. (only works with bot logging enabled)

Cyogenus commented 4 months ago

No it doesn't. I don't think you really understand what I mean. I already talked to Ruri about this and he knows what I'm talking about.

openbullet / OpenBullet2