General Discussion

[Xela]

Fair enough...

[DarkTl]

Um, why do we show character base class twice? First with white text next to the new frame, then in the end of the left frame. And with different logic, no less, so I dunno which one is better.

[Xela]

They show the same thing... I came up with the text version first, later added the buttons with an intent to make different once for SIW, Service, Warriors and Manager classes.

Leave the one you like best and comment out the other.

Only TisaOTM/default fonts works with weird characters, you've used something else for full names so I am getting "artifacts" instead of the weird unicode. Frame you've used is also small so on longer names, it changes size which is a bit annoying and didn't happen before.

[DarkTl]

You should have seen it before I reduced font size, really long names ruined the whole gui immediately 

Whatever I do with the frame, it won't be a reliable solution. The whole left panel is too narrow to support names of any length. We should move full names somewhere else, or change font size depending on the text length.

Actually, I wonder if the game can pick font size depending on the text width, without manual length checks.

[Xela]

No, it cannot. We can move them to Edit: *tooltip viewport maybe... as part of the default.

[Xela]

There will be even more work with the next release if I decide to update stuff to new interface paradigm. Everything will still work even without any modifications but I love the new way it is coded, it'll definitely worth doing for the next major refactoring.

[DarkTl]

There is also SE, a huge field for coding with SimPy and for creating events and locations 

[Xela]

A lot has been taken care of already on jobs, buildings and simpy areas. I am more concerned about fullfilling the interface gismo vame up with cause that seems like boatloads of logic. Tonights effort of building team reports for jobs went really well. I cannot crack one of the issues with it yet but it might be ready tomorrow. It's another thing we can use for SE.

[DarkTl]

There will be a series of quests based on Naruto there as well.

Eh, most quests are kinda meh, I'm going to remake them. There is a difference between an idea and actual ingame events. Something that looks good on paper or in imagination is not so good at the screen.

[Xela]

I thought it was ok for a start.

Team Jobs Reports are more or less finished and working well. I am going to adjust cleaning job to them soon.

[DarkTl]

Of course we need more finished systems to make proper quests, like SE, which effectively allows to search for hidden or lost characters and items outside of VN mode with minimum coding.

I tested the village a bit, it's quite inconvenient to use matrix every time you want to visit the ninja shop. Gonna make it work like other shops.

[Xela]

Of course we need more finished systems to make proper quests, like SE, which effectively allows to search for hidden or lost characters and items outside of VN mode with minimum coding.

I told you, it shouldn't get in a way if you leave out the bit that requires the module and just set up conditions during testing as if something was accomplished or failed...

==>
Core cleaning job and team reports are finished, you'll need to update testing.rpy if you want to test it. For team reports, we'll use autoscrolling stats and images (latter if there are too many images). Cleaning job requires more luv (pretty much like all other jobs) but I am not going to micro it atm. Next is prolly the guard job and/or whatever else is left.

[DarkTl]

I'm afraid due to lack of a detailed concept I dunno what SE will be capable of.

[Xela]

I'm afraid due to lack of a detailed concept I dunno what SE will be capable of.

Who gives a damn... you wrote: find a person/item. Just write the conditions as if a person/item was found/quest was failed. It will be resolved in SE later.

[DarkTl]

Ehh, we probably shouldn't show gender field for gifts, materials and loot. It's not just useless, it looks weird to have a unisex glass