Avoiding unwanted CCUs
Options
Hello,
our team is about to release a build to some testers and friends to get feedback, stress test etc. One thing I realized is that if somebody owns a copy of an old build, they could potentially use up CCUs by playing the old version. In a worst case scenario, someone could distribute said build and cost us money in monthly biils.
Is there any way to prevent said situation from happening? Perhaps by blacklisting game versions, or changing appids just before launch?
This won't be an issue after we release to steam, but if unsolved it prevents us from releasing public test builds in fear of people redistributing en mass and costing us money in the future.
Any solutions or advice are much appreicated.
Thanks,
-Carson
our team is about to release a build to some testers and friends to get feedback, stress test etc. One thing I realized is that if somebody owns a copy of an old build, they could potentially use up CCUs by playing the old version. In a worst case scenario, someone could distribute said build and cost us money in monthly biils.
Is there any way to prevent said situation from happening? Perhaps by blacklisting game versions, or changing appids just before launch?
This won't be an issue after we release to steam, but if unsolved it prevents us from releasing public test builds in fear of people redistributing en mass and costing us money in the future.
Any solutions or advice are much appreicated.
Thanks,
-Carson
0
Comments
-
Hi, simply create new app before launch. You can delete old apps in your dashboard.1
-
Thanks! This is the answer I was looking for. Sorry for the late replyOneManArmy said:Hi, simply create new app before launch. You can delete old apps in your dashboard.
0
