General Discussion

[DarkTl]

And something is to be said about finding icons for all elements and delivery types... images that we use completely outshine unicode that we use.

Done 

[Xela]

Done 

Awesome!

While messing with BR, I may have figured out how to get our inherit from ADVCharacter directly... not 100% certain yet but we may be able to do stuff like:

Code: [Select]

hero "Hello"
$ hero.health += 10
and

Code: [Select]

nami "Hello"
$ nami.health += 10
$ nami.mood_override() # Or whatever it's called...
Right now you gotta type nami.say "Hello" which is a bit inconvenient.

[DarkTl]

I was under impression that it's unsafe to write stuff like $ hero.health += 10, and one should use $ hero.mod("health", 10) to check if health is less than all maxes before applying.

[DarkTl]

While messing with BR, I may have figured out how to get our inherit from ADVCharacter directly...

Funny, I don't see BR on github anymore. It was there just a few days ago.

[Xela]

I was under impression that it's unsafe to write stuff like $ hero.health += 10, and one should use $ hero.mod("health", 10) to check if health is less than all maxes before applying.

No, it's perfectly safe, our character class will redirect it accordingly.

Funny, I don't see BR on github anymore. It was there just a few days ago.

The idea for the repo was to be private, it was for a while and TW was paying for it. We decided to switch to BitBucket which allows private repositories for free. I can add you there if you have an account with them. I just added killer class that inherits from three parent classes so you can do stuff like:

Code: [Select]

$ nika.stat += 10
$ nika.expr("face_expression")
$ nika.set_flag("fucked_the_capitain")
nika "Hi, I am Nika!"
which will really simplify the development in the future. I must be getting better at this sh!t cause I couldn't figure out how to do this in three prior attempts (one in PyTFall included) Prolly the most convenient way imaginable to dev the game!

I've also put my PyTFall's experience with image tags to good use The doll with all the clothing and all the expression is constructed fully automatically from files names and with "exceptions" through JSON file. It's possible to test new shit that was added almost "on the fly" using a special screen and use Ren'Py to recolor any set of clothing (although we're not planning to do that as precolored options that are bound to items are used, could become a thing in the future).

They made a mess of locations, flags and wrote some classes that might have worked in pure python but are not renpy safe, I need to clear that sh!t before story can be developed...

[DarkTl]

Fix BE menu for weapon attacks when you'll have time. I believe scrolling of some kind is the only solution, since we'll have more and more attacks in the dev mode.

[Xela]

Fix BE menu for weapon attacks when you'll have time. I believe scrolling of some kind is the only solution, since we'll have more and more attacks in the dev mode.

Oki, I'll add a viewport there right now.

[Xela]

Oki, I'll add a viewport there right now.

Done, we'll need to come up with proper names at some point, for once, you enter a menu called "attacks" and almost every options ends with "Attack"... it's about the same as adding "Spell" after every magical skill. Also some of the names are too long, menu names should be used to create abbreviations of some kinds.

[DarkTl]

There is a free game on steam, Crush Crush. They have a few curious ideas.

- Characters have many statuses depending on disposition level, from Adversary to Lover. They don't really do much, but it looks neat in their profiles.
- MC can spend time on various hobbies and gain hobbies levels from it. They don't do much, but certain characters like certain hobbies.
- Gifts are separated by types like books, flowers, candies, etc. And characters like not specific gifts, but specific types of gifts.

[Xela]

Not bad, but this will overload players brain in pytfall

[DarkTl]

Gifts types make gifting simpler. Once you know what the character likes, you don't need to guess what to buy.

[DarkTl]

Wait a sec...

First of all, after

call screen hidden_area(areas={...})

_result variable does not exist, unlike normal matrix. So I pretty much cannot know what the screen returns.

Secondly, I changed buttons alpha to 1.0 to test how matrix works. And with

call screen hidden_area(areas={"fish_0": ((100, 100), (.1, .5)), "fish_1": ((100, 100), (.1, .5)), "fish_2": ((100, 100), (.1, .5)), "fish_3": ((100, 100), (.1, .5)), "fish_4": ((100, 100), (.1, .5)), "fish_5": ((100, 100), (.1, .5)), "fish_6": ((100, 100), (.1, .5)), "fish_7": ((100, 100), (.1, .5)), "fish_8": ((100, 100), (.1, .5)), "fish_9": ((100, 100), (.1, .5))})

all ten areas are located in top left corner, with zero randomness.

The random matrix is not operational 

[Xela]

I'll check it out tomorrow evening (gonna be traveling in morning/afternoon). Push your testcases so I can take a look.

[DarkTl]

I dunno why _return doesn't work. But I don't really see any attempts to randomly place hidden buttons, so the lack of randomness is not surprising.

[Xela]

I am pulling your testcase off the server right now.