Software Requirements

On this page is a list of required software for the team. Some are necessary while some are optional. We are open to suggestions at all times for any suggestions for improvement. Given the remote nature of our work, it is typically desirable to use the same software for the whole team as it makes troubleshooting significantly easier.

This Wiki page is where we document our work. It is useful to merge important documentation into one easy to find place. Organisation is key, and we try to have all design and art documentations together as it is likely any questions have already been answered at some point in the past. Please read the entire workflow section carefully after you are part of the team and have access to all the articles. Interviewees are not expected to read beyond this introductory page and the interview tasks themselves.

Here is a list of important software that are must-haves for all team members.

Discord is the application of choice for text and voice communication between the team. It is also very useful for screen sharing. In essence, it is very similar to Slack/Skype but with many improvements.

All members are expected to be active on Discord. Install it on your phone, and treat it as a text message that needs replying to if you are tagged. Slow mode is used for channels that should not be spammed with anything except import information.

Currently, we use this Wiki and pCloud to share documentation. This includes excel sheets and word documentation. pCloud rules are fairly elaborate, and are very strict regarding its usability, especially for artists. Please read the art documentation for more information. As a general rule, please refrain from using other file sharing methods as these files are easily lost and most services do not offer complete and regular backups of our files. Data loss is a major issue and we should take as many steps as possible to prevent this from happening.

After much research, we find that pCloud, allows a powerful rewind feature that gives us insurance in case files are deleted or lost. We have tested some 20+ different cloud storage solutions such as Mediafire, iDrive, Google Suite, Microsoft Teams, Dropbox and many more. Very often they either do not offer complete version control, team permissions or unstable uploads.

In your own pCloud, please do not store personal files on there. If you plan to store personal files, please use a different storage solution. Also, please always sign up under 'European' in the pCloud region as we cannot share files if you are registered in another region.

Team members are expected to work a specified amount of hours as agreed upon. The minimum Time Doctor productivity that is expected over a period of each week is around 90%. This takes into account meeting hours (which are usually lower) which are averaged out over the period of each week. Generally, meeting 90% each week should be fairly easy under normal working conditions.

Please do not track time when you are not working. Time Doctor tracks apps and URLs while open, and is regularly for productivity measurements. In addition, it takes periodic screenshots while active.

General Advice:

  • It’s okay to listen to music while working.
  • Please do not watch Youtube or other videos while working unless it’s strictly work-related.
  • Try to avoid using personal messaging software such as Whatsapp or Facebook messages during work.

Team members are expected to work their hours on weekdays (Monday-Friday). Missed hours should be filled during weekends, but only when absolutely necessary. Ideally, weekend hours should not exceed 2-4 hours per week.

It is strongly advised to spread out the working hours across the week, as this means higher availability uptime as compared to compressing excessive hours into specific days of the week. We believe sustained consistency is the key to high productivity.

Trello is the project management software of choice. Members must check Trello regularly to see updates and new tasks which have been assigned. All members are required to add a profile picture to their account, and also use their real names on Trello.

If you are currently working on a task, please add yourself to it. This is very important, so people are aware of who is working on what at any given time. In addition, please write a brief description of what is actually done in the card when it is complete. Try to avoid moving Trello cards to complete with no description of what was actually done. This causes problems down the line later.

Try to prioritise tasks that are tagged as ‘high priority’ in red, rather than other tasks with no tags. While we do give freedom on what bugs are to be tackled, please do not put off difficult tasks forever as they will stay at the bottom of the stack for quite some time otherwise.

Most developers joining the team will already be familiar with Unity. We are currently using Unity Collaboration to manage game versions and not Git. There is not much more to be said here, except do not push unless you are sure it will not break the rest of the game. A few points to note at the time of writing.

Our current file and data structure could be significantly better. This is also true for a lot of the code that has been written. It is not a major concern for the time being, but we will work on improving this significantly down the line. In addition, playing the game inside Unity and outside seems to be a little different and generates different bugs. The bugs that appear are apparently a little different between the two. Keep this in mind.

When compiling the game, please use the right compiling method, one of the LZ4 methods. If you don’t, the game will be over 5GB in size. This gives a faster compile speed but is obviously not a desirable outcome. For art imports, please make sure you talk to other developers so you understand how the importing should be done.

  • software.txt
  • Last modified: 00:27 24/08/2021
  • by Terry Jin