📝 End Users neglecting documentation.. about monigomani HOT 10 OPEN

Hi there,

I did not like your comments above on my issues. Your way of response is a good evidence on your arrogance and very weak communication skills. You could simply direct me to the exact portion of your bad documentation that answers my question or leave it open for good people to answer if your "precious time" (haha) does not allow you to answer!!!

from monigomani.

Hi there,

I did not like your comments above on my issues. Your way of response is a good evidence on your arrogance and very weak communication skills. You could simply direct me to the exact portion of your bad documentation that answers my question or leave it open for good people to answer if your "precious time" (haha) does not allow you to answer!!!

#20 (comment)
^ @edebie quote: "do we need to optimize the bot before every run? and how?"

The answer to your question is even in this GitHub Issue here (my 2nd last line with no in fat), so you did not even read that fully?
Following warning I have displayed on the home page, documentation page & every release version published:

WARNING: MoniGoMani should always be re-optimized after doing manual changes!
You need to optimize your own copy of MoniGoMani while thinking logically, don't follow your computer blindly!

Please elaborate how you missed this? Maybe I should reference it even more?...
You clearly show that you did not take the effort to read any / all documentation... I do not need to spoon feed you & I don't have time for that..
Now leave GitHub issues for actual software bugs, read first and then use the allocated Discord #moni-go-mani-help channel if you still have questions...

from monigomani.

You could consider enabling github discussions? Sort of fills the gap of general question that might be bug scenario and keeps the communication close to the code (something discord misses out on in my opinion).
I enabled it for my algo trader and while I don't have the same amount of users, it seems to work well (and is easily searchable)
https://github.com/mr-highball/simplebot-support/discussions

I will not do this on purpose.
It's too prone to re-attract leeches that will abuse it for already documented/asked/answered questions.
We'll stick with this place only being for actual bug reports & new issues, the Discord #moni-go-mani-help & #moni-go-mani-testing channels really suffices for these sorts of questions in my eyes.

Furthermore, there other users can take the load of my shoulders by replying towards other users questions + there the expectation isn't so high that I'll answer upon all questions.

from monigomani.

#20

from monigomani.

#19

from monigomani.

#18

from monigomani.

You could consider enabling github discussions? Sort of fills the gap of general question that might be bug scenario and keeps the communication close to the code (something discord misses out on in my opinion).
I enabled it for my algo trader and while I don't have the same amount of users, it seems to work well (and is easily searchable)
https://github.com/mr-highball/simplebot-support/discussions

from monigomani.

#56

from monigomani.

Documents in wiki link to 404

from monigomani.

Documents in wiki link to 404

You currently need to be on the development branch documentation as mentioned in the warning at the main branch documentation in the wiki.
v0.12.0 is highly outdated & doesn't follow the new documentation format yet,
due to main currently being so outdated it's good that it's documentation can't be easily found, this will nudge more new people towards the development branch for now.
The wiki is already prepared for documentation format of the next release.

from monigomani.