lynx

Hey, did you build it yourself? 1. I'll take a look. /.../ I can pick it up just fine. Even move it around more than I remember was possible. 2. Some traps are resetting by design, you'll need to provide a concrete example, so the data can be examined. Press ctrl-m on a detected trap to get a nice dump. 3. Can reproduce, looks like a bug. 4. Can't reproduce, do you have a reliable way?

No, why would you need backups when you can uninstall mods?

How about uninstalling mods?

missing a "no backup" option. missing a wtf option to the categories question. missing an OS question, so us liberty lovers and macers won't skew the results too much. further automatic qa improvement would be to ifdef many of the questions depending on the initial bws answer. Many don't make much sense for plain users.

If you don't have a clone to git grep through, github is a good basic searching alternative: https://github.com/Gibberlings3/SwordCoastStratagems/blob/d25ff1b6568690c1bc4dc3b8c8788e4c7d205780/stratagems/caster_shared/caster_shared.tph#L170

Both BWS and its EET version are hosted on github, so there's no real danger of downtime plus they're innately unfragmented. If an extra list is needed for TCs and bad mods, stuff that can't end up in the BWS, that can be a separate thing. I don't see any benefit of hosting a list of links on git though, it just makes it hard for other people to contribute if there's no userfriendly interface (eg. wiki or something more complex like lgdb). Also, I've read the other thread and I don't really see any dishonesty anywhere. Harder to detect through text, but still.

BWS already uses my microservice to be a bit smarter about projects hosted on github. While I don't agree with some individual choices (having been a packager years before), it does use the latest release, prerelease or master automatically. Here are some docs: https://github.com/Gibberlings3/modhub I don't see how you could do any better than that for (semi)automation. You could add extra tags for more categorization to BWS and create a simple parser for a web frontend ... voilà, you saved a ton of work. Getting modders on to VCS is an orthogonal matter and you'll get everyone's support there.

Besides what has been said on the other thread, you seem to be mirroring the repos, so users would always download the main branches' HEAD. That can easily be unstable stuff in between releases, so not ideal. Other than that, we probably all dream of a central place and the best we could come up with is the database used by bws.

Just dumping everything on a (git) hosting service won't achieve much. Authors need to be convinced to start using them or things will just get stale. We've had a long discussion about this sort of stuff before, which resulted in the current sitation, where more and more g3 mods are under external revision control. Not sure you can access this thread though: http://gibberlings3.net/forums/index.php?showtopic=27649 Either way, anything on github can be mirrored automatically, once you know it exists.

Why the strawman? Read everything ...

I was refering mostly to the other points, but yes, a proper fighter/sorcerer is a simple weidu mod away.

gemrb allows for some of this, but it's a big load to swallow.

How about 187/195 or the two stats holding titles (class strings)?

Looking at our code, the extra object is supported in all iwd variants and pst, but we don't use it anywhere yet, so can't confirm anything.

Sounds like something long abandoned and unfinished. No mention anywhere in iesdp or gemrb.

It doesn't add up, it would introduce a gap. But that's just parameter6. Fixed.

Cool, one more for the evil side of things. Does she have any serious conflicts with other npcs that people should know about (like Edwin and Minsc)?

Yes, it will work fine on linux.

./ is not needed to enforce relative paths, unless you need to remove an ambiguity — like with running stuff in the current dir. Above, you're not passing anything to weidu, so not sure what you're trying to achieve by running it.

Nice, didn't realize g3 was 15 already!

You mean a few days?

unless you have pre-g3 links to iesdp, they all point to the most recent version.

Just the title is wrong, but it's fixed now.

Yes, the offset were clearly forgotten. I can confirm the rest too; as a bounding box, this can never be rotated, so it should be clear enough. updated.

I understood it as an extra way to reduce the confusion between the two. And really, as a fork, the team behind it can point it to wherever they want.