I requested read-only access for another game recently; and I can check out the running game in Studio, but when accessing the game page in Control Panel I get a
Code: Select all
Access restricted (You only have read only privileges for this game)
. So I haven't been able to look at the code yet.
As soon as you request readonly access, the code is available to read in your SFTP folder
I don't see any need to go to the game page in the control panel (since actions listed there are not applicable for read-only access) but I suppose I could give access to this page in readonly mode too if it's disturbing not to see it.
Advantages of Git* over BGA:
- Public code
- Low barrier of entry. Nobody to ask first. Especially useful if I only want to look at the code/learn without interacting with the author(s).
- Viewing, even editing, code in the browser.
- Much better collaboration possibilities: pull-requests, bug/ticket management, code review, code comments etc.
Thanks for listing this! Here are my thoughts about each point.
- "Public code": well, I don't know what you mean exactly by 'public' but with readonly-access any developer on BGA studio can get access to the code of a project by default, and there is no restriction on the creation of studio accounts (which is a logical first step if you are interested in creating games for BGA), so I'd say that "public code" is already the case.
- "Low barrier of entry. Nobody to ask first. Especially useful if I only want to look at the code/learn without interacting with the author(s)": same thing on BGA studio, unless the developer changed the default (only a handful of games) you don't need to ask to get readonly-access, or to create a copy of a project that you can fiddle with.
- "Viewing, even editing, code in the browser": yes, that would be nice. Lots of developer prefer to use their choice IDE, but still, it would be nice, even for us admins when we need to make a quick fix to a studio project. I'd like to add this when time allows and if I find a good open source in-browser editor.
- "Much better collaboration possibilities: pull-requests, bug/ticket management, code review, code comments etc": quite true, but most studio game projects are actually one-man projects and BGA already has its own bug/ticket management system once the game is released. Still, for projects with multiple developers wanting this, it's a good solution as it would clearly be a lot of work to add all this to BGA studio (even if an online editing tool could maybe come with simultaneous editing, that would be pretty cool).