/jp/ - Otaku Culture

>>43939766
>Source: Your Ass.
Well then, anon, why don't you show me all the dialogues with specific text for threesomes? Surely that will be easy since it's such a popular things to write for, right?

There are only six characters with any amount of dialogue for Alternate Insertion, and of those, five only have dialogue with very specific partners.
The full list is as follows:
-Hatate (with Momiji)
-Kaguya (everyone)
-Benben/Yatsuhashi (with each other and Raiko, but there's no actual substance to it)
-Toyohime/Rei'sen (with each other)

Kaguya, Benben, and Yatsuhashi also have reverse dialogue for when they're the previous TARGET (still nothing substantial for the Tsukumo sisters), which is handled in the most obtuse and buggy way imaginable, as I've come to expect from Japanese code, were it's effectively impossible for alternate dialogue files to trigger their reverse code since it will just call the main dialogue every time.

Fixed some issues with requests:
https://files.catbox.moe/tmu0f0.7z

The biggest thing this fixes is unaccepted requests actually being cleaned up when they should.
Y'see, the intent was that when you wake up, the game would make a call to each request the player hasn't actually started to see if they should be reset and eventually re-rolled. This is supposed to be done by making a call to the "依頼消滅条件" case of the specific's request function, which determines when a request should be cancelled (typically just a 30% chance each day, though newly created requests are excluded from this check). However, instead of calling to "依頼消滅条件", the game would actually request "依頼消滅率", which is not defined in any request, and as such would do absolutely nothing.
As a result, no request would ever be reset unless the player actively accepts it and either resolves it or cancels it (or resets all requests through the menu).

This is enough of an issue in and out of itself, but this is then compounded by another issue. Request 13, the dreaded fishing request, is supposed to be disabled if you don't possess a fishing rod. However, the way it's coded is that the request can be rolled on the request gacha just fine, the player is only prevented from seeing the request and accepting it. This means that the specific character will forever retain the fishing request as their current request, even though it can never be accepted. Hypothetically, this means that eventually every character (other than Wagasakihime) could get stuck with a fishing request the player cannot accept until they buy a fishing rod, making it impossible to complete any request.
The recently added check to the mod branch to disable logging and fishing requests function in the same way, and similarly clog up the request system, though I can't blame the Japanese completely for these.

I've also made some changes (really just reverting ENG-only changes) to one of Reimu's unique requests in @固有依頼1, since I don't think those worked as intended.
I think the idea was that Reimu would not offer the request to hand Marisa her item back if Marisa was already present at the shrine, but you could still accept the request just fine, and the only thing it actually did was prevent the player from handing it over to Marisa as long as she was on the shrine map, which was just confusing.
Since the associated dialogue has special consideration for Marisa being in the room with Reimu, with added dialogue for that scenario, I decided to just remove those limitations, which makes it very easy to complete the request if Marisa is already there.

All in all, I've patched the following things:
-The call in @IRAI_VANISH has been changed from 依頼消滅率 to 依頼消滅条件, allowing inactive requests to be cleaned up
-@一般依頼13 now completely blocks the creation of the request if fishing requests are disabled or if the player does not possess a fishing rod
-@一般依頼14 now completely blocks the creation of the request if logging requests are disabled or the player carries no timber at all
-@固有依頼1 has some checks removed