General Discussion

[lamoli]

Here Another one..





Ineed to work more on the belt...
And since you do not have a slot for bra(underwear) i combined it into the item

[lamoli]

Didn't we decide to split the suits into bits? This is excellent regardless of that

What do you mean by bits ?.. like top and skirt separate ? leggings/shoes always are separate but i show them in full render when i decide to add them.. ( but can be done later on )

[lamoli]

No, equip doll is plainly the sprite we add to the equipment screen paired with positioned slots. To change the clothing on sprite or to change the sprite based on equipped item simple function would have to be written paired with adding new fields to items data file(s) and relevant loading func. Depending on complexity of design, whole thing can take from 10 mins to 10 hours but I doubt it'll be more than that (the only way that it will is if we decide to build OW like doll which will require careful positioning of clothing, possible re-sizing and layers), such system is still not very hard to code in but will take time to get write through trail and error.

I already tryed the layer system.. you just add the clothing image on top of the body thats all.. ( no positioning or resize needed )


Use this as base..





Then with gimp or other program to add layer on.. use either ones..





Of course the clothing image is not perfect and sometimes get transparency problems.. but its fully automated.. the result you see is made by pressing a button.. so with little work with editing manually they could be perfect.. unless i improve my automated method..


Same will work for every pytfall item once i make/render them.. you just past them on top ( but you might need to set some items to specific layer like cloak above all else.. while some goes under others and so on..

[Xela]

What do you mean by bits ?.. like top and skirt separate ? leggings/shoes always are separate but i show them in full render when i decide to add them.. ( but can be done later on )

Yeah, I meant splitting top from bottom. Maybe stockings as well (I don't think that we have a eq spot for this), shoes most definite.

I already tryed the layer system.. you just add the clothing image on top of the body thats all.. ( no positioning or resize needed )


Use this as base..





Then with gimp or other program to add layer on.. use either ones..





Of course the clothing image is not perfect and sometimes get transparency problems.. but its fully automated.. the result you see is made by pressing a button.. so with little work with editing manually they could be perfect.. unless i improve my automated method..


Same will work for every pytfall item once i make/render them.. you just past them on top ( but you might need to set some items to specific layer like cloak above all else.. while some goes under others and so on..

I am afk for most of the day again

Maybe I'll be able to cook something up tonight, at least with those images.

[lamoli]

Next..

[DarkTl]

Didn't we decide to split the suits into bits?

We (you and me) did not, at least yet 

You see, too many clothes could not be split into top and bottom even in theory. So there will be top/bottom ones and undivided ones (like in sims  ), which will lead to advanced coding from your side and confusing concept.

Boots and gloves should be made separately, sure.

Maybe stockings as well (I don't think that we have a eq spot for this), shoes most definite.

The problem with underwear and stockings slots is that they are quite situational. When you wear a full plate armor, they don't matter, and you probably can't even wear stockings properly (I think). Also the only way to get many icons for these slots is to render them, they are way too rare without rendering.

Stockings could be a part of boots slot though, when combined with shoes.

[Xela]

I don't care either way until we have enough content or way to create more content on our own at exceptable speed... Both item options (single peace or separate) will work with the current system and they both look great for it.

[Xela]

...

Loaded into Ren'Py using the simplest of screens. If you can put enough time into it to make enough content for a few decent setups, I'll write the code for custom control of color, layer order, alpha channel, hue, brightness, subpixel positioning and etc. to use inside of the game. This is a simple variant using just five lines of code (absolute total, including screens and label declarations) at any time:



===
We'll have to add a lot of new tags for this, since we do not have any tags that can separate clothing from the body, but I don't think that it will be a difficult task either, just add a new extra tag called something like "pure clothing"... we can work out details once we have enough content.

[DarkTl]

Hm. Where are formulas for calculating damage and stuff inside BE?

[Xela]

Hm. Where are formulas for calculating damage and stuff inside BE?

Code: [Select]

        def effects_resolver(self, targets):
            """
            Logical effect of the action. More often than not, it calculates the damage.
            Expects a list or tuple with targets.
            This should return it's results through PytCharacters property called damage so the show_gfx method can be adjusted accordingly.
            But it is this method that writes to the log to be displayed later... (But you can change even this :D)
            """
Mostly here but there could be other references. It's possible for every individual attack to overwrite this so we may be doing that as well sometimes.

[DarkTl]

Yeah, I'm trying to balance it a bit atm.

[DarkTl]

Are you sure it's ok to have two effects_resolver functions (one of them is not global, and used for poison only)?

[Xela]

Are you sure it's ok to have two effects_resolver functions (one of them is not global, and used for poison only)?

Yes, I arrange it that way so each attack could be truly unique and would not have to interfere with general mechanics (as in Poison). None of them are global by the way, function that are bound to classes are called methods, children can access methods of their parents if needs be.

[DarkTl]

How can I access specific fields of equipped weapons during calculations, like type?

Also, how double weapons work at the moment? You still select which one to use, like it used to be?

[Xela]

How can I access specific fields of equipped weapons during calculations, like type?

Code: [Select]

char.eqslots["weapon"].type
char.eqslots["smallweapon"].type

Also, how double weapons work at the moment? You still select which one to use, like it used to be?

If they both have skills as most if not all weapons do, you'll get a choice out of the two skills under attack.