tbf a standard and expected reply (re ease of use etc)
reality tho is different. these kludges ultimately only create entropy (confusion amongst inexperienced users).
My experience is to the contrary - there are many people who otherwise avoid Wine because they just want to be able to install and play. They don't want to spend time dealing with the potential complexity in setting it up themselves, having to trudge through compatibility reports in various places etc. and then possibly still fail to get it running for whatever reason, having wasted however much time that they would have preferred to spend actually playing the game.
My wrappers are much like what you'd get with official Wine-wrapped releases, except that I aim to provide a much better experience, with a higher degree of user control and more options for customisation than they typically allow.
a good doc IMO is >>>> wasting time on writing debugging maintaining such scripts and then explaining how to use them
Well both using them and explaining how to use them is pretty damn simple:
Step 0: (if not done already) install dependencies
Step 1: Put the wrapper + game installer files in one place
Step 2: Run the build script
Step 3: Run the game's start script
Anyway it's not like this stops anyone from setting it up manually if they would prefer to do that. I write compatibility reports too: https://www.gog.com/forum/general/the_judas_does_this_run_in_wine_thread_v1173
and I'm working on submitting reports to WineHQ's AppDB.
Oh, also I wrote a guide for using PlayOnLinux: https://www.gog.com/forum/general/the_try_linux_repostrewrite
I need to update it but it's still mostly accurate. I plan to write one for using Wine directly at some point as well.