My team has just made the very concerning discovery (out of the blue) that the overview and revisions for CloudScript are suddenly called "Legacy".
Can you please elaborate PlayFab's plans and timeline for the future of CloudScript?
Having a live product in the market and spotting a fundamental change like this by pure chance is very concerning. We are not in a position to convert all of our functionality over to Azure functions.
Yes, I was also surprised to see it this morning.. I did not see any mention about it anywhere before.
What's the best place to keep up to date about those kind of upcoming changes?
@Rick Chen Hi Rick , but why would you remove cloud script Legacy from a project already using it , like mine: 4DD7B, and we were supposed to launch it days ago, and we can't change our functionality to Azure functions , Help !
Hello @Rick Chen, we have a live app and this change introduced two bugs. Our app isn't working now and we are getting customer complaints B95FB. We have been unable to resolve this problem and need assistance.
Legacy Cloud Script is enabled for title B95FB, please have a check.
Hi Playfab team @Jay Zuo, Pls enable Legacy CloudScript for below titles :
BC0DB , 734A9 , 5A475
Thanks in advance.
Hi @Jay Zuo @Rick Chen could you please enable Revisions for the title 9E28A as well? We have created game using our own studio with revisions pipeline (as Function were marked as "Preview" when we started and exited preview way after point we could switch) and now we need to transfer whole project to the client's newly created studio and title. But we cannot move revisions. Please help, we cannot rewrite hold thing using Functions on such short notice!
Edited 2022-01-06:
Since the General Availability of the Azure Functions Cloud Script integration, newly created titles no longer have access to the legacy Cloud Script service. We apologize for the lack of sufficient advance notice about this, but this is part of our move to fully integrate PlayFab as an Azure service, which will allow us to provide better and more consistent support to our community. We are fully committed to making sure developers that already have a significant investment in legacy Cloud Script can continue to use it.
If you need Cloud Script turned on for a new title, you should specify both the new title IDs that need it and the older Title ID in which you have been working.
We still recommend using Azure Functions as the Azure Functions has significant advantages over legacy Cloud Script:
Old post:
Even though the tabs in the CloudScript are called “Legacy”, as far as I know, there is no such plan to retire the CloudScript. The word “legacy” is just indicating that we have the Azure Function which can be an alternative for CloudScript. You can check this document PlayFab Roadmap - PlayFab | Microsoft Docs to see our plans.
Please don’t worry. If we were planning to deprecate the CloudScript feature, we will write a post in Microsoft Azure PlayFab Blog and will send the notifications to all the developers in advance.
UPDATE:
Announcing CloudScript using Azure Functions is now GA
This blog post has announced that the CloudScript classic has become a legacy feature. It will remain available for titles that are already using it. For the new titles, we recommend using CloudScript functions, as it makes developing and operating your game easier:
Please check out our overview video and quickstart guide for more detail.
This looks like a decision that has been implemented poorly. It is not uncommon for a team to operate multiple titles for different environments. For example, a team has one 'dev' and one 'prod' title (maybe more like 'test') to keep things seperate from each other and prevent issues. Great, but what about teams who were currently in the middle of building their product for launch and hadn't yet uploaded any Cloudscript classic to their prod title but had done so to dev? That prod title doesn't have an upload option anymore. Is that it? Go home? Tell the shareholders "oh well"? Come on guys surely there needs to be a grace period for this, especially for teams that had spent so long on development only to wake up one morning and find they are screwed. Telling people that you recommend to use Azure functions when it's forced upon them is not a good look.
@Timothy Mironenko & @Tobias Mueller For this scenario, please feel free to open a support ticket, we can enable Legacy Cloud Script for you if there is any reasonable business impact.
@Jay Zuo Please re-enable revisions for E0513 & 5F2DE. Our project is already started and is a clone/reskin of an existing title. We need to be able to do a straight copy-paste of our existing title's Cloudscript. Our project budget, timeline, and contracts are already set months ago. We didn't know you would take this feature away and now we can't renegotiate our development contract.
Agreeing with Timothy. We also have various playfab titles for internal testing, developers etc. and of course for production, with new ones (e.g. for new markets) potentially being added in the future.
Not being able to add a new title for an already established project and product is very concerning and is currently blocking us from moving forward with our project.
Hi, I am new to PlayFab (joined one month ago, free plan for now). You said "newly created titles no longer have access to the legacy Cloud Script service" but I have access to Legacy Cloud Script (Revisions) from Game Manager and I can execute hello world sample scripts. Am I missing something?
That statement is incorrect - we were considering deprecating legacy Cloud Script for new titles, but that has been put off for now. However, we strongly encourage new developers to use our Azure Functions Cloud Script integration, since it has many advantages:
playfab, as always, screwed up the developers who pay money.
Why has the cloud scripts function disappeared on all my projects that were created many months ago????
I demand to return them to their place, as the year of project development can go down the drain because of your unexpected actions! We have been developing our games for over a year using Cloud Script Revisions. But today, when it was time to bring the games to new platforms for which the projects was created several months ago, we found that the Cloud Scripts Revisions section had disappeared.
title ids: B3F66, 621AE, D5897, D1F7D, 6CCA6, 7B3F6
Its good to enable option for Legacy Cloud Script on Title creation, as everyone suggesting to enable it. Our Prod Title has not created yet due to project is still in dev stage of 80% completion and we are not sure how long will take to create and publish to Prob.
Also its not too easy for small teams to quickly grad the Azure functions in mid of their tightly scheduled dev progress.
@Jay Zuo kindly address the situtation for us, as client not decided to create a Playfab account or title until signoff and core functionalites of CloudScript has been developed and Tested and here there we go with New Title with no CloudScript. What to do with the upcoming title? Its like u guys at GUN point forcing us to move Azure Functions.
UGH! Within 2 months this went from "no such plan to retire the CloudScript" to yanked it out without warning. A blog post isn't the way to go when companies (studios) need to PLAN AHEAD. Our game in development was supposed to leverage pre-existing code from another game of ours, including the Cloudscript. The contracts are SIGNED. Dev is started. We can't just pivot to a new system when it wasn't even known to be necessary. We don't have the budget to add more people to the team now. Seriously! ... SMH
Renable it for: E0513 & 5F2DE
Because really, if we have to re-code our back end, we might as well explore other services than Playfab, no??
Hi @Jay Zuo @Rick Chen Could you please enable Revisions for the title 5A475 and 734A9 as well? Help! Thanks!
Hi Playfab team @Brendan @Rick Chen, please enable Legacy Cloudscript for title: 4EE33
Thanks in advance for further help.
Hi @Jay Zuo @Rick Chen , @Brendan . Will it be possible to enable Revisions for the following titles : 23720, 6E3C1, 93F61, 5DC44 ? They will all be the same game (a production version and 3 for prototypes that will be deleted afterward, we plan to reorganize a lots of things in it during testing with several user groups testing different versions of the game). We already made the code using Playfab Revision for the Title A2A07 . I'm the sole dev of the team and migrate to Playfab Azure Functions was not scheduled in our production plans.
Thanks by advance.
Tom
23 People are following this question.
