General Discussion

[DarkTl]

Almost in all cases their effects cannot be interpreted by dummy, that's why we jump to a label after all, to handle complex, unique logic.

Might as well disable dummy completely for such items.

[Xela]

I never know why these things just break down during refactoring... in either case, code that governed it was imprecise, this is much better:

Code: [Select]

            # if direction and getattr(store, "dummy", None):
            if getattr(store, "eqtarget", None) is self:

[Lurker]

Dragon Quest


https://mega.nz/#!OYJgwCYK!4icn0WGkK11xyDInQhccON1BbDcfxL8WTJ-ivWgB564

[Xela]

Kewl.

I did some work on jobs/tiers but everything is broken to the point that I can't launch the game atm. I'll see if i can debug to the point of pushing tomorrow or early next week.

[DarkTl]

I'm going to add info about items, such as the values of mtemp and ctemp fields, to items gui. Otherwise it's too confusing without the knowledge about game mechanics and reading items jsons.

[Xela]

I'm going to add info about items, such as the values of mtemp and ctemp fields, to items gui. Otherwise it's too confusing without the knowledge about game mechanics and reading items jsons.

Same setup as for the traits info?

[DarkTl]

I think it's done, now along with stats changes the game shows special fields, ie mtemp, ctemp, mdestruct, statmax and mreusable.

Although even with these fields misc items logic can be vague without a proper explanation. And I'm not sure where to explain it. I could add a book about it to library, but it's still not an obvious place to look for items mechanics explanations.

We still need to show skills changes for items, probably in the same way as we do it for traits. But since it required your coding skills for traits, it also requires them for items 

[Lurker]

Should a make a girlpack post in User Mods or where do you want it?


Anywho here's some Bleach.
https://mega.nz/#!vdZBmYhY!TM8TZxAmhxPGNdgEYwQBLfyZ1ZzaDX3c9I8yszJ7stI

[Xela]

Should a make a girlpack post in User Mods or where do you want it?

I am not sure, just make it here, I can always move it to mods section if something is off with the packs and you're no longer around or interested in fixing them.

We still need to show skills changes for items, probably in the same way as we do it for traits. But since it required your coding skills for traits, it also requires them for items 

I'll take a look at what you did and if we can implement the skills for items in the same way as traits. I was thinking of maybe doing that under "pro-stats" or that is useless and should be removed.

[Xela]

Oki. Took some doing but I hooked up skills info from items to the screen. It's in the left side, Skills button (former Pro Stats). I've also (hopefully) reliably restored tooltip so it can be used to expand on stuff we display on the screen when item is selected. I've also tried some icons instead of A: K: labels to represent knowledge and action parts of the skills but nothing seems better than plain letters...

[DarkTl]

Looks good. But I think you forgot about the other items screen which is used in shops and at the items transfer screen. If you take a look at my last push, I changed two files.

Although I have no idea where to show it there. Perhaps just do not show skills there?

[Xela]

Perhaps just do not show skills there?

Yeap. We can always improve the interface but I don't believe that we show a lot of info about items in the shop. Also, don't forget that we planned to reveal full info only to well developed MC at some point in development.

[Xela]

Oki... so, jobs/tiers are not going to pen out the way I wanted. The per job approach I now took is a lot better than the original plan (which was to focus everything in tier class) but still has issues, like for example we cannot reliably guess stat levels at specific tier. Good news is that it now seems possible to level up character to specific tiers. I will soon hook up ideas like dream job and current jobs to logic and take another shot at moving Jobs code to simpy land.

[DarkTl]

Just try to preserve image logic for whore jobs. It wasn't easy to come up with all those tags elifs to cover all possibilities.

[Xela]

Just try to preserve image logic for whore jobs. It wasn't easy to come up with all those tags elifs to cover all possibilities.

That's the easy part, those methods are all like individual funcs...