Dashus

Quite. Because we put real life ahead of the mod. Scandalous, I know.

I actually find the whole reaction to the leak amusing. It's almost like a battle in some ancient war where I get to put down a blanket on an adjacent hilltop pull out a sandwich and watch the carnage unfold I suspect there will be many complaints about 1.0b9 Not the least of which will be "why can't I update to the next version?" We actually explicitly tell the build scripts to build the updates from each version to another; updates from 1.0b9 to anything literally won't exist.

Well that's awkward given I'm still working on the mod

Who said all content was restored? (Watch it be me ) I would agree that a crunch period would be great but our available time is dictated by real life.

Really the leak has nothing to do with it (though I also recognize that some people won't believe me no matter what I say about that ). We just have time of late.

If we had chosen from the start to do so it would have to have been a two stage development: fix existing bugs and restore content (+ fix bugs we created). We did actually briefly consider that possibility but decided we might as well just do it all in one go because it was less of a headache.

Already have technically - issue id 1000 is in the system already. A few issues have been outright deleted for one reason or another.

Come on guys! We can make it! To 1000? i say it again dosn't it suck that this game was released in such poor shape i mean 1000! that is rediculous I would venture that 2/3 of those are caused directly or indirectly by us.

It ends whenever it ends.

Beta Software development generally uses a (alpha aka pre-release) and b (beta) (and occasionally c (gamma), though that's rather rare) in versioning.

The engine tends to just start doing wacky things after playing for a couple hours. It fails to fire triggers and dialogs skip all non-player replies among other things.

There is no requirement for number of playthroughs per build. They play however times they like. Updates come weekly. We release when we feel we're ready. At this point it really is that simple.

I'm confused. Who said Handmaiden/Visas wasn't in? Because it is. There was a bug that was preventing from triggering. But that's the extent of it. You're not getting it until 1.0c1. I would guess that most of that content will be in by that point. I believe the only thing we've said is "we'd prefer to not have to patch it." You don't implement a patch system wanting to use it It's three years btw.

Just an FYI: 0.9b1 will be the only build in the 0.9 family. 1.0b1 may take a few weeks but it will be the next build. The invite-only beta will begin upon its release.

Yeah that's intentional. The problem with having him leave is that it's impossible to verify that the player cleared the side he chooses to run off through of enemies (or at least not without more pain than we're willing to deal with in TSLRP.)

We don't. As you stated this project is about "restoring cut content." There are some pieces that were pretty evidently supposed to go in certain places but we've never claimed that we're "restoring" the plot as it was intended. Only Obsidian could do that.

More than a dozen. 0. Unless you count 'stunt' modules which are just duplicates of existing modules used in specific scenarios, in which case, roughly half a dozen. 1. Under half a dozen. I think it's 2-4 but I could be wrong. Keep in mind we all work on different bits, so all of those numbers could be off.

It's been hit or miss for me the last couple days as well...happens every so often.

Done and done.

Actually the translation team doesn't even have anything to translate yet as I'm just getting over a nasty sinus infection Also given that they were just brought aboard less than a week ago I very much doubt they would have been close finishing within 2 weeks

Not really. It was mostly that it occured to us that most of the bugs have been fixed and given that there are likely to be more after the last of the content is restored it was prudent to move the "fix remaining bugs" step to after the "restore remaining stuff" step. WIP page has an updated build plan.

Yes. And the download links will disappear after the mod is out, largely because most of those fixes are now incompatible with TSLRP as they were little snapshots from early in development.

Unless we already had a willing host.

I very much doubt it will take a year to do translations. We have a well kept log of all the changes made to the tlk file. There's under 200 distinct changes made many of which are gramatical and could be handled with a "replace all." I wouldn't anticipate translations taking excessively long. And as I've said before, there will be stuff for us to do even as the translation is going on, so it's not as though the translations will somehow "hold things up." I should also point out that "muliple language building successfully" simply means that translation is done. That build plan as it stands was written to be as generic as possible on the outside chance that building the foreign language versions along-side the english language versions somehow got messed up. But we've had dry runs with fake files and the foreign language versions seem to build fine. THe installer is common and only the updates ares lightly different and even then it's handled with a common build script.

Really the issue was/is that it's a crapshoot trying to get any bipedal droid to come out of the the disabled animation reliably. They claim in the documentation that using one function call will work, but it doesn't happen when the call occurs. It seems to happen at the end of a round. Which isn't so good for cutscenes. So it's just a matter of showing them activating/activated without the need for that kind of precision timing.