**UPDATES TO ENLISTMENT GIFTING EVENT:**
To prevent exploitation, we will prevent new Accounts from being able to Gift enlistment crystals. We will also be taking action on those who are using 3rd Party Sellers, Bots and other farms to gift themselves mass amounts of Enlistment Crystals. Lastly, we will be adding an expiration timer to Enlistment Crystals. All unopened Enlistment Crystals will expire on Oct 18 @ 17:00 UTC. For more information, please see this post: https://forums.playcontestofchampions.com/en/discussion/346104/updates-to-enlistment-gifting-event
To prevent exploitation, we will prevent new Accounts from being able to Gift enlistment crystals. We will also be taking action on those who are using 3rd Party Sellers, Bots and other farms to gift themselves mass amounts of Enlistment Crystals. Lastly, we will be adding an expiration timer to Enlistment Crystals. All unopened Enlistment Crystals will expire on Oct 18 @ 17:00 UTC. For more information, please see this post: https://forums.playcontestofchampions.com/en/discussion/346104/updates-to-enlistment-gifting-event
Comments
@Kabam Miike
@Kabam Vydious
well then its lucky you have a help 4 button on there so you dont have to click them on by one
It would be a problem only if the Hell All button send a bunch submits, sending individually every Help.
But only very amateurs developers would design it in that way.
The Help All button would send ONE submit, packing the whole helps.
In fact, this design would be safer for the servers, because it would prevent thousands players sending submits for hundreds champs.
Anyway, if they cannot handle their userbase, it's not a excuse, they should invests their revenues improving their platform.
The problem with all the speculation surrounding this issue is that basically all of it doesn't appear to reflect how these games generally work. If I had to guess, I would say the problem is that the action of requesting help for a single champion is an atomic request that can't be trivially "packaged" into a multiple request action because the front end doesn't work that way. The game client seems to do most things with HTTP(s) XML or RPC requests through a Google cloud front end. There are probably architectural limits to what you can do with such a front end that make retrofitting the request system after the system was implemented non-trivial. The alternative would be to use a pass through, but the back end servers probably aren't designed for that kind of computational load.
The complicating factor here is that the front end processing is probably happening with relatively state-light web apps that have to synchronize across a global database, probably Cloud SQL, maybe something else. If transactional latency exceeds a certain amount, it would probably cause issues with the game clients. Forcing the help requests to be singular and serialized is probably a form of pseudo throttle. Tampering with that without understanding the dynamics of the game system sounds like a good way to get yourself fired.
Anyway, it's a fact it's not true a Help All bottom will screw the servers because it's not true a Help All should be hundred submits (as was stated at the beginning)
It's a fact a Help All feature could be and should be one submit packing the whole data, and it's a fact do it is not Alien technology.
It's a fact Kabam's developers knows how do it and can do it because it already was done in the Help 4 bottom.
We already can Give packs of helps but "cannot" Ask packs of helps because "it's technologically impossible". Of course, it can. It's not necessary to make a mountain from a mole hill.