Can you post the shortest plugin that causes a crash?

make_object() calls <class>._obj(<ptr>) and we have added this as a class method to BaseEntity. https://github.com/Source-Python-Dev-Team/Source.Python/blob/master/addons/source-python/packages/source-python/entities/entity.py#L149

Just take a look at the function's prototype:[cpp]bool CBasePlayer::BumpWeapon( CBaseCombatWeapon *pWeapon )[/cpp]As you can this this is a method, which takes one argument (a CBaseCombatWeapon pointer) and returns a boolean. Since this is a member function, there is another argument, which is calle...

The problem is that your arguments tuple is wrong. The WeaponEntity line just just work fine, because it inherits from BaseEntity. # ============================================================================= # >> IMPORTS # ==========================================================================...

Yeah, works fine for me, too. But it would be nice if you could just copy the error and post it here instead of making screenshots.

We have finally posted a new release! This release includes some crash and bug fixes, updates to site packages, enhancements, new features and more. The full changelog can be found here . As always, you can find the release here: https://github.com/Source-Python-Dev-Team/Source.Python/releases

Hmm, I don't think we need something like that. Back in ES I have never seen anyone using that except for eventscripts_noisy and maybe sv_cheats. If you should ever need to do something like that, it's not hard to do this manually. sv_cheats = ConVar('sv_cheats') def load(): ...

Yeah, I agree. The hitbox is usually shipped with the model file.

I guess we can change the hitboxes (yes, plural: it's not just a single box you can resize) by using this header, but as you can see it's pretty complex.

What are you trying to achieve? A hitbox is not the same like a collision box. So, could you please be more specific what you want to do?

Well, I wouldn't call this a temporary fix. It's more like a workaround for a specific situation.

Anyways, thanks for sharing.

Thanks for reminding! I guess we forgot this post. I have now added your fix! https://github.com/Source-Python-Dev-Team/Source.Python/commit/44155139e1d8a78dfe9646721c50f1f0c429ddd6 Regarding your edit: Since I haven't done much testings on this issue, I would be happy if you could provide us your t...

Dear community,

we would like to use this thread to gather some general ideas, suggestions and improvements.

Please post your thoughts about the current state of our plugin! We are excited to hear them!

Thank you,
Source.Python Development Team

Great! I have added the changes to the repo. https://github.com/Source-Python-Dev-Team/Source.Python/commit/5d71b74984940a58cc27c3f28e2a6d7f2d0987eb

Alright, I just compiled a version with statically linked runtime libraries.

Let me know if it's working.

Well, the problem is that that folder isn't on the search path. Your OS doesn't know that it's there. I'm curious if it would work if you add that folder to the search path. If you want to test this make sure to uninstall the previously installed Redistributable Package and verify that it's not work...

My guess is that your 240KB loader was built in debug mode. But I don't think we have ever released a debug build. Could you please disable Metamod and every other server plugin. I'm also surprised that there are no loading messages from Metamod. I thought it would also print something to the console.

Why should it be too small? The loader only consists of this file. https://github.com/Source-Python-Dev-Team/Source.Python/blob/master/src/loader/loader_main.cpp However, could you please add +developer 1 -condebug to your command line. This will write some more information to ../csgo/console.log.

Yes, the code L'In20Cible posted is for CS:S.

I can't say what's better. I guess this is a matter of preference. The benefit of #3 is obviously that you can find every constant in a single file. But if you use #2 you will find every constant in the module they belong to. This creates some logical structure.

satoon101 wrote:Does this also mean we cannot call that function?

Yep, currently we can't, but we can update our plugin so that we can also handle these special cases. I have several ideas, but I need some time to think about them.