It always looked fine on my Droid. I would suggest getting a better phone.

Ok, we decided, since we will more than likely never use the old version, to create an old-branch for the old version and merge the newest changes from source-python-2 into the default branch. We also closed the sp2 branch itself, since there is no need to have it anymore.

Satoon

Eventually, we will merge source-python-2 over to default. I'm not sure where in the development process that will happen, though. We could go ahead and do it now, but there are things not available yet on SP2 that the Python API is being updated for. It helps to be able to test using the default br...

Just wanted to let everyone know of 2 major changes that were just committed to the repository. First, the listeners package, which was created with the thinking that other "listeners" would at some point be added to the package, was renamed to "tick". So, the following file changes were made: &sdot...

Another update for everyone. Since we are really liking the changes to the core design, all recent updates for the plugin have been on the source-python-2 branch. So, if you have been keeping track of the repository online, and haven't noticed any changes, you should be aware that we have still been...

Well, I see you have been on since, but maybe you did not notice back then. Our site went down in November, and we were unable to recover much of what had been lost. The last backup for the site was from September, unfortunately. I would imagine that you uploaded your addon between the last backup a...

Indeed. Happy Birthday, vingt!!!

Satoon

I removed the download because that version causes crashing when using the messaging system, as you have seen in your testing. Due to Valve updating to use the new protobuf system in CS:GO, the old UserMessage system got removed completely for that version of the engine. Again, as I posted earlier, ...

The message system has gotten a major overhaul, not only on the Python side, but on the C++ side as well (due to the protobuf system). So, if this is for CS:GO, you will need to compile the newest version yourself in order to send messages, then use the most up-to-date Python API. Info on the messag...

Not trying to derail this thread, but I am slightly confused by your statement. Overall, the Python-side API will still function as-is. It is just the links between the API and the C++ side (what we refer to as Source) are going to be a lot more consistent. Obviously, you can choose to use the Sourc...

We do plan on implementing KeyValues to parse .res files, but as Logifl3x said, there really is no need for es_key_ commands, as Python has other ways to handle these types of things.

Satoon

I would've posted the error earlier but there isn't easy copying and pasting. Sorry for double post, but I just noticed this in your post. Yes, using the console doesn't make it easy to copy paste. We do plan on including a logging system at some point that will make this much easier, but I am not ...

Yeah, it is definitely due to you passing a float value instead of an integer. Notice in the error, this section: Boost.Python.ArgumentError: Python argument types in edict_t.SetPropInt(edict_t, str, float) did not match C++ signature: SetPropInt(struct edict_t *, char const * szFullPath, int propVa...

As they said, it would be much easier to help you if we could see the code/error instead of just guessing at what your issue could possibly be. The only thing I could think it would be is that the health property uses an integer: # From ../_libs/_data/properties/player/csgo.ini [health] prop = "...

I'm not 100% sure what you are asking, but it seems to me you want to set the health of the "attacker" on player_death. If that is right: from events import Event from players.entity import PlayerEntity from players.helpers import index_from_userid @Event def player_death(GameEvent)...

Unfortunately, since the site went down, we have not really gotten the Wiki back up, yet. "health" is just an attribute of the PlayerEntity object. You get it by simply calling player.health and not "setting" player.health: # Get player's current health health = player.health...

Sorry, just realized this is an issue with the current download. Unfortunately, until we can fix our Linux build issues, we cannot release a new build. There are many things in the newest _libs that utilize functionality in more recent builds, which makes me hesitant to release the old build with th...

Update your _libs folder. That error was fixed on Dec 17th.

Satoon

You mean loop through all players on a specific team and setting their health to 100? If so: from filters.players import PlayerIter # This would be if you are doing this for CTs # We use 'player' as the return_type to return a PlayerEntity instance ct_players = PlayerIter(['ct', ...

Thank you both. I will add those when I get home later today.

*Edit: added, thanks again.

Satoon