Welcome to the ZDoom Forums!

OK, thanks for trying. Not a problem. I don't add new games so often, and if so i know to handle it.

Initial keybinds are done through some in-WAD initialization. Also doing it through autoexec.cfg will result in an order-of-execution problem.
I'll be honest here, this is too insignificant to fix.

bind w +forward
bind q +left
bind e +right
bind s +back

bind r +moveup
bind y +movedown
bind a +moveleft
bind d +moveright
bind v +movedown
bind g +moveup

bind b +land

bind f +use
bind z +zoom
bind c +crouch
bind space +jump

I have a file called autoexec.cfg with the following content:
[code]bind w +forward
bind q +left
bind e +right
bind s +back

bind r +moveup
bind y +movedown
bind a +moveleft
bind d +moveright
bind v +movedown
bind g +moveup

bind b +land

bind f +use
bind z +zoom
bind c +crouch
bind space +jump
[/code]

The integration of this file doesn't work, when a game is startet at very first time.
GZDoom has to be closed and opened again to get these key bindings work.

This is reproducable.
Remove all [WoolBall.*]-sections fom ini-file. Start GZDoom. Choose "Rise of the Wool Ball". Bindings doesn't work.
Close GZDoom. Start it again and choose the game again. The key bindings now will work as well.
Woolball is just an example. It's reproducable with any supported game.

Tested with today's nightly build. Commit: https://github.com/coelckers/gzdoom/commit/2ff492d005ede2966671bb927143e0feefd4d4bb