This Post Took 3 Years to Write
31–40 of 65 posts
Re: This Post Took 3 Years to Write
#32Re: This Post Took 3 Years to Write
#33Not sure if anyone here had the pleasure of playing "Glitch", but the copy done by Chris Shorrock is wonderfully crafted and reminiscent of the game.
Re: This Post Took 3 Years to Write
#34Re: This Post Took 3 Years to Write
#35Great game! Do you have short overview of what you used for making this game (frameworks, database, hardware, etc.)?
We're currently running an all javascript (coffeescript) stack. In the backend we have a variety of node.js servers. We have the following "types" of servers:
- Metagame: handles our web api requests - Game: handles all the game logic, on the server. no client side game logic. Because we're all JS - client is effectively open-source. - Notification: routes messages and notifications to the users, utilizes 0mq between servers. - Matchmaker: takes in requests for game searches, keeps requests in memory, and finds matches. - Overseer: orchestrates where all the servers live. Want to know the address of a server? talk to the overseerer. Need to spin up a new game server? Overseerer. - League: Handles league management.
We currently have physical 6 servers (2 metagame, 2 game, 2 for the others). The metagame mixes web-sockets and standard web requests. The game server is web-socket only. These are the only two servers that talk to the clients. All other servers just network between themselves.
The Metagame, and Game server are fronted by nginx which acts as a reverse proxy, does ssl termination, caching policies, etc. All our assets (images, etc) are stored on Amazon Cloudfront, and cached forever. All filenames encode the MD5 signature of the file to ensure that we can cache everything forever, speeding up the clients.
We're currently using MongoDB to store all our game data. We use http://www.objectrocket.com/.
We were also accepted into the Rackspace (http://www.rackspace.com/) startup program which provides us a lot of free servers for a year. While we don't need all 6 servers right now, we can test out the infrastructure and launch this way, allowing us scale up easier. Free for a year was a good reason to move away from AWS - where we previously resided.
We went with nodejs - largely because of the "fun" factor. When we started we didn't have a ton of familiarity with it, but we wanted something different, and node had a lot of buzz at that time. While writing it in C, Java, or Erlang would of been more in our wheelhouse, we knew this was a hobby project and wanted to learn something new and enjoy ourself. It turned out to be a good choice, node is great. It performs well, and is a joy to work with. I've always felt that server side performance just needs to be good enough, you can optimize and optimize and optimize, but at the end of the day your stack needs to be architected such that it can run on 100s of computers at a time. You can only run with 1 server for so long, so creating something is scalable in hardware is more important then squeezing a single server for all it's worth. Node, combined my 0mq (for us) makes this a snap. My 2 cents anyhow.
Mongo was chosen for a similar reason. It has nice aspects to it, and is a great compliment to an all JS system. For us, we're not query heavy so it was a good choice. That said, as we add features, I can see partitioning our data into mongo data and more traditional RDBMS data. Mongo is good for certain classes of data, but you need to know what you're getting into. If you'd like me to talk to anything else, let me know.
Re: This Post Took 3 Years to Write
#36"Like who you work with: In life, and in business, surrounding yourself with people you enjoy makes difficult times easy." A very underrated statement. This really matters. No matter what you do in life, it always comes down to the people you do it with. E.g. People don't leave a company, they leave their boss. People don't leave a marriage, they leave their spouse etc etc.
I don't agree. I prefer to work and be alone.
Re: This Post Took 3 Years to Write
#37Well, that felt intuitive. I didn't want to click on a card then click the (i) to view a detailed description. So I held ctrl and clicked it. It worked! I'm going through the challenges right now. So far I'm really enjoying this. Nice work!
Re: This Post Took 3 Years to Write
#38* If you link to the site, you can only say nice things
* You can't opt out of their emails
* They say, "please refer to our privacy policy" but there isn't one (this might be an oversight or maybe I just missed it)
[edit for formatting]
Re: This Post Took 3 Years to Write
#39Good work! I tried out the tutorial and thought it was pretty good, but wanted more before signing up. I'd recommend putting in another larger battle where the tutorial ends, so I can get a feel for how the game plays.
I felt the same way. And then I signed up with a bogus account, and it wanted an e-mail verification.... Why make me e-mail verify?
If more websites would verify, then this wouldn't be a problem.
Re: This Post Took 3 Years to Write
#40In Tutorial, when being instructed to place the 8th-grader, it's not clear that it should be placed on a specific tile out of 6 (?) highlighted. Took me some clicking around to notice that small green arrow against greenish tile and realize that. Later on, same hiccup with "Now press forward". Green smallish arrow against cyan background next to green header pointing at green field... you see where I'm going. -- All…