Two problems when hooking SiglusEngine about textractor HOT 8 CLOSED

ITHVNR worked fine for me with this game(金色ラブリッチェ), if that matters. The garbage hooks kept coming sometimes, but there always was at least one from the start which kept giving all the text needed.

from textractor.

@Mars132 Does Textractor get any good hook on this game for you?

from textractor.

@Artikash just tested with 3.2.2 a couple of times, seems to be pretty much the same as I had with ITHVNR. Just have to be more careful when searching for the hook, as it gives you list of about 40 hooks right away. I was able to firsttry finding the right one quite a lot by selecting about 3rd-7th number from the end. About 2-4 working hooks among the mess.

from textractor.

Ok, looks like this isn't an issue

...jk it is. Kind of. Since every hook creates a new thread as well, and Windows only allows me to create at most a few hundred threads, Textractor will crash after going through a few hundred lines of this game. I'll fix ASAP (but RL is picking up for me about now, so ASAP might be a ways off).

from textractor.

Also, I might suck at this terminology, those lines on the screenshot

each represent a different thread, right? And the right half of each line is a hook name.
If that's how things work, replace "hook" in my previous post with "thread".

Here I tried to break it, after adding aprox as much threads as on the screenshot it gave up with an error.

@tinyAdapter Finished the novel with no infinite adding and no crashes on ITHVNR. If you just want to read the thing, use the old way for now.

from textractor.

Yeah, each line is a thread. Having too many crashes. ITHVNR handled it with a hard cap on the number of threads that it would allow, I removed that. I have a better solution in mind.

from textractor.

Scratch that. I've tried implementing my idea and it's bad for some other reasons. Gonna go back to ITHVNR method of thread count hard cap.

from textractor.

Alright, fixed.

from textractor.