Terasology is an open source project started by Benjamin "begla" Glatzel to research procedural terrain generation and efficient rendering techniques in Java using the LWJGL. The engine uses a block-based voxel-like approach as seen in Minecraft. After proving itself as a solid tech demo begla was joined at first by Anton "small-jeeper" Kireev and Rasmus "Cervator" Praestholm and a full-fledged game concept was born. Our goal is a game that pays ample tribute to Minecraft in initial look and origin, but stakes out its own niche by adopting the NPC-helper and caretaker feel from such games as Dwarf Fortress and Dungeon Keeper, while striving for added depth and sophistication in the foundation systems akin to DF.
While trying to make the setup match the launcher (where the Gradle plugin works within IntelliJ) I ran into an issue where even set up correctly the Gradle plugin fails to parse the engine project - most likely due to the squirrely dynamic includes of sub projects or something like that.
Within IntelliJ the JetGradle window just never refreshes all available tasks and you can provoke an error by trying to refresh the project
Found the fix in the subprojects.gradle file - can actually use the IntelliJ Gradle plugin now. Sadly all our customizations need to be redone in the new preferred IntelliJ project format to go with that approach, so it might still be a while before we bother doing so -_-
Cervator
commented
10 years ago
While trying to make the setup match the launcher (where the Gradle plugin works within IntelliJ) I ran into an issue where even set up correctly the Gradle plugin fails to parse the engine project - most likely due to the squirrely dynamic includes of sub projects or something like that.
Within IntelliJ the JetGradle window just never refreshes all available tasks and you can provoke an error by trying to refresh the project
Not particularly high priority but would be nice