Is there any ETA on when the other offsets will be updated? I know that clan tag offset changes literally all the time, because of small updates from Valve, but some of the others rarely change and it would be great if those could be updated too. I can see that the approach right now is update-when...

It's time for another development status update! :smile: ⋅ Fixes: ⋅ Additions: ⋅  Added insert_server_command() and insert_command_string(). ⋅ Removals: ⋅ Changes: ⋅  Buildbot and "sp update" changes. ⋅  Use FIFO method ...

I just updated most of the data. Though, there are still some updates missing (marked as TODO):
https://github.com/Source-Python-Dev-Te ... 83834972b5

As for give_named_item, it wasn't just a data update. So, I recommend to run sp update.

This is partially true. I just need to do one click and a new build is created and published.

No problem! But I'm just the maintainer of SPE. your-name-here is the creator.

Regarding the offsets:
Please take a look at your Linux server. I gave you the updated offsets a few weeks ago.

I guess there are missing 32 bit libraries on your system. GCC 7 might also cause problems. Try 4.8 -- that's also what our buildbot uses:
http://wiki.sourcepython.com/contributi ... html#linux

However, I will be back home tomorrow. Then I will create a new release.

I don't quite understand what you mean. Making entities visible/invisible has nothing to do with colliding.

I guess it's the same reason why triggers aren't shown. This code allows to make triggers visible:


If you adapt it, you should also be able to make other entities visible.

Have you tried returning True instead of False?

Our buildbot will be shut down by the end of this month. Thus, we had to make some changes to our Builds page and sp update server command. The Builds page has been replaced by a new Downloads page. On this page you can now always download the latest Source.Python version. Important: As you can see ...

It only shows how to setup the PassServerEntityFilter hook. Of course, there is more to do, but I haven't looked through the whole SM code. Just wanted to give you a hint/place to start.

Sorry, I totaly forgot about it. Here is the basic structure: import memory from memory import Convention from memory import DataType from memory.hooks import PreHook from entities.helpers import baseentity_from_pointer server = memory.find_binary('server') PassServerEntityFilter = s...

Then it's probably a read-only property.

See example #2:
viewtopic.php?f=5&t=567

set_property_X is just a wrapper for set_network_property_X and set_datamap_property_X. If it's a network property it will use the first method, else the latter.

It's time for another development status update! :smile: ⋅ Fixes: ⋅  Fixed issue #261. ⋅  Fixed issue #253. ⋅  Fixed issue #157. ⋅  Fixed issue #233. ⋅ Additions: ⋅  Added SmokeMaterial keyvalue to the CSmokeStack data. ⋅&nbs...

Could you please try this?:

decompile wrote:Is there currently a way to restrict the value of a ConVar to a specific value type?

No, not yet.

I would simply use the build_callback instead of creating individual menus for every player. Then you have one menu instance for all players, but they will be rebuilt for every player before they are sent/refreshed.