Geo

I'm not sure how that is a "must" though, it still works without doing that now.  And just to play out that user scenario a little further, what happens if...

Great start- I think decomposing the problem into 'types' of files like you did at the beginning is smart. One thing that may be missing as a category are 'local'...

One more format-specific thought- maybe its worth investigating a switvh to the eggdrop.conf.d naming syntax (renaming eggdrop.conf to that, and eggdrop-basic to eggdrop.conf; or whatever makes sense there

In short- need to fix telnet control response in 1.9, as it will affect the user-facing output an expect script could be relying on (unlikely, but still valid). Specific comment...

Thanks for the report- we're looking into this, the first two guesses are that it has something to do with unicode characters, and the server_raw/gotmsg functions not properly handling them

Can you run it on a bot for a few days? We'll tell you if the server explodes :)

So rather than delve into a matter of opinion on which is better (for the record, multiple configs out of a single directory is the intended usage, and your implementation...

I'll also throw out another non-technical solution you've probably already thought of, but consider using prefixes on your filenames like config_bot1.conf; user_bot1.user, etc so that similar files are grouped together...

The autobotchk script is intended to be run from the directory containing the .config file, or using the -dir flag. That should help solve any issues you have encounter with...

> "I can't make Floaty code open source because of the communication protocol, it has to be protected and not seen by all people." This right here should make you...