Evaluation

The long term goal of the game was simple which is to survive and get the highest score which the final game lacked as the end screen did not show your high score. However the challenge was still in the game, the trains enters after a certain amount of time so the player was able to learning the pattern after a few amount of play through and the challenge ramps as more trains enter the screen and you have to avoid more than 1 train whilst collecting packages to bring back to the station to gain a score which is the immediate goal.

Although when you click the arrows it shows visual cues on the screen to indicate which way the train will go, the arrows can confuse you as you think the train will go the way the arrows point but it doesn’t, the contradiction can and will confuse some players.

The game still has the tactics and strategic play to the game such as learning the pattern, going to the centre of the level to collect packages whilst changing the arrow direction to make the enemy trains to go around the outside. However even though you keep making the trains constantly going around the outside whilst you are in the middle collecting points, it will be hard to get to the outside lane and go to the station so you have to think about what to do. The trains all move in the same path so they have the same pattern but because you can change the arrow direction of the enemy trains it can mix up the pattern a little bit and because the enemies don’t come on the level so quickly it won’t feel like they are following the same pattern but after playing for a while you will recognise all the enemy trains are going in the same pattern and makes the game start to feel boring.

Deadline

The final day to get our game finished, we had extra features programmed in separate flash files and we thought it would have been as easy as a copy and paste task but sadly that proved to be wrong as new problems came about and because it was so time consuming to copy and paste codes from a separate file to many objects in the final version of the game, it was close to deadline that we found these problems so we had to revert back to what we already had.

 

This left us with not implement a nice visual starting screen and game over screen with a high score because we kept pushing this task to end as we thought we could do it in a matter of 10 minutes so we just tried to implement the new features which we shouldn't have done since we have experienced many problems when adding new elements to the game so we should have known that it couldn't be done in 1 day. Instead we should have tried to refine what we already have since we still have the core mechanics of the game. The elements we could have refined was the train moving along the tracks properly so it looks visually better, changing the visual lights of packages to have the last circle large, showing you have reached the limit, made a starting screen with an option for players to read instructions,  change the arrows to leavers to players don't get confused with where the arrows is pointing as it doesn't indicate which way the train will be going unless you click on the arrows which gives a visual cue on the screen which way the train will go. 

 

Finally the upgrade train feature was not implemented because just getting the trains around the course was a lot of trouble to get working and to do the same job with a new train would be overwhelming as there are many codes in the game exactly the same except the name of objects so when a problem occurs, it will be hard to pinpoint the problem. This was also an extra feature to visually please the player and increase the challenge so we put this feature at the back of the list to do which kept getting pushed back like the title screen, game over and high score as we tried to solve problems we had before.

 

Although we worked well as a team, the problem we had was not having a team leader which would make the crucial decisions whether we should implement the features we tried to do on the last day as we were blinded by trying to add as much features from our design document into our game instead of refining our game which doesn't feel like a polished game. The last day should have only been adding graphics to our game or replacing graphics we already had.

Downfall - Mass of Problems

Trying to get the arrows have 3 frames for the 3 way corners instead of only 2 frames was more time consuming then expected and eventually we got working and wanted to derail/crash trains at bad junction which we were able to do on 1 corner but this really showed to be harder than expected on other corners since it was checking variables from objects on each side of the object which turned the train so we decided to remove that feature because we already had a lot of variables and codes going on because we couldn't use arrays or didn't know how to use it in our case since the arrows changed the trains direction and if you only changed on train and it touched a directional object which tells whether they are moving forward or backwards, the array will tell every train it is moving backwards so we did separate codes for each train and this became overwhelming.

The bridge code was also removed and we left it so that it became a normal track path because although we had the bridge working the codes would affect the entire game because it changes the depth of each objects so when a train crashes or it goes game over, the object will not work so we had to write a code to make the object depth go back to it's original depth but even though we done that, it still sometimes didn't work which we did not understand so we thought instead of having a feature which causes problems further on in the game we should just remove it for now.

Once we decided what wasn't going to be in the game because we knew we were going to need more time, we decided to add things which would help players understand such as circle lights at the bottom beside the score to indicate you have picked up a package, we also added scores to the game.

Testing

Today we had a beta testing of our game with outside people from the group and problems aroused which we took into account to try and fix such as people not understanding the what the arrows do because they can't see which direction the train will be going. Another problem was that the trains went out too fast so a timer was suggested, that way the players can digest everything that is going on before being rushed with legions of trains. We were also told to fix the hit detection between trains since they would crash from opposite side of track which would have been game over for the player if your train crashes into an enemy train. However we did not have a game over screen so players didn't understand the actual point of trying to avoid trains since the players train would just keep driving through everything so one of the first changes was to add a game over screen when the train collided with the enemy train.

Train Movement - Chosen Method

after getting it to rotate around 2 corners we found problems with the lines that the train moved along since it was telling the train to move along but because it was too close to the corner the corner will also tell it to rotate so in the end the train ended up spinning in one spot so we decided to change the codes and remove the lines it moved along.

We done so by making the train moving in a constant direction and when it touches the box it will make the train play few a series of frame and once it has reached the end of it, it will stay in that direction and move along the y axis or x axis depending which way it is coming from, before we had all the codes in all the train which would get confusing which is the reason why we broke down the programming into several objects the train will collide to do a new task.

http://megaswf.com/view/59695106459cdf678c7a632e39be4253.html

Train Movement

We finally have a finalised design document after reviewing and play testing our paper prototype so we are now starting to program our game by sorting out the parts which we feel will be the hardest part of programming which is the corners the train turns on the track.

We thought of 2 ways of doing so, the first idea was to have the train hitting changing frames which constant went forward and something pushing it down which can be seen on the swf file located on link below.

http://megaswf.com/view/07f9f105fee8f5e493d3ca35045f303c.html

The second way is the way we decided to use. The second way is to have the train touch an object and it rotating and then it moved along the line which can be seen below.

http://megaswf.com/view/b8121ea3c2dc6b12e2c75cea85bb038b.html

Paper Prototype

We played our paper prototype of our train game and found out that more features should be drop such as being able to reverse because this feature made the game way too easy. After removing features of our game we wanted something to also ramp the difficulty so we decided to have carriages.

The group recapped the idea the next day to see if everyone remembers what changes has been done and to clarify what we want in the game. After some thoughts, we stumbled upon some problems which we needed to solve such as if the player is too good for the game or really bad so we thought of the idea of the train slowing down after a certain amount of packages was collected, ideally 5 packages was the amount to slow down your train which indicates to go back to the station and drop of the packages.