Do you run Python on the same machine as the server you tested on? If so, what version?

iPlayer wrote:Edit: fixed my misunderstanding of how convar querying works

Not your fault, the docstring of that method is very mis-leading. I will try to update it soon.

→ https://github.com/Source-Python-Dev-Te ... issues/151

However, print works just fine on my side.

Any error into the ../logs/source-python/* files?

At this point, I think you want to remove them all no matter what: from listeners import OnEntityCreated @OnEntityCreated def on_entity_created(base_entity): if base_entity.classname != 'env_screenoverlay': return base_entity.remove() Since you seem to have trouble installing...

Painkiller wrote:Hello, that does not work.

You are doing something wrong. I tested it and it work just fine.

Why not check hammerid instead? Because this listener is called when it is allocated and added to the global list while a lot of stuff is done/linked in the post constructor . Which is the main reason why we manually link m_pNetworkable on the edict_t instance before calling the registered callback...

Okay, I tested and it seems that on HL2:DM, OnServerActivate is called AFTER the entities has been created so the entity is never marked for deletion. Since this is for a single map, and that we know the index, I guess we can safely do the following: from engines.server import global_vars from liste...

What is the map in question?

BaseEntity is a wrapper around CBaseEntity that get exported from the c++ side while Entity is an extension class that inherit from it and extend it adding some functionalities. A BaseEntity instance can either be a server-side entity (perform various task on the server but never sent to clients) o...

This remove only those created by the map.

from entities import BaseEntityGenerator from entities.entity import BaseEntity from entities.helpers import baseentity_from_edict from listeners import OnEntityCreated from listeners import OnServerActivate from memory import get_object_pointer from memory import make_object _marked_for_deletion =...

→ https://github.com/Source-Python-Dev-Team/Source.Python/commit/324c52cfc4483883a8146a38c3a49394a59e8410 EDIT: Okay, made more testing and this doesn't fix everything. Setting any fields will no longer cause a crash. However, getting string will cause one - I was testing with SayText2.chat so I did...

Fixed in 2315e41, thank you for reporting!

Does that work with disconnecting clients? E.g. can't there be a case when a player has already disconnected, but their entity has yet to be removed or something? Other words, can I safely do this: player.delay(5.0, player.spawn) ? (omitting the "respawning a respawned player" iss...

By setting m_bClientSideAnimation to False, you tell the clients to stop predicting animations, so the fact it does disable that effect tell us it is entirely handled client-side and there is nothing we can do from a server-side plugin. I'm pretty sure there will be enough complains for them to add ...

→ https://github.com/Source-Python-Dev-Te ... 93a29f64b3

For convenience, we could add an Entity.delay method that wrap the Delay class and internally cancel on entity deletion.

Like I explained here about delaying spawn, same concept apply for delaying deletion. ⋅ Instead of having a function that call the spawn method on the passed player, you could simply delay that method to be called: Delay(cvars['autorespawn_delay'].get_int(), player.spaw...