Misleading pinkcoin configuration filename

Hey guys :)

Tried helping a new member today and he was having problem figuring out how to add a configuration file to the directory.

After it having been pinkconf.txt in the past and this not working, we ended up trying pinkcoin.conf and it didn't work either. It turns out it's now Pink2.conf (that's correct or was this co-incidence by him getting connections as soon as he renamed this?) and this is not documented anywhere, at least not for the normal user.

With 99% of the other coins it's just coinname.conf so changing it to the generally accepted name would be beneficial in my opinion.

If not, would it be possible to maybe add some help file in the repo to make it easier for people to figure out how to name the configuration file or am I missing a tutorial somewhere?

There is another issue about the exact same problem that got closed before it was resolved, no idea why, so it's been something that has been on the list for quite a while it seems :)

[PinkDev]

We're trying to keep new users out of that directory, and encourage people to work with pinkconf.txt through the gui. I understand that there's a strangeness there for people that are used to accessing the file directly and for people running the daemon. I will update the code to look for pinkcoin.conf if no config file has been specified per the -conf argument and pinkconf.txt doesn't exist.

The pinkconf.txt file is accessible in the qt gui through the help>debug window menu on the information tab.

That said, if Pink2.conf is coming up, that raises serious concerns for me, as that is not, nor has ever been, an official configuration filename for Pinkcoin:

https://github.com/PinkDev/Pink2/blob/master/src/util.cpp#L1056

I need to know, is the user somehow passing the -conf=Pink2.conf flag? And if not, where did this new member obtain their pinkcoin binary?

After the chat in the Slack with caligo and the user, it seems that it must have been a coincidence with him changing the name of the .conf file and incidentally then receiving connections, as he got the client from the official site.

Thanks a lot for thinking of the daemon users here, it's indeed very much appreciated and totally understand now why there is a .txt file in place in the first place (actually something more coin developers should encourage for the casual user, so thumbs up!)