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?

Oh, you right. I just checked the code. Well, in that case it would be quite easy to get rid of this problem. We could also update our take_damage() method so that it takes an additional keyword. E.g. try_trampoline=True. Our take_damage() method would then look like this. def take_damage( self,...

To call the original function within a hook, we have added a call_trampoline() method. Though, that will probably not help in this particular case, because we are hooking OnTakeDamage, but calling TakeDamage. : /

Yeah, but they are not included in the latest release.

satoon101 wrote:Those 2 classes are not included in the latest release.

If you are getting the ImportError, you probably didn't update your Python files.

Actually it's working fine for me. On which game did you test that and did you update your SP files? from players.entity import PlayerEntity from players.helpers import index_from_userid from events import Event @Event def player_jump(event): userid = event.get_int('userid') ...

That's not the full traceback. However, you have to call super().__init__().