• Content count

  • Joined

  • Last visited

Community Reputation

2373 Excellent

About Avalander

  • Rank
  1. "Gameplay data" is kind of a broad concept, but if we're talking about unit/item properties that might change in the future, I would go for storing them in the game server. And I'll assume that when you talk about "the cloud" you are talking about some sort of game server and you know roughly the purpose and effort that goes into implementing these things. We're talking about a multiplayer game here, so you'll need to have the data available in the game servers for any calculation that affects multiple players anyway, unless you want to trust the client to do that calculation (hint: don't). You could, of course, have that data hardcoded in the game client also and use it in the local simulation, but, as you mentioned, it's nice to be able to change that data dynamically, so I don't really see any benefits in hardcoding that data in the client besides it being easier to implement.
  2. I beg to disagree. Distributed source control means that when you clone the repository, you get a copy of the whole repository, with its commit history and stuff, in your local machine. I suggest checking out the link below for differences between traditional and distributed source control systems. https://betterexplained.com/articles/intro-to-distributed-version-control-illustrated/
  3. First, a bit of introduction to work with source control. Details depend on the system you are using, but in a nutshell, there is a server with the master version of the code (as, for instance, github.com). Everybody who needs to work with the code, downloads a copy of the code from that server into their computer and work on that local copy in their computer. Once they are done working on a particular feature, they update the code in the server with their changes, and now the master version has their changes available to anybody that's going to work with that code in the future. The good thing about source control systems, is that they allow multiple people to work on the same codebase at the same time. When two people have been working on the same codebase at the same time, they didn't see one another's changes because they were working on their local copies. They will see one another's changes when they try to update the master version with their changes, and someone will have to merge both updates. One of them is going to be lucky and update the master version before anybody else, so the master version will be the same that they downloaded. No trouble. The next person that tries to update the master version with their changes, will find that the master version is no longer the same code they have been working on. Then, that person will have to download the changes and make sure their code works. If they are lucky, the previous person won't have touched the same code as them, the source control system will be smart enough to merge their changes and everything will work out. If not, they will have to go over their code and make sure that the recently updated master version works with their changes before updating again the master version. In my experience, you usually try to avoid working on the same part of the code. If I'm working on the same feature with another developer, we either sit together in front of the same computer and work together (that's usually known as pair programming, by the way) or work on different parts of the code. It happens, however, that you end up touching the same part of the code as somebody else that is working on a different feature. In those cases, if the person modifying the code sits close to you, you just sit together and review the parts of the code that you both have changed to make sure that both features work properly. Otherwise, the other person has hopefully written tests to make sure their feature works, so you fix any compilation issues, run the tests and fix anything that is not working. Debugging has nothing to do with source control. When you debug, you use the copy of the code in your computer, so you don't use or affect the master version of the code at all.
  4. I had the same problem signing in from Chrome on my laptop, it kept redirecting me to the login page again and again, even though I was authenticated because I could navigate manually to the home page.