From Thrive Developer Wiki
Revision as of 11:01, 10 January 2021 by Hhyyrylainen (talk | contribs) (→‎Random discord comments)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Random discord comments

Here are some comments I've said on discord for future reference

I haven't read up on this a ton, but I think that making generic algorithms run faster on a GPU requires a lot of redesign in order to make them more parallelizable, meaning that we might have to design the entire simulation differently to run on a GPU. There's also the fact that while rendering the game at the same time as running a simulation on the GPU may need some careful coding to not use too much GPU power for the simulation in order to not drop the FPS a ton. One more bonus fact: it seems a ton of people are trying to run Thrive on really weak GPUs (intel integrated graphics), which makes it even harder to maintain a playable FPS while putting extra load on the GPU.

It seems that Godot doesn't have Linux arm export templates We can make Linux arm releases once those are added Assuming there isn't a request for this yet, you should go and ask the godot developers to add support for Linux on arm to the engine officially Though it seems that if we had a arm64 server to compile godot ourselves we could do it: but I'd need to do a bunch of stuff to setup such a thing. With official export templates it would take me just a couple of minutes to do it

I don't think DLC is really going to work. I want to explore ways to fund the game, so things like having the game cost money on steam for the convenience of getting it from there, is something I want to try. In the same spirit I suppose official "mods" could be distributed through the steam workshop for example, basically making pseudo DLC much easier to get through steam.

Usually modding a game is not covered by the game's EULA or anything, so it is a legal gray area. However, as thrive is GPL all code that is linked to the same program (to make one program), would mean that technically every mod to thrive must also be GPL licensed. Meaning that we could technically take any mod we can get our hands on and incorporate it into the main game. If the mod author complained and maybe tried to take us to court, we would counter sue by saying you made a modification / plugin that is to be incorporated as part of our GPL covered work, meaning that they must provide their work under the GPL. I'm not saying that would happen, but it is a possibility, at least as far as I understand the GPL license. I glossed over the asset aspect. Those don't need to follow the code license, so if a mod had custom textures and stuff like that we couldn't force those to be included under the GPL license as they are data files the program uses. So mods with extra assets would be "safer" from hostile incorporation into the main game.

It's much harder to teach the computer to try to guess when you have made something resembling enough of some invention to enable a feature in the game With specified technologies arranged in a tree or web, you just tell the game to enable a feature when a technology is unlocked. With some kind of invention designer you first need to design the actual technology tree first, and then you need to make the computer guess when those technologies should be unlocked for the player