MODDING with a single person working is a HUGE task -even if that single person happens to be proficient in coding, modeling, graphic design, audio manipulation, etc. It takes enormous amounts of time to pull it all together for a finished project.
It is no surprise why game companies spend millions utilizing large teams of people working for years just to produce one game.
So many MODS in modern games with huge popularity never make it to market, so to speak. Not knowing the numbers myself, I can only surmise that it is ever more so with an older game like Homeworld. This does not mean that people are not interested. Try to keep in mind other people’s perspectives. Some people just love to read about it. Some people would love to help but do not have the expertise. Others have the expertise but are already on their own adventures. Some help can be made when the scope is small enough but other efforts involve a scope so large that it is not feasible for them to jump in and help easily. It is a tough decision to want to help, but know it would take such an enormous amount of time to do so --time that one may not have to spare.
Of course, we all know this but sometimes it helps to think about it again… and again… and again.
Here are some words of wisdom I have been given over the years to apply to any project I am working on:
Work toward a deliverable.
This sounds easy enough, but if we look backwards at deliverables we have made in the past, most of us will see more unfinished projects than finished. When I think about this, it forces me to make some decisions. Like, should I go on; or is this project too much work for me? Do I need to scale back to get something delivered? I have a habit of fluidly wanting to add more and more (wife’s insertion here: “and more and more and more…”) on anything I work on. Other times it motivates me to push forward if I feel the effort is worthwhile to me. (That is to say it is something I enjoy doing.)
What is my driving factor?
And I ask this over and over throughout the life of a project. There can be many driving factors but one will always overshadow the others. And driving factors can change over time. For instance, am I doing a project because I enjoy the process? Am I doing a project just to learn some new process? Am I doing a project because I want to share this with the world? Or have I got to the point where I just want to have a deliverable so all the work done prior does not feel like a waste? These are just a few of the questions I have asked myself… and there are many MANY more! But understanding the driving factor helps me make a decision. Sometimes not asking this will propel me to just keep working on something in aggravation not knowing what my actual desire to do with it is.
Am I enjoying working on this?
Yes or No? If No… can I wrap the project up by producing a deliverable now or do I scrap it? In the end, for me, working on something should be fun. Yes, projects always present challenges, aggravation, and sometimes a broken lamp across the room. But I have to be objective and really answer, am I enjoying it?
If I get past those questions and still want to move ahead, I lay out the problem(s) I am facing. Sometimes this requires setting it all down and sitting in my large recliner with a pen and paper, and brainstorming the things that need to be done. Other times playing my MOD with pen and paper and writing down every single issue that needs to be worked on. It is also awesome to have my gaming wife (@gameg1rl) to brainstorm with. And then I just start tackling the issues I can resolve. In the end of either I should be able to produce a list of problems that need to be tackled and identify the scope of each. Identify the order of all of them. If you know SCRUM, this is my method. Having this list allows me to move forward one block at a time or decided to cut stuff out if I cannot get a block of work done.
Anyway this is my process.