Yay right..lol. I did search and read and search and read.
Btw, thanks Rev for the help with my typo on github. So, this is what I get:
"[INFO] extDB3 v1.028 extension loaded"
"[extDB3] Startup..."
"[extDB3] ███ SQL_CUSTOM Protocol error! [0,""Failed to Load Protocol""]"
"[extDB3] ███ ERROR - Startup aborted"
[22:55:01:127672 -05:00] [Thread 3596] extDB3: SQL_CUSTOM: C:\Program Files (x86)\Steam\steamapps\common\Arma 3 Server\@extDB3\sql_custom\a3wasteland doesn't exist
[22:55:01:127672 -05:00] [Thread 3596] extDB3: Failed to Load Protocol: SQL_CUSTOM
and to top it off:
http://prntscr.com/f94t9a
thoughts?
Ok, so like I said I did some reading prior to posting this, which is what introduced me to ProcMon. Lovely tool.
Set my filters as such:
Process begins with: arma3
Path contains: a3wasteland
Tons of results, however, it did show that for some reason, the server isn't looking for a3wasteland.ini in sql_custom folder. Nope, it's actually looking for just plain old a3wasteland.
So, notepad++ open the ini, save as, scroll to the top and select all types (*.*)....boom a3wasteland without any extension and it works.
So, anyone having DB issues and it can't find a3wasteland, just save a copy of the ini file as a3wasteland without an extension. Til someone figures out a fix.
Just to put this out there:
32 and 64 work like this. Don't ask why.