5 ms·
It's a shame that it took a threat of a lawsuit for it to be released as open source. This wasn't a game that was ever charged for, so I see no reason it shoul
by CydeWeys 10y ago
It's a shame that it took a threat of a lawsuit for it to be released as open source. This wasn't a game that was ever charged for, so I see no reason it shouldn't have been released like this 15 years ago. There's actually a weird culture in roguelikes (and similar ASCII games) of not releasing the source, and using opaque, non-open development processes. NetHack was open source but only recently switched to an open development process recently, and may other popular entrants in the genre such as ADOM and Dwarf Fortress are closed source entirely.
- problems 10y agoYeah, I think that might be a matter of wanting to keep things secret from players. Of course, it doesn't keep things secret from players with a copy of IDA and too much time on their hands, but it probably adds to the mystery for some people.
- clarry 10y agoI don't think it's about keeping secrets. Stuff are often covered in great detail in changelogs, development blogs, forums, etc. And players figure stuff out. All the info will be on wikis. It is not effective. If people want to spoil it, they check out the said wikis. If they don't want to spoil it, they don't check the wiki or the source, if it is available.
- hurbledr 10y agoActually, several developers have stated as much, most notably Thomas Biskup, who develops Ancient Domains of Mystery. That's not to say you're wrong on any of your other points, but I think the reasoning for it isn't so much to prevent players from figuring stuff out and publishing guides, but more to encourage players to experiment and figure stuff out for themselves rather than relying on a guide to tell them the 'right' way to do things.
- Cursuviam 10y agoIn Dwarf Fortress's case, the closed sourcedness is because the creator wants to be the sole driver of the project until it's "done."
- CydeWeys 10y agoIf they don't accept PRs then they will still be the sole driver. But if I were in his situation I'd at least take PRs for simple bug fixes. That gives you more freedom to work on creative stuff.
- gwern 10y agoGiven the ecosystem around it and the reportedly parlous state of the DF codebase, I would guess, somewhat along the lines of Minecraft, what would happen upon open-sourcing is that people would start big cleanups and APIfying, and he would have little choice but to either accept PRs en masse or quickly be left in the dust with an obsolete codebase while everyone begins using a version forked from whenever he balked at a re-architecting patch.
- ludamad 10y agoI'm inclined to agree that in practice you just can't ignore open source contributions if you want to remain the official version. The moment the community is patching faster than you your changes start to become ported to the 'official version' and not the other way around.
- CydeWeys 10y agoHe could add trusted contributors to handle that load for him. No one says he has to handle merging all the PRs himself. Dwarf Fortress has a huge community of very technically-minded people. The end result would be better with more contributors, especially if it freed up the attentions of the main developer to focus solely on the creative stuff while bugfixes and maintenance tasks were handled by the community.
- 10y ago
- daviross 10y agoIt does note that the original plan was to open-source it once the Kickstarter completed, so I suspect a decent amount of it was "From an older era of Roguelike development"
- boomlinde 10y agoOpen source may mean additional administrative overhead. For a game, which is essentially a sort of artistic expression, there may also be little value to the author in external contributions or derivative work. Forks or exact specifications of the mechanics could very well compromise his artistic goals.