Orpheu&Rage | Ham_AddPoints Hook | Permanent Player Trail | FM_ShouldCollide Semiclip
Hey, my questions for today are :
1. 2. 3. 4. How to make a permanent player trail? The existing plugin is really bad coded and I can't understand anything from it. I tried setting a task every 1 second and re-set the trail (TE_BEAMFOLLOW) but it lagged when player looked at it. 5. Thanks. |
Re: Orpheu&Rage | Ham_AddPoints Hook | Permanent Player Trail | FM_ShouldCollide Semi
1. It's explained in the Rage thread: https://forums.alliedmods.net/showthread.php?t=179706
But it seems like it never made it out of Beta and I didn't really see people use it. It's potentially more powerful, but it's more difficult to use (create hook handlers that is). Orpheu is good enough. 2. In your amxmodx/configs/orpheu/, in functions and virtualFunctions folders. There's not a set list of functions you can hook, it's totally dynamic and you have to provide data in these folders for Orpheu to use. That's done using JSON files containing signatures or other data for functions. You can find many around the forums as examples. 3. Looks like CBasePlayer::AddPoints() is only used by CGameScore ("game_score" entity?). It works, but it's probably not called when you expect it to be. 5. According to ReGameDLL_CS, it looks like CS doesn't even support ShouldCollide API in the first place. I.e: it's never called. |
Re: Orpheu&Rage | Ham_AddPoints Hook | Permanent Player Trail | FM_ShouldCollide Semi
Quote:
2. Quote:
3. Quote:
5. Quote:
Quote:
|
Re: Orpheu&Rage | Ham_AddPoints Hook | Permanent Player Trail | FM_ShouldCollide Semi
1. Not sure. Possibly use it to hook stuff that can't be hooked otherwise by Orpheu because some data types are not supported. It should be possible to go around that stuff in Orpheu with some memory hacking though. You should just stick with Orpheu and not bang your head thinking about Rage.
2. InstallGameRules is a function in the game dll that gets called when a g_pGameRules global variable is to be initialized in the game. HL version of this function (each mod can have its own, but they all return a CGameRules pointer): https://mxr.alliedmods.net/hlsdk/sou...erules.cpp#311 It's just an easy way of retrieving g_pGameRules which can be used to retrieve all kinds of game data or call some methods from CGameRules or CHalfLifeMultiplay classes. New 1.8.3 get_gamerules_* natives are dealing with this g_pGameRules. 3. When do you expect it to be called? As I said, it looks like it's only called by game_score entity and not when for example someone gets a frag by killing other player. 5. I believe ReGameDLL_CS accurately depicts what Valve's CS code is. I'll maybe take a deeper look into this. |
Re: Orpheu&Rage | Ham_AddPoints Hook | Permanent Player Trail | FM_ShouldCollide Semi
Even if Klippy already answered, I feel like you are still confused. Maybe I can help, idk.
Quote:
With orpheu you get access to this internal functions. That's why orpheu is great, you can interact directly with the game and change it's behaviour depending on what you want to do. That way you don't need to create ugly workarounds or inneficient code. Quote:
Quote:
As a matter of fact, that's why we hook new round with HTLV event, because that message is fired from RestartRound. Quote:
Quote:
So for example Ham_Spawn is basically CBasePlayer::Spawn. Also note that there are functions which can be called but can't be hooked, because they are not never called. You should not assume that any functions acts like you would expect it to, valve code is confusing. You should actually check the regamedll code for that specific function and see from where it's called, what this function really do, etc. That way you will know if your code is wrong or simply that function does not do what you expect it to. |
Re: Orpheu&Rage | Ham_AddPoints Hook | Permanent Player Trail | FM_ShouldCollide Semi
Quote:
|
Re: Orpheu&Rage | Ham_AddPoints Hook | Permanent Player Trail | FM_ShouldCollide Semi
Quote:
Quote:
Quote:
Quote:
Thanks guys. |
Re: Orpheu&Rage | Ham_AddPoints Hook | Permanent Player Trail | FM_ShouldCollide Semi
It's better to look in cs.so, because on linux function have names. Look into mp.dll when creating the windows signature.
I've already explained why. Ham functions are actually game functions, amxx has no control over them. Read again my post please. |
Re: Orpheu&Rage | Ham_AddPoints Hook | Permanent Player Trail | FM_ShouldCollide Semi
Quote:
|
Re: Orpheu&Rage | Ham_AddPoints Hook | Permanent Player Trail | FM_ShouldCollide Semi
Quote:
|
| All times are GMT -4. The time now is 17:59. |
Powered by vBulletin®
Copyright ©2000 - 2024, vBulletin Solutions, Inc.