[addons_zz]

Originally Posted by HamletEagle Just to make things clear. We have nothing against you, and you are free to post plugins here, but please post something as original as possible, which make sense and preferably a quality plugin. If you just fixed some bugs then you should post in the plugin thread. If you want to take over the plugin at least try to contact the author, if he does not respond PM an approver and tell him that you want to start developing this plugin. For me, at this moment, it seems that you just removed features that you don't understand. Don't do this, and take over a plugin only if you fully understand it. A plugin is not unmaintainable just because it has a lot of features, it become so when the coder don't know how to fix or improve the code. Running two map chooser plugins at the same time seems a bad ideea, Galileo was able to do everything.

Hi, sorry for my rudeness, It is just my beginning and the moods is all changing. The plugin I am talking, AMXX Dev Team NextMap is no a map chooser, it is a plugins that creates the cvar amx_nextmap, and guarantee that when maps changes, is to the amx_nextmap cvar, instead the orignal game mapcycle, file. So to became less cumbersome maintain galileo, is more obvious to let the original and do that task. There is no need to galileio assume that task if already there is other plugin doing that. It just let the code bigger and bigger and bad to maintain.

So now on, all the time a remove a feature I will redirect to the original plugin who do that, and make available they thread to others install or not with Galileo.

But if in the beginning you are talking about running galileo with a paused mapchooser, from AMX Dev Team, there no problem about that. Running they together just makes the vote happens twice. One after other, and who wins is last one.

But off course, i expect that the admin user, manually disable others mapchoosers by himself.

"it seems that you just removed features that you don't understand"

Exactly. I am removing feature that I dont want to expend time to understand because I can install a third part plugin who accomplish that. So there is no need to make a galileo a new Amx Galileo Super with lots of plugins. I will keep him specialized at votemap, and his actual addicional features that already has third part plugin specialized, i will link to then at galileo thread. Explaining to the new user that some old features now need others third part plugins.

What I am applying here is the principles of software engineering. Keep it small and concise. If you are disagreeing with that, you problem is not with me, is with the software engineering techniques. Here the Software Engineering Institute, a reference at software engineering.

"A plugin is not unmaintainable just because it has a lot of features"

And sure it became unmaintainable because have a lot of features to a new programmer at it, that see no reasons to accomplish all those features at one plugin, when there is others to accomplish the same requisites. So just let they developers maintain they plugin and I maintain my and keep his good at his features. And when the admin/user want to use my plugin, this admin/user install my plugin and the third part specialized ones if they want those features too. And be happy.

I don't mean to be rude, best regards.