As the title says. I severely dislike having to make accounts for every game publisher that wants to send me advertisements, collect data or whatever.
It’s usually an instant dealbreaker for me at this point
Publishers needing their own launcher already puts them on shaky grounds with me.
But I really liked the original BG 1 & 2, so I’m willing to not just refund it immediately and actually ask around first for solutions.
Thank you for the info on this, will be using it going forward.
Not sure if you did this on purpose, or if something else did it as part of editing, but your bulleted steps included an en dash (–) instead of two short dashes (–).
Have had issues in the past with that, generally with WYSIWYG type editors combining your – into either – or —.
I typed them directly into my comment from an Android phone, and it continues to display as two hyphens/minuses for me. Are you it’s not your client trying to be clever?
Ugh word does this. I didn’t realize until I wrote some documentation for a cli tool I made for a client and I wrote the documentation in word because they are fairly non technical so I wrote in the documentation sample arguments they can copy and paste and shipped it feeling good that it would work flawlessly because I tested the crap out of it. Or so I thought because they immediately hit back with it doesn’t work. I spent hours recreating their environment and watching it work no matter what I tried to get it to not work. Then I hopped on a call and had the client step by step show me what they did and they opened the word doc and copied the example commands, changed the arguments to be correct and run it. I followed along on my own machine and then I fucking saw what had happened. Fucking Microsoft Word replaced my " " with “ ” (straight quotes for smart quotes for those who cant see the difference). A quick patch of the cli to properly parse those and things were working again.
Copying out of MS products always seems to leave junk behind. The worst one is the zero-width space (unicode U+200B or hex e2808b) . Sharepoint loves to scatter these all over so any copy from a sharepoint source has to be put in a plain text editor and have a run through with a regex to find any invisible formatting characters.