General Discussion

[Thewlis]

Good news! While I didn't straight up revert the jobs file, I did go through and add back every girls.remove(girl) call so whores now service multiple clients, and every other job should be working as originally intended again.

I fixed the Service girls not bar tending (I made a typo) and added the "les" tags back to the lesbian sex act.

I may have also fixed CityJail, but I'm still testing that.

[Xela]

http://www.pinkpetal.org/index.php?action=post;quote=30968;topic=1291.4000;last_msg=30969

Great!

I've updated items transfer screen:

[Thewlis]

Alright, I've definitely fixed the CityJail/RunawayManager next/previous index problem.

Although I've got to ask, is there an important reason, asside from standardising it with normal screen syntax) that the location_actions positioning arguments were renamed? 'Cause using align doesn't work with submenus as the whole screen will be moved more and more to right with everyone opened.

[Xela]

Although I've got to ask, is there an important reason, asside from standardising it with normal screen syntax) that the location_actions positioning arguments were renamed? 'Cause using align doesn't work with submenus as the whole screen will be moved more and more to right with everyone opened.

I couldn't figure out how to work the code but everything seems to be working fine, where does the code fail? There was no important reason, no.

[Thewlis]

It was the use of align. Align is basically shorthand for pos and anchor, so:

Code: [Select]

align (0.95, 0.95)
==
pos (0.95, 0.95)
anchor (0.95, 0.95)
The issue is that as the action screen gets wider when sub menus open up, the x anchor ends up moving further inwards as 100*0.05 == 5, but 200*0.05 = 10. It was only really noticeable when I was testing with the maximum number of sub menus as it became more and more pronounced.

I've fixed it by changing the default arguments to pos=(0.98, 0.98), anchor=(1.0, 1.0), align=None so it gets positioned at the same place but has its anchor set at the very end.

TBH naming the positional arguments like that is probably for the best. Certainly matches the rest of the screen code, although I did like how left/right top/down sounds.

[Xela]

Well, feel free to change it back or fix whatever is wrong with it.

I wanted to set ypos to three hundred and something and anchor it is such way for girlsmeets that middle of girlsmeets menu would find itself perfectly aligned to the middle of bar. I couldn't figure out how to get it done with the old code so decided to rewrite it a bit, after testing everything seemed to be working fine. I didn't test more tiers

[Thewlis]

Don't worry, I just needed to change the default arguments to use anchor and pos instead of align.

[Xela]

Kewl.. I am done for the night, pushed last minute fix to old sh!tty code in items transfer screen.

Next thing should prolly be more stuff for girlscapture (now working) but captured girls don't get any special treatment in jail.

I want a moderate "registration fee" and "upkeep" cost. They should either be sold chap to Stan, receive expensive/lengthy (Break) training with Blue or be sent to training dungeons if player has such a thing...

[DarkTl]

...or be released and either returned to wherever they were captured or added to city population.

[CherryWood]

How do you plan to add girls to the locations?

Right now, it say :"girls": {"Angel": 100} in the cursed forest, but players may not have a girl with that ID in their games, so is there another way?
---------------
- merged my loose item file with others + small stuff
-------------
Maybe something with gears?

[Xela]

How do you plan to add girls to the locations?

Right now, it say :"girls": {"Angel": 100} in the cursed forest, but players may not have a girl with that ID in their games, so is there another way?
---------------
- merged my loose item file with others + small stuff

Nothing will happen if they don't.

[DarkTl]

I suppose time related characters like Sakuya from touhou project can be met near the temple of time. So we probably need names and meeting code for all freely accessible locations, unless it easier to handle via custom meeting scripts.

[Xela]

I suppose time related characters like Sakuya from touhou project can be met near the temple of time. So we probably need names and meeting code for all freely accessible locations, unless it easier to handle via custom meeting scripts.

Individual cases should be handle through the event system, we're not going to expand modules to auto-handle cases like these until 1.0 if finished. I got an hour or two, going to look into if the top stripe can be auto-hidden with gismos new map (just that one screen and map option) like the windows toolbar...

[Xela]

Pushed logic for gismos new map, top stripe is a dropdown on the main map now...

Apparently you can't properly use screen variables declared in screen that was called with use statement, only from parent... took me a long time to figure that out

[Gismo]

Well, that's all I can do for Temple of Time. I left a place for npc in the right part of the picture.