Judge feedback

Judge feedback is anonymous and shown in a random order.

• A good start to a nice point and click action game. Would benefit from more time. Make sure to test for null in methods like game::SpawnEnemy() to make sure all required components are attached to gameobjects. in game::Update(), consider putting this logic inside a separate method rather than directly inside the update loop, it will make future extensions easier Also, consider moving the embedded numerical literals to variables that are serialized in the inspector, so that you can tweak the spawn rates in the editor for difficulty. good use of #defines in the exit method for editor specific code branching environment randomized generation is good, consider does environment tile need to be a monobehavior? there may be some cleanup issues when you destroy. Keep at it, nice progress 8) Cant' wait to see the final game
• I just wanted to give some general feedback: 1. Most of the time, the first thing that people will see is your Main Menu. So it can help to spend a bit of time and polish on that to start on the right impression. 2. Think about adding Instructions or How to Play to the Main Menu or a pause screen. 3. Think about adding a fast forward or game speed toggle. It would help when people have a good setup for their cannons. 4. When you're using random world generation for your resources, you need to be careful. Try to keep it balanced, otherwise you could end up with a lot of one resource and not enough of another. It would make it harder/unfair if you were trying to go for a leaderboard score. 5. Think about adding some basic sounds to the game, you'd be surprised how much they can add. Also, next time try to plan the basics of what you want, and create a polished slice of your game, which can then be built upon. It can be better to have something small that works really well, as opposed to trying to do a lot, but never really hitting the mark. This was a good start though, and something you should be proud of!
• I can't review this submission - there's no documentation or binary, just the Unity project.
• Ideally, build your project rather than submitting the entire project folder. It takes less time to export and it's guarenteed the same for you as for anyone else. Projects can be opened in different versions of Unity and will run differently while a built version will stay the same. It also protects you from people just taking your work for themselves in future. There is no built in tutorial nor any files provided to explain what has been done, how to control the game or what is actually happening. I've pressed every button on the keyboard and the only thing I could do was shuffle the randomly generated environment. I can see the UFOs but I don't know where the cannons are. Good job getting the UI to update when the UFOs reach the other side of the map and it looks like they're in an object pool which is good practice but a bigger concern is that I don't know how to play.
• Unfortunately it showed that this was really rushed. Overall the game was very buggy and difficult to get started with because I had no clue what my goal was or even how I lose. No documentation was supplied, so it's difficult to know what has been changed from the base project, but it doesn't look like a lot was done. I don't think it was a bad effort, but with only 3 days to make a game, they should have prioritised their time better.