A new release is available! 87 commits have been made since the last release. Changelog: https://github.com/Source-Python-Dev-Team/Source.Python/compare/ff92726...master Download: https://github.com/Source-Python-Dev-Team/Source.Python/releases/tag/d9d9593

Great idea!

Maybe today or tomorrow.

Do have any other server plugins loaded?

In the next release you will be able to execute the kill command. https://github.com/Source-Python-Dev-Team/Source.Python/commit/34d0d4aed50f84d4e6b178639e94faa9f6fd0552

Can you provide a test script that reproduces the crashes?

You should also mention that you have updated an interface. So, even if we add the data it might not work.

I have now taken a look at CS:GO and found this signature. 55 8B EC 83 EC 28 56 57 8B F9 F3 0F 11 4D FC However, this is a special function as it uses a custom calling convention on Windows. The "this" pointer is passed through the ecx register (that's usual for a Windows thiscall), but t...

Rather than creating regular expressions you could simply pass the commands and required arguments seperately. I would think about something like this. That seems to be more pythonic and allows more flexibility. @Command('sp_ignite', Argument('player', validator=player_filter...

I really like the idea of this auth module. Our current implementation allows people to create/load different auth providers, so they can use e.g. EventScripts' or Sourcemods auth files (though, we haven't added parsers for these files yet). But actually I'm not really sure if that's the way we shou...

Oh, yeah. We haven't added that to CS:GO. Sorry.

I would also like to mention that we have a method to cause damage. player.damage(...)

That won't work. Imagine you have 2 CT players and 1 T player and now the T player leaves. Then the T team has no players and "killserver" should be executed, but your code won't do that.

I didn't thought about that in my previous answer to your code.

Yeah, but you forgot to exclude unassigned players and spectators.

Ahh, okay. Yes, the event player_disconnect is fired when a player is about to disconnect and not when he already disconnected. The reason behind that is simple: you can still access the player's attributes, functions, etc. You can use this to work around that problem. from events import Event from ...

What exactly is the problem?

We have posted a new release again! The changelog can be found here: https://github.com/Source-Python-Dev-Team/Source.Python/compare/2eb3a29...master As always, the download can be found in the release section on the GitHub page: https://github.com/Source-Python-Dev-Team/Source.Python/releases

I guess with "property" you mean "properly". But can you describe your problem a little bit better? Do you get errors?

Maybe someone volunteers to update this script. I could do it, but I don't have time today.

This addon was made for a very early version of Source.Python and doesn't work with the latest release. It requires some updates to work again.

Just tested both cases (changelevel and automatic map end) and I wasn't able to reproduce the crash on my Linux server. Do you have any other server plugins installed?