|
Post by SirBuscheese the Third on Feb 24, 2018 3:30:03 GMT
So, this game is being created by some volunteers, meaning that they can't work on it 24/7, right? Well, more talented people could be drawn to the game if more knew. I'd suggest contact with some relatively big YouTubers and maybe a Steam Early Access release. This would give it a more stable launcher/update installer, and more people could see it. Of course, I've never made a game before, so I don't know if files would need to be reworked or if putting a game on Steam costs money or anything of the like, so take this post lightly.
|
|
|
Post by NickTheNick on Feb 24, 2018 7:23:14 GMT
It's a good point and one we've thought about quite a bit.
At the moment, since we are switching to a new engine, our hands are tied. If we got new developers on board they wouldn't be able to start developing until the switch was finished and would have nothing to do. The exception would be for minor tasks or modules of code that we know are going to stay the same in the new engine. So we're planning to wait until the engine switch is finished, and then do a big burst of outreach to attract more developers to the project (including using Steam and Youtube).
|
|
|
Post by SirBuscheese the Third on Feb 24, 2018 8:23:23 GMT
It's a good point and one we've thought about quite a bit. At the moment, since we are switching to a new engine, our hands are tied. If we got new developers on board they wouldn't be able to start developing until the switch was finished and would have nothing to do. The exception would be for minor tasks or modules of code that we know are going to stay the same in the new engine. So we're planning to wait until the engine switch is finished, and then do a big burst of outreach to attract more developers to the project (including using Steam and Youtube). Ah, gotcha. I forgot about the engine change and how big of a setback it is.
|
|
|
Post by QuantumCrab of '18 on Feb 24, 2018 12:24:57 GMT
It's a good point and one we've thought about quite a bit. At the moment, since we are switching to a new engine, our hands are tied. If we got new developers on board they wouldn't be able to start developing until the switch was finished and would have nothing to do. The exception would be for minor tasks or modules of code that we know are going to stay the same in the new engine. So we're planning to wait until the engine switch is finished, and then do a big burst of outreach to attract more developers to the project (including using Steam and Youtube). Might I ask, what is the new engine you are switching to?
|
|
|
Post by BiologicalSomething on Feb 24, 2018 12:48:44 GMT
It's a good point and one we've thought about quite a bit. At the moment, since we are switching to a new engine, our hands are tied. If we got new developers on board they wouldn't be able to start developing until the switch was finished and would have nothing to do. The exception would be for minor tasks or modules of code that we know are going to stay the same in the new engine. So we're planning to wait until the engine switch is finished, and then do a big burst of outreach to attract more developers to the project (including using Steam and Youtube). Might I ask, what is the new engine you are switching to? "Leviathan", I believe. I think it's hhryyaoixmozixnsx's. I can't remember their name ok
|
|
Darwin
Multicellular
Posts: 20
|
Post by Darwin on Mar 2, 2018 21:48:53 GMT
Might I ask, what is the new engine you are switching to? "Leviathan", I believe. I think it's hhryyaoixmozixnsx's. I can't remember their name okhhyrylainen's Leviathan. leviathanengine.com/
|
|