Brothel King - Girl packs and Mods Collection

[__neronero]

I don't know anything, tried doing tags based on other packs which turned out to be not so great of idea. Many of those don't make much sense and even saw some weird tags that are not mentioned in the guide.

There are two issues with only tagging for the game as-is:

1) Your pack has very limited flexibility. If Goldo or modders decide to introduce new features or rework old ones, your pack will likely require an update or become lackluster. (the tagging guide itself being outdated serves as an example of this)
2) To tag optimally, you will be required to do a lot of mental gymnastics & memorise hundreds of different image-calls from the game.

Due to this, most taggers follow the "WYSIWYG" philosophy. Meaning: Your responsibility as the tagger is to accurately describe what you see in the image through using the available tags. Applying those tags in the right in-game situations is not something you should be concerned with, but the responsibility of the programmer/event-writer/Goldo.

You may be right that orgy events are too rare in the current version of Brothel King, but I firmly believe that's something that ought to be solved by introducing more of those kinds of events on the code side, not by inaccurately tagging your girl packs.

 

[nahitsnotimportant]

Sure, but i'm only making stuff for myself, any possible, theoretical, metaphysical, esoterical tags that may appear by the time Cyberpunk 2077 will be fully patched and bug free is irrelevant to me. Guide seems to be good enough, taking it from there and by playing figuring out which pics trigger or not makes it easy to focus on parts of the game i'm interested in the most.

 

[Jman9]

by playing figuring out which pics trigger or not

Good luck with that. I'm probably among the top three people who know how in-game tagging works on the algorithm level, and I usually can't recall exact details off-hand. Never mind testing thousands of different use-cases.

This is not about adding more and more esoteric tags, since the 'extended' tagset covers a lot of what could conceivably happen anyway. It's about either reverse-engineering the game (and the rules change occasionally!) to tag, or just tagging what you see and hoping the game can take it into account now (or will in the future).

I used to be a big proponent of rules-based tagging. But that's because a) I'm not a pack maker and never release(d) any of my work; b) I have (well, had) a comprehensive plan for tagging to suit the game events (got into a minor flame war over my 'pilot check-list', even ) c) I rewrote a lot of the image selection routines to fit with my tagging.

So unless you plan to do a lot of planning beforehand, I suggest you stick with 'WYSIWYG' tagging.

 

[nahitsnotimportant]

Think I got the gist of it, it's not like i'm looking for things to be super accurate anyway.

 

[nahitsnotimportant]

Tried the Marie pack by __neronero and getting this often

 

[__neronero]

Bug in her BK.ini, fixed file attached & online zips updated.

Must've been broken for a while. Strangely my local BK.ini was fine - guess I must've fixed it and forgot to update at some point

 

[__neronero]

Reverse-ratting-jutsu! Jman9

Spoiler: Bananas error

You don't have permission to view the spoiler content. Log in or register now.

edit: I'm gonna guess it could be something to do with the oldschool TK potential/effect-boosting

 

[Jman9]

OW! Getting bent back by a rat hamster hurts!

I'm on top of it and the issue has already been resolved by applying the latest 0.4.1.2 update (since that error seems to be kinda ancient). No idea what precisely caused it, but I think I rewrote the dice() function at some point exactly because of these kinds of problems.

 

[rnxus]

Can I raise my MC skills by 10 or more?

In the 0.15 version, it was possible with SHIFT +!

 

[Jman9]

Playing honestly? The max is 10 from stats and +8 from items. Some of the stats can come from level-based special abilities.

Cheating? The only way I know of to go above 10 'raw' stats is to use the console.

How exactly 'was it possible' in 0.15? I tried 0.15b right now, and 'Shift + !', 'Shift + +' or even 'Shift + !+' did nothing on the character screen.

 

[rnxus]

In version 0.15 when you press shift +!, that command came out

I was able to raise my MC skills to 99

 

[Jman9]

In version 0.15 when you press shift +!, that command came out

No, it didn't. I just looked and neither 0.15, 0.15b nor even 0.14 code even contains the string "MC cheats". I suspect you are using Kite80's cheat mod or something like that.

Edit: Especially since the first screenshot in the OP, which was originally partly advertisement for Kite80's cheat mod/trainer, has that exact screen.

 

[Kite80]

In version 0.15 when you press shift +!, that command came out

I was able to raise my MC skills to 99

That was my old trainer for BK, not included in vanilla

 

[nahitsnotimportant]

The only thing I wish was more clear is which tags are exclusive/inclusive, like it mentions in the guide how "monster" makes it so pictures only appear in the farm. And there seems to be more, that makes tagging a real pain in the ass.

I want the better quality pictures to appear more through-out the game and i'm refrained from using more tags since that can exclude the picture from overall pool.

 

[Jman9]

That is the entire point of the tagging system: disable images from inappropriate situations. Again, I think you're going about it the 'wrong' way: do not tag for the current algorithms, tag 'WYSIWYG' and the game will generally make sure the picture only appears in the right situations.

If you refrain from adding a tag so that the picture appears more, you're making a pack where the chance of getting an inappropriate picture is much higher. Fair enough, if that's what you're after. Many if not most players are not.

 

[nahitsnotimportant]

Yeah, even changing farm content of all packs to fetish since i never use it anyways, i'm a naughty inappropriate boy

 

[nahitsnotimportant]

Again, I think you're going about it the 'wrong' way: do not tag for the current algorithms

Jokes aside that's my point, knowing the algorithm would help compromise less accuracy for the most quality

 

[Jman9]

Okay, then you basically need to take the tagging guide and improve it yourself. Get a file search tool (Notepad++ is pretty good) and look for... Hmm, _tags. is probably one of the more general things. Specifically, you want
and_tags.append(...), not_tags.remove(...), tags.append(...), maybe some others. Most of this code should be in BKgirlclass.rpy, BKfunctions.rpy and BKinit_variables.rpy.

You'll probably need to spend quite a bit of time grokking the code. As I said earlier, it's not something that's quick and easy to do.

 

[__neronero]

I think the best place to start is get_pic, that'll at least give you a general idea of which options are available when requesting an image from the game.

Spoiler: def get_pic (in comment form)

You don't have permission to view the spoiler content. Log in or register now.

Next you would have to start combing through the hundreds of mentions of "get_pic(" in the code.
It'll be a challenge, but a burning passion to create the ultimate pornography can overcome any obstacle!

One last bit of advice: Consider modifying the code of these get_pic() calls instead of adapting your girlpack's tags to it. That way...
1) Every girlpack will behave as you desire instead of just one
2) You can simplify the algorithm for yourself instead of trying to remember all the unique image requests in the code

Downside: You'll have to copy over the changes if you ever want to update the game. But Goldo has started work on 0.3, so we're not expecting any updates for the next few months.

 

[Jman9]

Next you would have to start combing through the hundreds of mentions of "get_pic(" in the code.

Looking through girl.get_pic() is a good idea. The generic get_pic() it's built on, probably not so much.

And most of the time tag conflicts are handled via constructing and_tags and not_tags beforehand and passing them as arguments to get_pic(). Which is why I suggested concentrating on those, since there's a lot more superfluous get_pic() calls. To be thorough, you'd need those as well, of course.