About your topic, you are just bloating with useless and uneeded information, and as a result just confusing the end-user completely. You should always try to keep things as short and as straight as possible.
This can even stop people from using your plugin in the first place. Like they open the main page and see one giant wall of text. They'll say "it's too complicated, I want something simple".
For example:
Spoiler
Contributing
You are welcome to start contributing to this plugin. To do it just:
Learn how to use GitHub.
Fork it on GitHub. See here how to fork on GitHub.
Checkout on the `develop` branch.
To read the Contributing Guidelines.
To see the Issues List. The best way to start it is first fixing one trivial issue and
to perform its pull request and to see how it goes.
To see recent commits on:
https://github.com/addonszz/Galileo/commits/develop,
as:
https://github.com/addonszz/Galileo/...d3607734e5f60d.
To open and to comment on issues at the Issues List.
And to perform pull requests.
Uneeded, if someone is able to write code, they can figure out how to use github or they already know.
Quote:
Miscellaneous:
You need to disable nextmap.amxx.
You need to disable any other map choosing plugins, such as mapchooser.amxx.
|
This should be in the install instructions. Basically, what you want is a clear list of instructions. Like do x,y,z, short phrases without useless words. For example:
1.Copy x file in folder y.
2.Disable this and this and this.
3.Reload map.
Quote:
How to upgrade your Galileo?
Download the "galileo.amxx"
Replace your currenty installed version.
It is done.
|
Probably useless, it's obvious that the plugin needs to be reinstalled.
Having the entire configuration file in your post seems too much. People can just open the file after they download it. Also it's a pain to maintain, needs to be changed after each update that's messing with user settings.
You have a "The Galileo can:" paragraph and
Brief Features' list. Better to have only one paragraph where you explain everything related to features.
Consider placing credits inside a
spoiler.
Spoiler
Quote:
People just saying it is broken/lagging and do not help providing the requested information at the main's page
Support section, will be ignored.
I am not asking to you write code, I asking to just copy and paste something from your server. Then if you
cannot neither do just such a simple thing, it will be broken for ever or until you fix by yourself, or until
someday I/or someone else notice your problem on my/their server and copy and paste what I am asking.
If you cannot help me figure out what is wrong with the plugin, it is definitely not my problem, but it is all
your problem as, you will need to use it bugged or not use at all. Which is not relevant, you should use whatever
work better for your server, if you can find such. At least on my server it is working fine and I do not see
anything wrong with it. But if you are finding and fixing bugs and not releasing/sharing it, this is not good
from you to the others at all. Would you like I never shared the source code? That depends, if you got something
which works much better for your server, then this plugin is pretty much irrelevant to you and you would not care
whether I shared my coding or not.
Basically, I am assuming anyone which posts problems here and do not provide the requested information as trollers. Because:
I do not run a server where I can test behavior related to a running voting within several people.
I am not a magician or psychic to guess your server environment or how the plugin is behaving if you do not provide it.
Until now I was able to fix everything reported by users which collaborate.
HTML Code:
Maybe he's tired of supporting them. Maybe he doesn't use those anymore so it
doesn't make sense for him to support them. You can fork them if you like. You
could be the next maintainer as it is open source.
It takes time to support repos. Supporting repos is work. I know because I
support a bunch. It is often a thankless job. People always want something, but
often don't want to put in effort to contribute (even if it's just a simple
donation). People don't like to read the documentation and love to ask a
question you've documented and answered hundreds of times. People don't like to
follow instructions you give them to get your support.
With that said, there are people who do contribute. And there are those who
occasionally give thanks (sometimes verbally and sometimes with donations and
sometimes with pull requests). Those are the people that usually give repo
maintainers the motivation to keep supporting the project.
In short, sometimes it can just get tiring. And if you've moved on from your
project (you don't even use it yourself anymore), it might not make sense to
keep supporting it. Only tito can answer exactly why. But I imagine he either
doesn't use them anymore and/or is tired of supporting so many repos.
Why some packages are removed from Package Control?#facelessuser
|
This entire paragraph is completely unrelated with everything. Do you really think the user will read it? Like I said, don't add walls of text if they are not needed.
Compilations Data is again useless. Remember that you are writting the main post for regular owners, not for coders or for people that really understand that data. And again, do you think they care? They will even use the worst plugins ever, just because "it works".
Setting up a Mapcycle section should be right after features and install instructions. Try to group things together.