I doubt parsing the output of report_entities will be faster than using EntityIter(). You could even skip EntityIter() and use EntityGenerator() directly. As you can see it doesn't do very much if you just want to iterate over all entities. But why do you think that it might be too slow? Did you exp...

This is also working fine.^^

Also, your code wont load due to ; after return which is an invalid syntax. No, a semicolon is valid in Python. It allows you to use multiple statements within the same row.[PYTHON]>>> def f(x): print(x); x += 5; return x; >>> f(5) 5 10[/PYTHON]Though, you usually don't use that in Python.

No, I meant the cstrike_pak_dir.vpk in your cstrike folder on your server. Though, the client has probably the same models.

You should be able to use every model you want. The built-in models are packed in *.vpk files in your cstrike folder. You can use GCFScape to open the cstrike_pak_dir.vpk, which lists the models, materials, etc.

I could imagine that the info_target entity implements its own Use() method. So, your hook only gets called when you press +USE on an info_target entity. Try hooking it on prop_physics_override.

The callback gets called everytime a ConVar changes and it doesn't need the NOTIFY flag. But yes, if it has this flag, you would need to hook FireEvent.

We haven't added that to the wiki yet. But here is the source code: https://github.com/Source-Python-Dev-Team/Source.Python/blob/master/addons/source-python/packages/source-python/memory/__init__.py#L77

I can add that to the wiki today.

I would like to take this chance to show another feature of SP, which is already available since a long time. Though, we have improved this feature a few weeks ago. You can create functions, which have an address in memory, so you can pass them to any function you want. This means that you can creat...

Well, it does not allow you to use operators.

Check the docs: https://docs.python.org/3.4/library/ast.html#ast.literal_eval

Could you please post the error?

Yes, you could do that, but what's the point? You can easily decompile it back to a *.py file. Moreover, we want to encourage people to make their code public.

plane.normal returns a Vector object.

Sorry for the short answers. I'm currently in my phone.

You can already get the plane from a trace. https://github.com/Source-Python-Dev-Team/Source.Python/blob/bd62d8a4118dce438c0a78f264cb4a2d0e4060b8/src/core/modules/engines/engines_wrap_python.cpp#L937

my_trace.plane.normal

I guess you currently only have two points. The player's location and the impact location (which is on the wall). But I think you need another point on the wall, because you can't calculate the angle to a single point.

Yes, it's possible, but requires the memory module. I guess we will add that functionality at some point, so you can just do player.name = <new name>: import memory from memory import Convention from memory import DataType from memory.hooks import PreHook from engines.server import engine_server fro...

I just read about properties and found a quote of the zen of python, which is obviously a point for you.

There should be one-- and preferably only one --obvious way to do it.

And since we are actually following many proposals, we should think about following that as well.

We decided that we want to have properties, because we think they are more handy. Do you have any sources for the "usually" in your edit? I have never seen a proposal for that. Though, I should also mention that I didn't search for it. If you are looking for other projects, which are using get_*/set...

The error tells you which types you can pass to the constructor. However, you don't need the pointer thing. Just return trace.get_entity_index().

No, L'In20Cible is right. Here is the proof. https://github.com/Source-Python-Dev-Team/Source.Python/blob/master/src/core/modules/memory/memory_hooks.cpp#L124

If you would just return True or False in a PreHook, what would be the return value for the caller?