Jump to content
  • Advertisement

Ben Walker

Member
  • Content count

    2
  • Joined

  • Last visited

Community Reputation

2 Neutral

About Ben Walker

  • Rank
    Newbie

Personal Information

  • Interests
    Design
    Programming
  1. Ben Walker

    Post Mortem: CountOut

    Post mortem: CountOut https://walkies3.itch.io/count-out- CountOut is a game based on requirements of a game jam, we were each given Atari’s “Breakout” as a base and then assigned an individual artist, my artist was Sally Sheinman an American installation artist. However, we did have creative limitations, these included; · Must closely resemble the layout of the original game. · Must closely resemble the mechanics present in the original game. · Must closely emulate the behaviour of player and nonplayer characters/entities. · Must resemble and embody the style and tone of the assigned artist. This project was a solo endeavor by me, I am a student of SAE Quantm based in Brisbane, Australia. With experience in game development and majoring in programming I wanted to create a game that would both showcase the installation style and also provide the same sense of easy fun that Sally intended with her art work. Most of all I wanted the game to stop becoming a game at some point and more a kinetic piece of art. What went right 1. Planning and scheduling As this was a solo effort, planning and scheduling was achieved easily. I knew how much time I had and when I was available, not having to be concerned about whether work would be completed by others on time. Each week I used a scrum method, making a list of priorities that needed completing through HacknPlan and attacking one at a time in order. Through this method I was able to keep a track of the work that was done and what needed doing and thus how much time I would need to allocate to it. 2. Design & Style From the beginning I had a very clear idea of the style and theme of CountOut should be, whether it was intended or not Sally’s work often imitates playable spaces. This made it very easy for me to envision a playable environment from one of Sally’s work in particular “Artkacina”. Looking very similar to a layout for a table top game with blocks to hit in the center. Her creations of many shapes and textures was easily reproducible in a game sense too 3. Feature finding As the game developed, issues arose with the core design and while this isn’t a positive thing the ingenuity in fixing these problems within a time period were. It also shed light on to new and interesting game mechanics that would eventually be reworked from bugs into features. Alternative solutions to these bugs were theorized and tested to make sure the new feature functionality was correct, overall these were still achieved in a reasonable time frame and didn’t affect the scheduling. The way I worked This was an interesting task, being a university student, time was restricted on the project. However due to effective planning and scheduling through HacknPlan, time was efficiently used as mentioned previously a scrum method was applied, by keeping track of tasks that needed to be completed within that week and updated frequently. There was never a point where I wasn’t sure what to do next. Also, any problems that arose were swiftly sorted and if the problem was outside of my expertise I looked externally for answers. What went wrong 1. Not planning ahead While I had an idea of what I wanted and needed in the game through the given individual specifications, the first couple of weeks of development my ideas changed, which in turn means there was less time planning the overall design of the game. Which lead to problems later in the project which included; core mechanics being changed, interactions being changed and more. Ultimately these were worked around or solved but if a clearer design was decided earlier than much time and frustration could have been avoided. 2. Self-Management This is something I feel is often overlooked, especially in our industry. Even though my schedule and time management were well planned, my well being was put second. Often working many extra hours to achieve goals. Even though I enjoy this development process at the end of the day its still work. Making sure that you have sufficient breaks and time to clear your mind is just as important to the projects health as yours. What to do in the future 1. Not planning ahead This is something that I’m normally guilty of, starting development before final decisions are made. While it could be avoided by changing my work method from a scrum to a waterfall. The most obvious solution is improved documentation, by effectively sorting these out before the project is started, issues are addressed and understood in the pre-production process. 2. Self-Management Now these are going to sound a bit ridiculous, but you would be surprised how often this is overlooked; · Take a half hour break every three hours, have a stretch, get a snack · Make time in your day for “play” · Stay hydrated · Get at least thirty minutes of exercise a day, even if it’s just a walk Looking after yourself is not only crucial to you and those around you but the life of the project as well. Time to reflect and recoup can help bring clarity to project which ultimately can save time and stress. Conclusion Overall, I’m really happy with how CountOut turned out, I learnt new programs and achieved things that were previously unobtainable. However, there is always lessons to learn and take away from experiences, this project being no different. In future projects I will keep in mind to create more detailed documentation and not to start a project before final considerations. Finally, to not take for granted health and self-management as the management of these affects the productive output of both the person and project. Find the game at: https://walkies3.itch.io/count-out- Development stats · Developer: Ben Walker · Length of development: 4 weeks · Number of developers: 1 · Development tools: Unity, Blender, Audacity, Photoshop, Visual studio · Sleepless nights: 2
  2. Ben Walker

    Postmortem

    Post mortem: Infinity game’s It’s a blob It’s a blob is a top down puzzle platformer with a cute pixel art style to the game. Currently only available on itchio. In the game you play as the character Blob (very creative I know), Blob is part of a solitary alien race; their influence is spread over many galaxies however they are destined to spend their lives alone. But Blob is different, he doesn’t want to be alone, so it’s his goal to reunite his people. Blob spends many of centuries (blobs live for a real long time) searching for some old alien technology that linked all his kind together. Pretty much the equivalent of Blob interdimensional Facebook and that’s where the players story begins. Blob actually found it! And now it is his mission to seek out and reunite his blobs once again. We’re a very early indie games studio made up of students from SAE Quantm based in Brisbane, Australia. With varying backgrounds that make a well-rounded team. Our team wanted to create a game that would be filled with the same fun and experiences as other games had been in our childhoods. Overall, we weren’t looking for any financial gain from this project but instead knowledge and experience that we could take to future projects. What went right 1. Ideas stage Through brainstorming sessions and generally just bouncing ideas off each other we were able to come up with a concept fairly quickly for the project. Being able to get this information in a visual form and voting on what ideas we would use was an integral part of our process. 2. Scope As this project had a deadline of 12 weeks, it was very important that we didn’t over shoot with what we were capable of producing in that time period. In fact, we under shot this quite a bit. While all the mechanics were in place, the amount of levels we had to explore those were so few we had to expand them by double. This wasn’t an issue though as we had plenty of time to alter and improve on the project. 3. Style From the beginning we had a clear direction for the art style, wanting a fun and classic looking game, in the form of pixel art. Which was both easy to produce and visually pleasing to consume. The style remained mostly the same through out the project getting a visual tweak in the polishing stages, this was done for both visual clarity and especially if animations were involved. 4. Testing The game was play tested thoroughly as new mechanics were added to the game and in the final stages, which picked up on majority of our bugs and problems. We also conducted a closed group alpha testing which provide to be invaluable for our game, by recording their feedback and gameplay we were able to analyze why the game wasn’t being played as we intended. Apart from a few in game bugs we hadn’t picked on, the main issue was giving the player to much freedom in tutorials and as a result they were not doing them or completing them in the wrong linear order which hindered their overall experience within the game. The way we worked This was an interesting task, being university students, we did have time in class to do some work but most of our time was apart. We assigned a project manager to the group who split tasks and generally kept a track of the work needing to be done. Although a scrum method was applied, it was a loose method. Mostly just addressing issue that arose and applying things in order as we needed it (art assets being left until later). Meetings were held every Monday afternoon on our own discord channel for several hours, as previous work was verified, and new work was assigned from that point. Further contact was kept through a Facebook page, so we could upload and share content on a more frequent basis. What went wrong 1. Puzzle refinement As mentioned in the testing section, level designs concepts that we thought were obvious as developers were not obvious to players, resulting in a poor player experience in our initial alpha testing. By changing the layout of the (portal room) and altering the intended path of the player (forcing them to complete levels in a certain order) we were able to fix this. However, it required more time and effort than was necessary than if we considered this at an early stage. 2. Not planning ahead This was a big one, while we had an idea what we wanted and incorporated that into the game this changed throughout the project, with new ideas being tested and trialed on the fly. Sometimes working and sometimes causing more issues. These included: · Changing camera perspective through game development (many hours changing and recoding) · Changing level design · Recoding the interactions between player and objects · Change of assets · UI However, the results of this undeniably improved our game, but by planning ahead and coming up with a conclusive design, we could have mitigated these risks and saved ourselves a lot of time. 3. Management This was something that was a bit all over the place, initially task were delegated as they were needed to the people appropriate... great, however as the project went on and the focus was more on coding, tasks were being split unnecessarily for the sake of feeling included in that point in time. This resulted in a mess of trying to collaborate work, double ups of some work and sometimes things just not being done at all. In the end it reverted to the old method of only being given to the appropriate people. Some delegated tasks were not being completed as well, forcing others to pick up slack to make sure the project was on time. Conclusion Overall this was a great experience for us as early developers, even though it had its ups and downs. It gave us an insight into many of the aspects of both team work and the development of a game. We learned a lot through out the process too and im sure we will all be taking these lessons on to future projects. It’s a blob was never meant to be anything more than an educational project but to me it become so much more than that. I’m proud of it Development stats · Developer: Infinity Games · Release date: Dec 2017, PC & Mac · Link to game: https://lazareth13.itch.io/its-a-blob · Length of development: 12 weeks · Number of developers: 5, (4 at a later point) · Development tools: Unity, photoshop, visual studio, monodevelop, · Budget: N/A · Sleepless nights: 2
  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

Participate in the game development conversation and more when you create an account on GameDev.net!

Sign me up!