The most plugins on this forum are probably out-dated due to the development. Your script doesn't load, because an error was raised. To show the error, you have to edit the LOG_SETTINGS.

Yes, sp load <script> is correct. Could you show us your script?

You should also go to ../cfg/source-python/core_settings.ini and adapt LOG_SETTINGS.

Your code should run without any problems. I guess you are running an out-dated version of SP.

To enable better debugging take a look at cfg\source-python\core_settings.ini.

After spending several hours on this I finally found the issue(s). This error already existed since I replaced DynDetours with DynamicHooks. But it wasn't just one error, but three: 1. Somehow AsmJit didn't get linked properly if we compiled for CS:GO. 2. There was an issue in the SDK for CS:GO that...

That's a linking error, but I can't tell you more. I will have to test this out on my own. Did you compile in debug or release mode?

Do you run the latest revision of our repository or the last official build?

Should be fixed now.

Yep, I broke it yesterday.
I will try to fix it today.

You could write a plugin that emulates ES Shell syntax and functions, but I doubt that anyone will ever do that, because the effort wouldn't be worth it.

Does it crash without SP being loaded? If yes, I can't really help you. Otherwise we still have to narrow it down to some functions we can check.

They may seem to work properly, but please make sure that they don't cause the crashes by disabling them for now.

Due to that line I think it has something to do with say commands, but I can't tell you more.Try to reproduce the crash and then post the code.

CS:S and CS:GO are currently supported, but it should theoretically work on every other game that relies on the OrangeBox engine. But you probably have to add some data to the Python side (like teams or weapons).

Regarding the error: you have to change all DATA_PATH occurences to SP_DATA_PATH. Take a look at this revision. I'm currenctly not sure if it's included in the latest build.

Just add "sp load <your script>" to the autoexec.cfg.

CEngineServer is the class object, but you need an instance of it.

Yeah, everyone is busy, lost the interest in this project or is unmotivated to continue the development.

I have never seen player_spawn firing 3 times.

It actually does that. The first time a player spawns he isn't in our set. So, we add him to the set and return. After that everything after "# Your code here..." will be executed.

Yep, but remember that es_userteam is a variable defined by EventScripts. This might be more effective: from events import Event players = set() @Event def player_spawn(ev): userid = ev.get_int('userid') if userid not in players: players.add(userid) return # Your code here... @Event def player_disco...