Originally posted by hgdagon
View Post
I use notepad as my frontend.
But seriously, it makes not a big difference if you had a gui for that.
Because of the descriptions.
It is no secret, that almost nobody reads readme´s. So the description must be at least directly after the auto_cvars inside the autoexec.
If it would not be there, people would have even more questions...
So, as a consequence, your gui would need to have these descriptions as well. And these are sometimes quite long, because I needed to explain some words what that auto_cvar does and so on.
So your gui would need a big "description" window beside the active auto_cvar.
If you look how the included sample autoexec is "designed", you will see that it summarizes auto_cvar´s in blocks to help the overview. And has the descriptions right after the auto_cvars.
In the beginning of the "small mod compilation" development, I did not have descriptions inside the autoexec. But after the auto_cvars became more and more it was unavoidable.
Nahuel offered to create a csqc menu for the "small mod compilation".
That would be possible, but the description text would be a problem and beside that, the continued increase of auto_cvar amount would need parallel updates for that as well.
I am sorry that I could not make it easier to adjust the features.
That is why I always thought quite long about their default setting. So that an adjustment is not necessary for the majority...
But that is impossible.
Some like it hot, some like it cold. We are all individuals.
I want to take the opportunity and thank Spike again, for creating the auto_cvar function and explaining me the usage in simple english words (I have problems with this language, hehe).
The possibility to adjust a mods features is really unique and without it, the "small mod compilation" would have died a long time ago because of different personal likings of its users.
I hope that you have a little bit fun with the "small mod compilation" nonetheless.
Kind regards,
Seven
Comment