General Discussion

[DarkTl]

Hm. Alright, I'll only change tags for locations pictures then. Thankfully, we can customize GM pics as much as we want already.

[Xela]

Yeap, that will be useful

I got an hour off so I am trying to debug some stuff in Bar job. Sim'Py is difficult to debug because it has it's own error reporting mechanism, I have not yet looked into how to make it work with Ren'Py better than it does by default... prolly cause I expect that it'll be very complicated cr@p to take care off and may not be worth the effort.

[DarkTl]

We have some non-sprite backgroundless pictures, with no bg tag. They could use a white background whenever we show them instead of the current black one.

[Xela]

Small things like this we can fix after everything else is done.

[DarkTl]

Well, there is not much I can do at this point rather than testing the game or building packs, so I test it to find even small issues and work on another random char. Because

- Moar quests mean SE
- Classes should be synchronized with actually existing, coded jobs before I'll begin to use them actively without the fear of them being removed from the game
- Matrix-based exploration requires a way to change party members from an arbitrary pool of characters without access to MC screen

[Xela]

SE is just a way of acquiring items/moving quests to next step, they should not prevent anything.

Classes you can take care of yourself if you like, we at the very least need a better normalization routine when assigning them.

You'll have to clarify on the click-and-point exploration cause I don't really understand why party change screen is required there.

==
And there is a lot more you can do, for once you can offer more opinions on what jobs should be like.

[DarkTl]

SE is just a way of acquiring items/moving quests to next step, they should not prevent anything.

I mean I cannot finish existing ones properly atm.

Classes you can take care of yourself if you like, we at the very least need a better normalization routine when assigning them.

I dunno. Let's say we have a dancer class, but in fact there will be no dancing at all, except maybe for striptease, and that job has strippers already. So dancer class will be quite useless.

You'll have to clarify on the click-and-point exploration cause I don't really understand why party change screen is required there.

- we cannot guarantee that MC is able to fight. Moreover he might or might not be able to fight regardless of class, it's up to players. Sure, a warrior will do it better, but non-warrior still could or could not be used in BE.
- as you find new chars during exploration, you could add them to your party, replacing those with low health for example.

[Xela]

I dunno. Let's say we have a dancer class, but in fact there will be no dancing at all, except maybe for striptease, and that job has strippers already. So dancer class will be quite useless.

That's what I meant as part of jobs discussion, what jobs will have have and how far will we take them...?

- we cannot guarantee that MC is able to fight. Moreover he might or might not be able to fight regardless of class, it's up to players. Sure, a warrior will do it better, but non-warrior still could or could not be used in BE.
- as you find new chars during exploration, you could add them to your party, replacing those with low health for example.

I think that is a bit clumsy, there are plenty of games where changing teammembers in combat areas/without returning to base is not possible.

Lets keep things simple! We are working on too much already.

[DarkTl]

Ok, I'll take a look at jobs code for a start. All jobs are in classes - jobs rpy, right?

[Xela]

Ok, I'll take a look at jobs code for a start. All jobs are in classes - jobs rpy, right?

It's scattered at the moment, but all of it should be in jobs folder.

[DarkTl]

            # Lesbian Act
            elif self.client.act == 'lesbian':
               
                self.skill = "vaginal" # May be overwriten!...

It's too simple. Checked skill should be based on selected picture (dunno how to do it in terms of code, you show pics after you select skill there).
Also in some cases we could use several skills to check (lesbian group for example), but it could wait for next release. Lesbian actions however cannot.

This too.

[DarkTl]

Atm only bar brawls require guards? Clients never attack whores, don't try to rape someone?

[DarkTl]

I recall we had various actions during rest depending on girl traits in the very beginning. Not anymore though. What happened to them?

[Xela]

It's too simple. Checked skill should be based on selected picture (dunno how to do it in terms of code, you show pics after you select skill there).
Also in some cases we could use several skills to check (lesbian group for example), but it could wait for next release. Lesbian actions however cannot.

Why is it too simple? I also complete disagree that mechanics should be guided by content, that will create a cluster f*ck in code and gameplay. We cannot think that way...

This too.

Messy... but prolly doable. These checks are very costly in terms of code clarity I'll take a look at it.

Atm only bar brawls require guards? Clients never attack whores, don't try to rape someone?

ATM, it's neither, I want to have normal BE calculate the combat. It'll require a lot of coding so events are not working atm. Maybe I'll restore old events first, I am not sure yet.

I recall we had various actions during rest depending on girl traits in the very beginning. Not anymore though. What happened to them?

Removed for now. Most traits we checked are now gone, some were replaced with base-traits that are not named in the same way. Rest now is also working differently.

===
Jobs/Businesses have been completely rewritten. That opens a lot of possibilities but I still don't have the loops perfected (yet). General logic seems to be working really well.

[DarkTl]

Why is it too simple? I also complete disagree that mechanics should be guided by content, that will create a cluster f*ck in code and gameplay. We cannot think that way...

Lesbian actions are much more varied then others. What if there is strapon+anal or 69 action, yet we keep checking vaginal for everything?

Removed for now. Most traits we checked are now gone, some were replaced with base-traits that are not named in the same way. Rest now is also working differently.

I don't see them even in comments. Doesn't matter, I'll recreate them using available pics instead, like issue 136 says.