⋅  weapon_knife ⋅  weapon_knifegg ⋅  weapon_incgrenade ⋅  weapon_c4 ⋅  weapon_p228 ⋅  weapon_glock ⋅  weapon_scout ⋅  weapon_xm1014 ⋅  weapon_mac10 ⋅  weapon_aug ⋅  weapon_elite ⋅ ...

I like #human more than !bot. Maybe we should change the # to a & or something since it is a python comment char? Everything else looks spiffy!

satoon101 wrote:Not sure if you made more changes, but it seems to work correctly now. Thank you

The change I made was in a css file, a browsers love to cache those things.. :P

Also.. make sure you are running the latest build before posting!

Tuck wrote:When would this be added, i'm working on a project for the cs:go release and would love the feature :P

We will get it working in a timely fashion.. I can't give you an ETA or anything, we have a lot on our to-do list!

Create a channel on Quakenet (IRC network used by most gamers) and provide a link on this page to the Quakenet webchat ( http://webchat.quakenet.org/ ). There is no wait or need for a request to create a channel there, you only need to join the channel and request Q to keep it. We have a registered...

The python syntax Highlighter looks broken, I have twice the amounts of lines in highlighted code: ex: http://www.sourcepython.com/forums/showthread.php?76-Player-index-userid&p=348&viewfull=1#post348 Is the issue fixed? I edited one of the .css files and it seems to appear on my end?

Just a heads up for those of you that have not noticed..

http://store.steampowered.com/app/1800/

CS:GO Is currently 10% off for the pre-purchase.

I'll look @ this issue when i get some time.. I am guessing a css issue or something goofy like that.

We have launched our official IRC channel today! You may join us with either your favorite IRC client, such as mIRC or by clicking on the Chat link in the navigation bar. irc.gamesurge.net #sourcepython You may also try clicking here if you have a compatible IRC client installed: irc://irc.gamesurge...

I'll look into some sort of solution.

I know one thing we have discussed is making sp.give (or whatever it ends up being) return an index for the item it created. We have also talked about adding sp.fire (or something) but I don't know if either one has been done yet. (Been sick for a few days )

That may be something we add in the future, but for the time being you are welcome to add anything like that under tutorials for now.. Should the need arise to organize it further, we will take care of it then.

We plan to provide all the events that are currently included with eventscripts. As for the es functions, we have since renamed the project to Source.Python so it will be sp now. We plan to provide libraries to mimic a lot of the es functionality in time, however we cannot guarantee that everything ...

Its a much different system than media wiki.. templates are not nearly as important. Pages can be generated without much effort at all.. In the future we will authors to maintain their own wiki pages, but for the time being we are going to rely on a select few to start writing up the documentation.

Some of you may have noticed a lot of new changes to the website today. We are currently in the process of adding new features to the website we feel will help support the website's growth and popularity in the coming future. We have added a few notable things such as a Wiki for documentation and li...

Yes, but this kind of inconsistency is even worse. I renember reading somewhere something like: Consistency within a language is important. Consistency within a project is more important. Consistency within a module is most important. Following that philosophy, it should at least be consistant in t...

I also agree an auth system would be highly useful....

However, I think having an admin plugin would not be a bad idea assuming we do not go overboard with it. (Developed in python)

I agree, but I don't like underscore function names. Also when SP more or less directly exposes the EngineAPI it seems to make sense to actually keep the CamelCase functions as they resemble the way the game is written (instead of forcing them into a PEP8 style). CamelCase is more of a java standar...

I find myself really on the fence about this.... If it can easily be done in c++, then it would be a great addition! If it proves to be a pain, I think this idea should be put on the back burner for now...