-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Creeper, platform etc. support? #95
Comments
Roads and constructing zones are mainly decals, a textured quad that follow the relief. It's a tricky thing to implement and it is not in the code road map for now. The sc2's creep is a particular thing, since it produces a covering texture, plus some decals or else at the limits. Very tricky ☺ For things like mask, like for energy of the protoss' pylones, we just have to add a cover above the existing one. |
After checking, its seems that Dune put ground assets to get constructible plateforms, which disable any ground relief. It will be possible to do the same with the future ground trinkets, because they certainely won't support any ground deformation anyway. |
Sound cool. Dune actually had two systems (and so does the model set we could get into OpenRTS), one layer of elevated rock on top of the sand and on top of that one could build platforms as foundations for buildings. I think something not too unlike the Zerk creeper could also be implemented as models/trinkets on top of the existing terrain? |
Would it be possible to add support for stuff like the Zerk creeper that covers landarea with a different type of texture/mesh cover??
Dune also used a sort of platform system to mark the parts you can build on.
Energy zones like done for the Protos in Starcraft are also kind of related.
I think the simplest would be a change in ground texture and the option to automatically place random trinkets specific to that ground texture. Maybe interesting could be also various types of non-random placement of these, for example outer perimeter only, or grid based etc.
The text was updated successfully, but these errors were encountered: