This will possibly get moved to another module at some point, but you can always use the PlayerTeams dictionary from filters.players to get player teams for the current game: from filters.players import PlayerTeams for team in PlayerTeams: print(team + ': %s' % PlayerTeams[team].team)...

The only module, I believe, that uses that file, is the filters.players module. This is how it reads the data:[python]_game_teams = ConfigObj( DATA_PATH.joinpath('players', 'teams', GAME_NAME + '.ini'), unrepr=True)[/python]Note that you will need to import ConfigObj, DATA_PATH, and GAME_NAME if you...

The plugin is still an alpha, so when we update, we occasionally break scripts. I have not updated this script to work for the newest build. I will try to do this sometime soon. Also, the "Source" module isn't really "missing". We removed that namespace to adjust to our new naming convention. Satoon

I am fairly certain that, while they used the CS:GO engine, they more than likely modified it severely. I would doubt that SP works for that game.

Satoon

Well, I am having issues building on OrangeBox now... I was able to build it on Windows earlier today, but now I cannot seem to even get that to work. I am also getting an error building OrangeBox on Linux. Due to these issues, I will not be posting an OrangeBox build tonight. However, there is a ne...

Indeed, the two do not work hand-in-hand with each other. In fact, Source.Python started off as EventScripts3, a complete re-write of the plugin. In its current state, there are a few things you can already do with SP. It is still in Alpha, so there are still lots of things you cannot do. A few mont...

There is no ETA, unfortunately. All of the C++ programmers are very busy with other projects and their lives. That is the only answer I can really give at the moment, sorry. As far as the naming scheme, we have already removed the "Source" namespace, so now importing from the C++ side is w...

From what I remember, BF3 (and most likely BF4) aren't exactly mod friendly. Even having your own server, there isn't much you can do with it other than just choose map rotations. I'm not sure how much, or even if you can, truly create a server side mod for it, unfortunately. I could be wrong, and p...

Not sure how well this will translate, but we have not really talked about adding other sections for different languages. We are still too early in development, in my mind, to worry about doing such. We will discuss this, though, and let you know our plan for the future when we have one. Thank you f...

Technically, we "should" be using: # Source.Python Imports # Engine_C from engine_c import get_engine_interface # Entity_C from entity_c import CEdict # Event_C from event_c import CGameEventListener We are discussing this internally to find the best solution and how to implement it. Thank...

It does make sense. Everything is in the namespace "Source". You import entity_c, engine_c, events_c, etc... from the overall Source package. They are their own separate modules, but you must import them from the main namespace and not directly. I think it works better this way and is more clear abo...

I likey this :) I will get right to work on modifying the current API to fit these changes. I prefer Source, personally, to sp_C. We decided to go that route in the very beginning, and it still seems to work fine. It is definitely a collection of packages/modules much like the Python API is designed...

There's no reason to go with Notepad++, the IDLE text editor that comes with the official python is more than enough for creating python scripts. I have to disagree with this. Using a proper text editor is a much better way to go. I personally use Notepad2, though I occasionally use Notepad++ and n...

It always looked fine on my Droid. I would suggest getting a better phone.

Ok, we decided, since we will more than likely never use the old version, to create an old-branch for the old version and merge the newest changes from source-python-2 into the default branch. We also closed the sp2 branch itself, since there is no need to have it anymore.

Satoon

Eventually, we will merge source-python-2 over to default. I'm not sure where in the development process that will happen, though. We could go ahead and do it now, but there are things not available yet on SP2 that the Python API is being updated for. It helps to be able to test using the default br...

Just wanted to let everyone know of 2 major changes that were just committed to the repository. First, the listeners package, which was created with the thinking that other "listeners" would at some point be added to the package, was renamed to "tick". So, the following file changes were made: &sdot...

Another update for everyone. Since we are really liking the changes to the core design, all recent updates for the plugin have been on the source-python-2 branch. So, if you have been keeping track of the repository online, and haven't noticed any changes, you should be aware that we have still been...

Well, I see you have been on since, but maybe you did not notice back then. Our site went down in November, and we were unable to recover much of what had been lost. The last backup for the site was from September, unfortunately. I would imagine that you uploaded your addon between the last backup a...

Indeed. Happy Birthday, vingt!!!

Satoon