Sounds good. Post either here or in the Module/Package Submissions forum when you have something working.

Thanks,
Satoon

Well, ESS will not be implemented, so those addons are completely out of the question. As far as Python-wise, changes to syntax will definitely be needed. Our API will be completely different than the ESP. So, many changes can (and will) be extensive.

Satoon

Welcome, pil. I would like to add that we also hope to have some seriously well done documentation on what all is available for scripters to use. We will attempt to add as much to that as possible. However, we will also need the help of other forum members to help us keep up with all of the document...

We will have to discuss this further internally at a later time. If you wish to work on an API for this on your own, and submit it, we have no issue with that. That would also help us get a better feel for whether or not it is something we would wish to implement. If we decide one way or the other i...

Good point about no native method, don't know why I didn't remember that. I already figured out how to do this without using __del__, and those changes are forthcoming. I had been working on a few other things, but I will hold of on those and update this right now.

Satoon

Updated main post with some more points.

Satoon

Updated main post. If anything is missing (which I am sure there is plenty missing), please feel free to mention it here.

Satoon

He has not pushed this change yet. Wait until his next commit is pushed and you should be good to go.

Satoon

Ok, since everyone else seems like they want this change, I'll work on updating the current version with these changes. I'll update the main post above when I get the chance. To be consistent, CamelCase will be used in the future.

Satoon

The "name" of the event is player_say. Using @event prior to a function will cause that function to be registered for the event with the same name as it. Therefor, when using: from events.decorator import event @event def player_say(game_event): pass We are registering the "pl...

This doesn't seem as big a deal right now as you are trying to lead us to believe. If the object actually isn't removed from memory, that really isn't the fault of using __del__ to unregister for an event. If we don't call __del__, the object will still remain in memory anyway, and the event will no...

Yeah, you register it the same way as the example i posted above.

Satoon

Well, the addon system is still a work in progress. The error is being encountered, but no message is being sent. I'll look into why that is in a few. The error you are getting is that you are missing : at the end of your load and unload functions. Also, you might take a look again at this post: htt...

I agree, and I "hope" they finally get the "path" module updated to support Python3.3.

Satoon

The "engines" folder houses all of the Python3.3 included modules. The "bin" folder houses the "core.dll" file. The "_libs" folder is where the API is going to be housed (currently already has addons and events base modules). The __pycache__ is a folder that Python creates when a Python module withi...

Commands to load/unload/reload are: ⋅ sp_load <scriptname> ⋅ sp_unload <scriptname> ⋅ sp_reload <scriptname> Using sp_load without any scriptname will print out all addons that Source.Python has loaded on the server. The path to a script should be ../addons/source-pytho...

The script that imports es is broken. es is not a module within Source.Python. All of the events are definitely still available. Whenever the Engine itself calls an event, Source.Python calls the function within ../addons/source-python/sp.py called "event_fire". The API then uses this to c...

This would have been an option when installing CMake. I'll add that to my quick tutorial.

Satoon

I did not have a second client when I tested, so that is why I did not think it worked. Now that my backup account received the Beta, I can test locally with 2 clients. It still shows up in the server's console with the correct reason, but shows other clients the new one. However, this behavior is v...

It looks like Omega has been working on a Wiki page for this, but it isn't finished yet. Here is a quick guide (with less info than the Wiki will end up having) that will hopefully get you up and going. If you have questions, feel free to ask: Install: ⋅  TortoiseHG ⋅  Microsoft ...