Actually, having thought more about my previous post, I should also state that if you are reporting crashes/bugs using the current repo version, you should post them on the issues list:
https://github.com/Source-Python-Dev-Team/Source.Python/issues

Satoon

Well, unfortunately, using a "mixed" version is obviously going to have its issues. I don't think we can support a mixed version. If you are going to report errors or crashes, please use the repo version, as that is what we are working off of and would need to fix. Having said that, you stated that ...

Are you using the most up-to-date version of everything from the repository or are you using the latest download version? I actually get an error on index_from_userid with the latest repo version, which would stop the code prior to even executing PlayerEntity.

Satoon

Just so you know, we already include ConfigObj with SP. I find it much easier to use to parse ini files than configparser. We use it in the translations package within the Python API.

Satoon

I have informed Monday of this, and he said he would take care of it when he gets the chance. I have not noticed any actual issues with it other than the error posting at the top of every page. I do not use Firefox, though, so, maybe that is why you have had the posting issue?

Satoon

I am waiting until all the internal changes have been made before I start fixing the Python API. That shouldn't take too much longer, but these issues will be resolved in due time. Out of curiosity, are you certain index_from_userid isn't the cause of the crash? I just need to make sure when I start...

Delete your entire ../addons/source-python/packages/source-python/ directory and reupload all current files from the repository from that directory.

Satoon

First off, sorry for the lull in development, everyone. We are now back and working on adding in more functionality, along with a few other "internal" major changes (coming soon). Having said that, I have finally finished developing the plugins package that was requested a few months back....

For kicking: http://www.sourcepython.com/showwiki.php?title=Wiki:CEngineServer#server_command from engine_c import CEngineServer CEngineServer.server_command('kickid %s %s' % (userid, reason)) For SayText2 (chat area): http://www.sourcepython.com/showwiki.php?title=Wiki:messa...

We changed the format to get SendProp values from: <CEdict>.get_prop('<prop name>').get_<type>() to: <CEdict>.get_prop_<type>('<prop name>') We just have not updated the Wiki to show those changes. Also, playerinfo is not a SendProp name. You can get a player's CPlayerInfo instance by instantiating ...

After you have started your server once, the file ../cfg/source-python/core_settings.ini should be created. Edit the file to your liking. The Logging section deals with debugging.

Satoon

I tend to agree with arawra on this. Are there any specific examples that you wish to have that ability for? Obviously, TickDelays has that capability, because you are calling a specific function with specific arguments/keywords after the specified time. I really don't see the point in doing that in...

Sorry, forgot to mention, but the data for the property values needs to be updated. I keep forgetting to do that, so I will do that right now.

Satoon

As Ayuto states, the name change was fixed already. Though, I am not sure why you are trying to import a method which is already included in PlayerEntity. You cannot import a method, anyway, only global objects in a module. If you wish to use get_ammo, just use it as it is designed: from players.ent...

Yeah, I got a couple as well, from a different (related) address. I went ahead and banned a range instead of the specific address. If anyone receives any more, let us know (might have to go one step further on the range).

Satoon

Awesome! Thank you Omega.

We have just moved the repository over to GitHub. We are now using git instead of Mercurial, as well. We will update the wiki as to these changes in due time. We have also posted a new build. The navigation bar has been updated for the correct Downloads and Source Code, as well as a new Issues List ...

I completely understand about not having many examples. However, we are still in the Alpha stage of development, and the little time that most of us have to work on the plugin, we choose to spend most of working on implementing code and not updating the wiki. It isn't like the EventScripts' wiki was...

I have started work on this locally. I will probably make these changes when we move to GitHub. Adding/removing as many files as we are going to be doing (moving adds new ones and deletes old ones) always causes us to need multiple commits/pushes. I'm not sure if this is a limitation of Mercurial, T...

I imagine that the biggest part of your issue with documentation is that our syntax highlighter is currently broken. Without proper examples, it can be difficult to know how to use certain functionality. We are working on that, but I am not sure when it will be fixed. Also, Source.Python is not bein...