| As a Roblox programmer (Builder’s Club) scripting a game, the draw of addressing this huge user base by way of simply coding Lua scripts to release a product that invites In App Purchase is downright tempting! Then you discover the apparently wide spread client side hacking (speed, teleport, aim bots... you name it) and content theft (models, geometry, Localscripts) and pervasive scam attempts so frequently reported. But that’s the internet, and the cost of doing business, right? After some success (proof of concept stage) building an unreleased game, I started to notice pitfalls and inconsistencies in the developer docs, including lack of documentation for methods and properties specifically out as recommended or best practice approaches. Chunks of the docs would suddenly disappear for days or weeks with no notice and no explanation and may or may not reappear after some time. Didn’t see any change logs that I could find. And then one day this summer I could not access the developer docs site at all, from any of my devices on different ISP connections. After proding around, I realized this was only occurring on Safari (Mac and iOS). Too many redirects (for Tracking)! Apparently Safari had gained additional privacy checking after an update. Got me thinking, if it’s the case that Apple effectively doesn’t trust the techniques used by Roblox to add tracking to their developer documentation site, is this effort something I want to continue pursuing? Which segues to the question: Given the active user base and gross cash flow of Roblox, how do you now frame the new ARKit, RealityKit, Composer, and SwiftUI announcements from WWDC? |