Ham_TakeDamage hitplace check.
Been looking around now for a while but I can't find any way to check where a player has gotten shot using hamsandwich.
|
Re: Ham_TakeDamage hitplace check.
May be with m_LastHitGroup, don't remember.
Else you can use the trace pointer from TraceAttack, TraceAttack is called from there. |
Re: Ham_TakeDamage hitplace check.
What's about:
PHP Code:
|
Re: Ham_TakeDamage hitplace check.
Quote:
Don't feel like including fakemeta just to call 1 function. Quote:
|
Re: Ham_TakeDamage hitplace check.
Been searching ever since my last reply but can't find any indication that you are able to modify damage in client_damage, which - obviously - is what I want to do.
I haven't found any other functions either which doesn't require fakemeta. And like I mentioned before I don't feel like including fakemeta just for calling 1 or 2 functions. |
Re: Ham_TakeDamage hitplace check.
Quote:
|
Re: Ham_TakeDamage hitplace check.
Quote:
I thought I read somewhere that using fakemeta should be avoided if possible. Due to the long execution times and CPU usage. EDIT: Thanks for nullifying any of my previous doubts, btw. |
Re: Ham_TakeDamage hitplace check.
It's wrong. You just have to learn what does each functions, and using the appropriate one considering your needs, whatever the module. What you can keep in mind is to use as few natives as you can. For example, if you have one engine native which does something, and if you have several natives from fakemeta which do the same thing, you are going to use the engine native. A matter to code intelligently, to choose the best function in your situation, though it requires that you take a look at amxx source code to understand better what does really each natives. You see what I mean ?
|
Re: Ham_TakeDamage hitplace check.
Quote:
Greatly appreciated. |
Re: Ham_TakeDamage hitplace check.
fakemeta_util, that's something you can actually avoid, because it's a bunch of stocks converted from engine/fun module to fakemeta, and it uses more natives most of times for one thing. As result, slower code. It's not a module, but just wanted to give an example of what you should not do/use.
|
| All times are GMT -4. The time now is 11:11. |
Powered by vBulletin®
Copyright ©2000 - 2024, vBulletin Solutions, Inc.