Oh, right. Well that explains a lot. But still, it would be awesome if we'd get to create our own private attributes Sure I can just make them public, but I think it would be much better convention to make them private.

There was a purpose to that previously, but I have been meaning to look at possibly removing that portion. And no, it has nothing to do with _EntitySpecials. It has to do with attributes like _index, _playerinfo, _pointer, etc... that have a property that returns the private attribute. But isn't th...

def __setattr__(self, attr, value): """Find if the attribute is value and sets its value.""" # Is the given attribute private? if attr.startswith('_'): # Get the name of the private attribute name = attr[1:] # Is the attribute a property? if ...

Is it possible to restrict a weapon completely? Like, to prevent a player for picking it up in the first place?

Then, change the encoding or your file to UTF-8 . This worked just fine for me (did you miss this reply ?)! I did change it through notepad's save dialog, but didn't help :/ Edit: Ugh it's all messed up, I did a system restore earlier today and apparently the Source.Python files were affected... No...

L'In20Cible wrote:You can set the encoding you want using the encoding keyword:[python]strings = LangStrings('file', encoding='encoding')[/python]

This did the job, with 'utf-8' Thank you
Edit: Never mind, I failed. It still doesn't work :/

Yay! Good work guys, you're doing an awesome job

L'In20Cible wrote:

Syntax: Select all

my_message = SayText2(my_strings['Test2'])

Should be:

Syntax: Select all

my_message = SayText2(message=my_strings['Test2'])

As for the keywords, pass them to the send method:

Syntax: Select all

my_message.send(index, keyword='hey', keyword2='oh')

Thank you very much. :)

How do I format the translations? I think I'm supposed to use $key inside the translation string, but how exactly do I set the value of the key when I use the translation, for example with SayText2, or inside a menu's option? Edit: I just got an error even without trying to format the translation. t...

Thanks a lot for the help :) I'll take a look at it later on, will try to adapt to the Source.Pyhton's way of doing things. I'm still not too sure about the __new__ vs __init__, to me it makes more sense to use what the base class is using. But I might change it someday, will have to think about it ...

It is true that there are fixed parameters, but I would handle it completely differently anyway. I would only pass in the index, which it seems so far is all you do anyway, then set the gold afterwards. And again, I wouldn't store the language the way you do, but set lang_key to None in __init__ an...

Thanks for your feedback xancara, and good to know it's already being tested widely! It's not our first priority, but we will add a check to make sure there are players on both teams. Also, I must've forgotten the level up message completely, will add it tomorrow as soon as I wake up! Thank you for ...

PlayerEntity's language property is the steam client's language, correct? I did a small quiz (<20 people) and almost everyone voted not to use the language used by steam, but instead let everyone decide their language through menus. What comes to the built-in translation system, I wasn't aware of it...

Hero Wars is a plugin for Source.Python that's designed to replace the outdated EventScripts addon called Warcraft: Source Hero Wars is still in alpha, and there are many bugs to fix as well as features to implement, but the plugin is already playable and thus we're releasing the alpha version. Here...

Alright, good to know they'll be coming eventually Thanks for the answer

This actually sounds really good, better than what I actually requested!
Is it still just an idea, or are you going to implement it already? If so, any eta. on the new update?

"Improving" PlayerEntity PlayerEntity lacks dozens of useful features, or the features are implemented in an unfriendly way for the people using Source.Python to create plugins. There's a lot of inconsistency between some properties, and some functions are completely missing. In my opinion, PlayerE...

Oh right, should've read all the changes, my bad there Well, thanks for the quick response!

You also seem to have removed the self._limit check. I'm not 100% sure about this so correct me if I got it wrong, but wasn't that still required? I figured that limit being zero probably means that the loop should run forever until manually stopped, so removing the check for limit makes it so the r...

Hey, there's a small bug in TickRepeat's reduce() method ../listeners/tick/repeat.py line 224-225: if (self.remaining and self._limit and self.status is TickRepeatStatus.RUNNING): I think it should say something like if (self.remaining <= 0 and self._limit and self.status is TickRepeatSt...