search

Source-Python-Dev-Team / Source.Python

This plugin aims to use boost::python and create an easily accessible wrapper around the Source Engine API for scripter use.
http://forums.sourcepython.com
GNU General Public License v3.0
163 stars 31 forks source link

CS2 update #493

Open archy901 opened 1 year ago

archy901 commented 1 year ago

Hi! Yesterday Valve released new version of the game, CS2. Could you kindly tell, if you have any plans of updating current software or, maybe at least, check possability of using it for CS2? Any help very appreciated 🙏

Ayuto commented 1 year ago

Unfortunately, there are no plans to support it at the moment. Please also see this thread on the forums: https://forums.sourcepython.com/viewtopic.php?f=10&t=2767

archy901 commented 1 year ago

Unfortunately, there are no plans to support it at the moment. Please also see this thread on the forums: https://forums.sourcepython.com/viewtopic.php?f=10&t=2767

I see 😢 thank you for the reply and for sharing the link

thetredev commented 11 months ago

At least we have "real" servers now to test it on: https://developer.valvesoftware.com/wiki/Counter-Strike_2/Dedicated_Servers

No more need to login, no workshop items are downloaded anymore, it's a true server binary since a couple of weeks.

thetredev commented 7 months ago

For what it's worth, I would argue that Source.Python can be classified as a Source 1 plugin. Porting it to Source 2, or adding support for Source 2 looks to be way too much (maintenance) work from what I can tell. I think they changed all the entity signatures and/or handling of them with Source 2 as well (at least I read that somewhere sometime ago, so take that one with a grain of salt). Plus everything is 64-bit so that's another thing to consider supporting/maintaining. That being said, I'm not a Source.Python maintainer, but I was there as a learner and plugin developer right from the start (back then as BackRaw) when the EventScripts era ended. I saw how hard it was to keep up with Valve updating their engine(s) and breaking Source.Python in the process a lot. It was fun reading about it in the forums, but I can't imagine all the headaches that it caused the maintainers. So, figuratively, the same (or much worse) could be said for Source 2 support alongside Source 1.

So, like I said at the start, it's probably the best to keep Source.Python aimed at Source 1 while letting other plugins try their take on Source 2 IMHO. New generations of engines/servers require new generations of plugins I assume. I think the only big change Source.Python will see, if possible and maintainable, is updating Python to a recent release like 3.12.

There's a C# project that's aimed specifically at Source 2: https://github.com/roflmuffin/CounterStrikeSharp. Maybe there can also be a Source2.Python? Who knows.

I personally would love for Source.Python and Source 1 to continue to live and breathe until the end of time regardless of Source 2, because I kinda grew up with them and Source.Python, as well as EventScripts before it, taught me how to do the Python thing, basically catapulting my IT career to where I never thought I could land. And I can subjectively say that modding in and of itself was at its peak with Source 1, starting 2004 and ending 2012/2013, partly due to CS:GO being much more matchmaking-focused. That being said I haven't tried modding CS2 yet using CounterStrikeSharp, so maybe it will be even better than it was with Source 1, who knows.

I also understand that all of us simply lost a bit of the passion we once had for this whole thing. You know, due to life being life and so on. But since I still see a lot of interest in Source.Python in general, I don't believe it will die anytime soon anyways.

Thank you, maintainers! It was a beautiful ride for me and I'm still looking at this project from time to time to check the progress this plugin makes, even though I'm unfortunately not the CS:S basement dweller I once was lol.