Martin L suggested an idea · Jan 19, 2018 at 05:59 PM · CloudScript
I have been using CloudScript for almost 2 years now. I developed a way to unit test my code using Node.js as a proxy for the server and I can debug that with Iron Node, which has saved a lot of time. But bugs still slip through and I have to go back to old school trial and error logging, which is laborious. I would like to be able to debug my CloudScript in place on the server.
There are requests for C# CloudScript, since people like to use languages they know, and many people likely develop in Unity, but with no debugger CloudScript development will remain slow even in their preferred language.
Joshua Strunk commented · Jan 19, 2018 at 08:16 PM
What kind of bugs can you not debug with your currents set up? What is slipping through? I am curious as it sounds like you should be able to debug almost everything with that setup, and I am not sure what Playfab could reasonably implement with more features over your current setup.
The kind of bugs that I still see come from a few reasons:
(I am now writing a set of integration tests to lessen some of these but I can't eliminate them)
We would love to know what you need. Submit your ideas and upvote others to help us prioritize.
No one has followed this yet.
API methods/CloudScript functions to interact with multiple Shared Groups at once
Playfab party multiplayer supports MacOS
Dash: Save JSON recipes for args
Add VC Recharge Rate to client and server APIs
Cloud Script environment variables and Admin API to update them
Validate Receipt on Cloudscript
Return the Function Result as a string in ExecuteCloudScriptResult.