IF it's just for development and you plan to ship on Windows in the end then just pick whichever distro suits you really.
So really - just pick a distro that works for you with all your hardware, GPU, CPU, WiFi, get the editors you like and that is it.
If all you want to do is program games then the differences between main distros (Fedora, Ubuntu, etc.) are not of any significance to you unless you require something closed you can't easily get otherwise that only Ubuntu has in repos or pick a spartan distro like Arch (which I know nothing of, except for the fact that every single Linux knowledgeable person I met says it's spartan and not 'easy' like other distros...).
I personally use Fedora with some extra repos and used Gnome, KDE and Xfce both at home and at (non-gaming) work rather successfully for all my needs (basically - web browsing, occasional game via WINE and Python, Lua, C and C++ programming).
The only issue I can think of is GPU drivers for NV, but I have an old Intel integrated card which works flawlessly on Fedora so I can't comment much here.
For Lua and Python I use Geany and for C and C++ NetBeans, and for quick small edits or remote edits on a server I use vi or vim, but there are tons of editors and IDEs of varying heaviness for these and other languages (Kate, KWrite, CodeLite, MonoDevelop, CodeBlocks, KDevelop, Eclipse, ZeroBrane, vim, sublime, VS Code, ...) out there that work on Linux. I find many of them very capable and adequate, even compared to VS.
But almost none of these tools are special and they come on most of mainstream distros, at worst you will have an exercise in compiling something yourself...
The only extra advice I can give is to learn the tools (lua, gcc/clang, etc.) and bash (or any other shell you pick, zsh, ksh, I just use bash because it's the 'default' one) properly to be able to solve any miscellaneous problems that may pop up with tools and your game but don't hold back or shy away from rich GUI IDEs and editors in favor of vim just because you're on Linux now and "that's how pros do it". Don't go too overboard with this either, just cd, ls, grep (with just strings, no regex knowledge), vim and xdg-open (open a file in 'default' app) with little to no parameters gets you a looong way IMO, it's quicker to navigate directories this way even. But of course it never hurts to learn a little more of this on the side, organically, too.
I recall one very pragmatic Linux advocate saying that with Linux tools, unless you 'edit text files for a living' you will miss something.
But.. programming is editing text files for a living so I feel quite at home programming on Linux. :P