General Discussion

[Xela]

"_day_countdown_interactions_blowoff" flag #175

Can you clarify? I went over the entire code chain and it seems like it should be working for all characters. Prolly the only thing that works that way.

Maybe it's how that flag is applied in interactions? If so, I need to know where, but it should work as a counter for all chars.

Yeah, I think this is fixed, flag wasn't activating for interactions, only for gms.

[DarkTl]

Something that bothers me for awhile is how in many games you can choose how characters address you. Especially enslaved ones. If we gonna have such stuff, it should be considered right now, not when we'll have much more lines to rebuild.

I mean, I personally dislike the word "Master", and would prefer chars to just use hero.name. But I bet there are people who'd love chars to address them as Master.

If you have different ideas, lets hear them. I am just putting my own thoughts in the table. It's not "similar" to free characters, they should respond normally and sensibly.

Right, ~dere characters responding normally and sensibly... 
Archetypes themselves are not normal at all by rl standards. Most of them at least. It's not a problem though, just saying.
 

You made a good case on encountering slaves in the city, I just don't know how sensible that that from game play perspective. Concept wise it makes sense, but "concept wise" it doesn't make any sense that you only meet females and only max three at a time either Compromises need to be made until we are ready to improve stuff.

I personally think it's too easy to find characters atm. The city is full of unemployed chars, it's unrealistic.

[DarkTl]

Yeah, I think this is fixed, flag wasn't activating for interactions, only for gms.

Yeap, it works now, didn't worked before.

[Xela]

The city is full of unemployed chars, it's unrealistic.

This is something we'll fix, maybe even for beta.

====>>>

I mean, I personally dislike the word "Master", and would prefer chars to just use hero.name. But I bet there are people who'd love chars to address them as Master.

Do we do this on per char basis? Or globally (on hero.namespace).

[DarkTl]

Per char, I suppose. Hero.name could be a dict of [character : name for hero]. Or it will be a new thing like char.name_for_hero.

[Xela]

Per char, I suppose. Hero.name could be a dict of [character : name for hero]. Or it will be a new thing like char.name_for_hero.

Nah, that is never useful when we're working with objects. Ok, I'll see what we can do.

[Xela]

Nah, that is never useful when we're working with objects. Ok, I'll see what we can do.

While you're at it, would it make sense to come up with pronouns? Like "his"/"hers"? Or is this an overkill at this dev stage?

[Xela]

Ok, it's done:

Code: [Select]

        # Properties:
        @property
        def mc_ref(self):
            if self._mc_ref is None:
                if self.status == "slave":
                    return "Master"
                else:
                    return hero.name
            else:
                return self._mc_ref
might even be useful for free chars, if one of them decides to give MC some weird nickname You just:

char.say "What's up [char.mc_ref]?"

and it should work. We'll add setting it later to the interactions menu as well.

[Xela]

Gonna take a look at SE, been slacking off in that department and there should be some good time for it today.

[DarkTl]

While you're at it, would it make sense to come up with pronouns? Like "his"/"hers"? Or is this an overkill at this dev stage?

Sure, go ahead. I'll replace pronouns with keywords. He/She, His/Her. I suppose cases like herself or hers are just keyword+"self" or "s".

[Xela]

Sure, go ahead. I'll replace pronouns with keywords. He/She, His/Her. I suppose cases like herself or hers are just keyword+"self" or "s".

There you go:

Code: [Select]

        # Properties:
        @property
        def mc_ref(self):
            if self._mc_ref is None:
                if self.status == "slave":
                    return "Master"
                else:
                    return hero.name
            else:
                return self._mc_ref
               
        @property
        def p(self):
            # Subject pronoun (he/she/it): (prolly most used so we don't call it 'sp'):
            if self.gender == "female":
                return "she"
            elif self.gender == "male":
                return "he"
            else:
                return "it"
               
        @property
        def pC(self):
            # Subject pronoun (he/she/it) capitalized:
            return self.p.capitalize()
               
        @property
        def op(self):
            # Object pronoun (him, her, it):
            if self.gender == "female":
                return "her"
            elif self.gender == "male":
                return "him"
            else:
                return "it"
               
        @property
        def opC(self):
            # Object pronoun (him, her, it) capitalized:
            return self.op.capitalize()
           
        @property
        def pp(self):
            # Possessive pronoun (his, hers, its):
            # This may 'gramatically' incorrect, cause things (it) cannot possess/own anything but knowing PyTFall :D
            if self.gender == "female":
                return "hers"
            elif self.gender == "male":
                return "his"
            else:
                return "its"
               
        @property
        def ppC(self):
            # Possessive pronoun (his, hers, its) capitalized::
            return self.pp.capitalize()
to use:

"[hero.pC] ran away screaming as [char.op] staff menacingly emitted mana ..."

We also need to resolve the same for names, gonna look into that as well, I think Thewles wrote a good function for it.

[DarkTl]

Jeez, can't they be more memorable? Hero.hisher or hero.heshe would be better 

[Xela]

Jeez, can't they be more memorable? Hero.hisher or hero.heshe would be better 

Feel free to change them, chances are that you'll be the one working with them the most. Names are simpler, you basically just add an apostrophe in almost all cases so we don't need it.

But honestly... is there a better way to memorize names of the pronouns? 

Or, and there is also "him" and "his".

? It's there, you need to scroll, you cannot see the whole code, it's in a viewport.

[DarkTl]

We'll see. If I often will have to open the code and look how needed functions are named, I'll rename them.

Btw even if there will be male chars at some point, they should use completely different lines in many cases. I definitely don't want males to use some sleazy lines made for females 

[Xela]

Btw even if there will be male chars at some point, they should use completely different lines in many cases. I definitely don't want males to use some sleazy lines made for females 

Fair enough, we decided not to bother with that. This functionality might still be useful + preemptive if someone comes along who might be willing to work on it or we decide to come up with a simplified iterations version for other genders in some very distant future.