As is typical of poorly-made, outdated CC, it needs to be manually updated.

Fixed link.

Talk is cheap.

There isn't one. That's the point.

Exactly.

Officially, EAxis, which is the operating principle which allows PMBD to operate openly and publicly. No one seems to want to actually fight this as a legal case in an actual court anywhere, though.

I do server and technical things. I don't maintain content, that requires contacts with people who have feelings.

I mean that, yes, obviously, this place is now fairly quiet, and that people have taken the paysite war to their own other sites.

Yes.

Given that we have no suppliers or maintainers, no. People seem to have taken their business to various other sites, but we have no plans to otherwise shutdown anytime soon unless I keel over dead. Which could happen any time given that I am terminally old.

That is the Steam patch? It SHOULD be, in theory, since everything else is, even if it complains, but I don't have Steam, and the 1.69 patch isn't available elsewhere, so I have never tested against it.

No, no you don't want your game to run/look/behave like mine, because my game tends to run in modder-debug-mode. The non-debug stuff gets released here.

Did the fences reappear when you did this? If the fences reappear when you do this, send me the original package and I will take a look at it.

You can't recompress an encrypted pack because the index that contains the sizes of everything in it can't be read.

Recompress is mostly about repacking the file to save disk space, and doesn't materially alter any of the innards of the file. Decrapify attempts to remove the tags that prevent the content from loading in the game.

I somehow don't think that's actually going to help in any way, but it probably won't hurt, either.

I have no information about this set. Are other fences from other sets affected?

Not without a far more thorough code audit than I have time to perform. I don't install other peoples' stuff.

Okay, so I dug into the code and found out how to probe it for whether or not the story progression engine is turned on...I think.

Obviously, I have no way to test this, as I don't actually have the mod installed, so either you're going to have to come to #grah, or operate on a very slow testing cycle where there's no fast way to get you test builds and get any reports back.

Your image hosting service has died, I'm getting no connection to it. Can't view.

I'm not sure how you "turn it off". But if you have it installed, AwesomeMod is able to detect that you have it installed and will cede control of story progression over to it.

Now when you say "another world", you mean that you are turning it on and off on a per-save-file basis? What does this look like? Because searching for this behavior in someone else's code when I've never experienced this code in an ildasm output is needle-in-haystack shit.

I have not currently implemented any method of doing this, because I wasn't aware that NRAAS story progression was "world specific". Since it makes no sense to have two story progression drivers running and fighting each other, I simply reasoned that if you installed NRAAS, you clearly wanted that one.

What do you even mean by this, anyway? You mean you have different saves in different worlds?

If an action is illegal, it should be marked with the handcuffs, so I don't think this one is flagged as romantic, seeing as it's the opposite thereof. But if anything happens, let me know, because it should be totally okay to break up with someone for being 12.

In theory, there was nothing actually changed in the Steam version, so yes. However, I obviously do not have the Steam version to test it with.