Nightly builds went offline when the server crashed and the server owner disappeared one night. It was entirely unexpected so there was no back up. Now tell me, what you are doing to fix it? I can tell you what I've been doing. I wrote a branch that will upload each nightly to github releases, but sadly that would add a tag for every commit, so we are probably going to drop that. I also added mingw support to citra, in addition to adding mingw build bot support. I'm just about to move the code over to upload to a different build host as well, and trying to see if I can set up multiple mirrors for releases as well so this never happens again. But no, lets just turn this into an "Us vs Them" where its those silly people over at github actually making the emulator that are the bad guys for not know that its impractical to have users compile citra. /rant
If you have a static build you shouldn't need any of the dlls. I dunno what you did wrong off the top of my head though.
Also that method misses a lot of the required dlls for dynamic builds. Use something like
http://www.dependencywalker.com/ dependency walker to find what dlls are still missing. (They should show up on the right in red if they are missing) Alternatively, you can just look at the list of DLLS that bleeding edge copies over and do the same
https://github.com/citra-emu/citra-bleeding-edge/pull/3 (Wow really! Its open source and we can all benefit from it??!) More specifically this list
https://github.com/jroweboy/citra-b...0793996b2e612f7435807cad314/appveyor.yml#L125
If you have a static build it shouldn't need dlls. Maybe one day I'll make a "unofficial" build to show everyone how its done