4 hours ago, fathamburger said:
As for the FB/Unity SDK Changes, are you talking about stuff completely deprecated? or stuff they have to leave out until they update for newer interfaces or dependencies?
I am talking about functions that use to work and then sudenly don't because of a clash between software.
For example in Unity 2017 the IGraphResult call from facebook no longer provides the profile pic as a texture. So you are forced to either use www redirect(Unity's www function is very bad) or you need to go into the Facebook SDK and fix it yourself.
Now as you can think this is just the very basics. When I was still using Unity 5.4 and I think it was the Facebook SDK 6 I spend hours online with there customer care because almost none of the payment functions worked. We had to rewrite more than half the code to get it to work.
At the start of this year I helped a small team where the developer submitted a game first to get publishing permissions then later decided to add payments. Of course the payments did not work and he was told to submit it for approval again. Except he was latter inform by Facebook that the game had already been submitted and approved. Then after a few days to fix this problem he was told to delete the app and to create a new one and submit again. He did this without telling the team. We logged in as normal using our testing tokens and got our facebook profiles blocked. Took me a week to get mine unblocked.
The worst part about that story is that it was probably just a boolean that was set wrongly and gave me a weeks worth of problems.
4 hours ago, fathamburger said:
As for whether Enjin will be just as half assed? maybe, maybe not.
It isn't half assed, that is the problem. Facebook SDK uses 3rd parties just like so many other payment methods, these days it's a miracle if you get any software that doesn't need a java update. The easier software is to use the more third party plugins you will need to keep updated to use it.
And as for blocking peoples accounts, that is just a factor we have to deal with if we want to protect our self and our clients from robbery.
4 hours ago, fathamburger said:
from lack of experience i.e. team has fintech but not gaming background or something
Normally a team like this has at least one real programmer on it, so more often the confusions happen because of poor or outdated examples and lack of documentation.
In truth all problems I have experienced with payment options is either related to software clashing when updated or code used wrongly because the function had one value changed and no one updated the documents because they thought people would see it and understand.
4 hours ago, fathamburger said:
I'm really fishing for specifically badly designed payment solutions
If you are really looking for badly designed payment gateways why not go to a user review site or check some of the smaller payment options?
If a gateway works it grows large fast, while the ones that fail die faster. With adverts developers are mistrusting from the start so only a few make it.