Leaderboard

Thank you! This mission gets more and more intriguing as I go along. Very creative story idea.

@stgatilov

Holy war mode on ? You probably know little software, or only a very limited class of software. See Myth #5. Keeping interconnected applications in single monolithic repo has a lot of benefits over having different repositories. The main benefit is that every revision is set in stone and perfectly reproducible afterwards. It is also possible to do atomic changes to several projects. Just read about why Google does that. SVN allows you to checkout only a few subdirectories of the repo, so monolithic repo does not forbid people to download only what they need. Git sort-of has sparse checkouts, but there are complicated, most likely limited, and etc. Submodules... I'd better never know of their existence ? Yes, SVN is known for having more conflicts and having worse tools for resolving them. But with trunk-based development, they rarely happen. On the other hand, conflicts are the core nature of all VCS we use. Don't tell tales that conflicts won't happen at all with git. The same thing happens with git when people work via merge requests. Which is how it is usually done, especially for outer contributors. Changing VCS won't help you much with not breaking trunk. Unless you are going to work in your private branch for months without merging back, in which case nobody will ever review&accept your merge request due its gigantic size Yes, and this is very dangerous, because most of developers are poor testers. They will gather bugs in their branches, and then when they consider them "truly stable", merge all these bugs into trunk/develop. And nobody will notice it soon, since everyone is deep in his own branches, branched from develop a month ago. I prefer following the most widely used practice of game development, when everyone is sitting on trunk, so that all bugs get noticed and fixed quickly. Do you know that in Naughty Dogs artists even have an auto-update script for assets repo? So that when someone commits something, everybody forcibly gets the updated version. This is a relevant topic due to recent server outages. It is planned that our admin will provide readonly access to current backups to several members, to be sure that the whole TDM knowledge base does not suddenly disappear. Speaking of normal usage, SVN has zero chance of losing data, since there is no history rewrite. Git, on the other hand, has lots of unsafe ways to edit history, and it is often encouraged. Which provides a good opportunity for users to lose their local history. And in worst case, I guess even remote history can be lost. Recall that git is not a Version Control System, it is a "Stupid Content Tracker". Stupid enough to lose the content it tracks. Holy war off? I think the main reasons why SVN stays on TDM are: Aside from the engine source code repo, we have a few more repos. They contain assets, and migrating them to git would be a disaster. And since they stay on SVN, source code should better stay on SVN too. Avoiding one more VCS is enough reason in itself. Git is inherently harder to use than SVN. Moreover, it is harder not because it has to be so, but because it was ill-designed. I don't like the idea of forcing complexity onto everyone (including myself BTW). Whoever wants to use git can take the additional complexity onto himself and use git-svn, or any other approach to synchronize SVN with git. Also, we have artists: while usually they don't work with source code repo, sometimes they decide to build the engine themselves. There are ways to use git locally with SVN. I do this sort of thing myself with hg. Some time ago I suggested creating an official GitHub mirror for source code repo, with some semi-automatic workflow for accepting pull requests. As far as I remember, nobody was interested. And migration is unlikely to happen.

@greebo

I probably have too little competence to discuss about the lore, but... if it was for me, the vocals could be a bit more concise. When i read the lines, I have to wonder what really distinguishes them from the other factions. When I read this: https://wiki.thedarkmod.com/index.php?title=Pagans , the Pagan culture IS deeply rooted in nature and animals. So, maybe a tad more references to that would be nice. All I read are references to the "spirits", which is great, but, that could be any other urban faction who believes in supernatural things as well. When i take a look at Thief 1-3, the Pagans were a very characterful and colourful bunch. Would be a bit disappointing to lose that. I know the TDM Pagans are supposed to be different, but, IMO, the faction just screams for tribal, mystic, spiritual nature weirdness, and, that should show in the way they talk. In my opinion.

And here's the consolidated Google Doc: https://docs.google.com/document/d/10b4A9_YBGqdB9ZpN_YVWhWgu92L9pRrZrxsrQVQyAOI/edit?usp=sharing At present everyone is able to edit and comment it, with a backup to be on the safe side. If you have Gmail or a Google account (register here) and send me the name I could reserve the full edit rights for us while still allowing comments by anyone who's interested, which may be the most sensible approach. Commenting is either done by selecting a phrase and clicking the speech bubble with a + icon at the top of the screen, or you can switch to suggestion mode by clicking on the pen at the top right. Indeed, we actually have the luxury of choosing the best lines for each situation as the script is now at a total of 330 lines - the only section we're still short on is conversations (the old master script had far fewer such situations), and I already quite liked the ones you've made. Something we could do is allocate some lines to subsets: your mouse & rat lines to an urban pagan, while something like "This is your death, outsider!" could be more suited to a rural pagan living in an isolated society. Practically speaking, I'd imagine separating the lines by putting a blank space (enter) inbetween the 'keepers' and the rest. I've also separated out some shaman lines by putting 'Shaman' on a new line and his dialogue below it. Also, I've taken the liberty of moving all the multipliers (x2, x4 etc...) from individual lines next to the name of the situation, as they're meant to denote how many lines to have for that situation. This is the same for me, and surely most people around here this time of year. Let's just see what we can do for now.

The bank of Colliford Lake (HH:TLC, Part 1: The Weir) Did not make much progress the past weeks due to RL things. Original plan was to start beta next week. Far from it, actually.