[Arkshine]

• This:
  

  ~get_pdata_int(he, m_usEvent, XO_WEAPON) & HEGRENADE)
  get_pdata_int(nearbyNade, m_usEvent, XO_WEAPON) & SMOKENADE

  Even if it could give wanted results, it still a wrong way.
  m_usEvent doesn't return some bits. It's an index incremented when precache_event is called.
  As it has been said, you are just lucky it somehow works this way and hardcoding such "flag" is not appropriate since that's something which could be changed/altered.
  The proper way has been stated above, checking if not c4, and then checking if m_usEvent is same as precache_event(1, "events/createexplo.sc"). This would be more reliable.
  
  
• Not sure to see the point about FL_EXPLODED. Using a random engine flag doesn't seem a good idea as there is no meaning behind. At best, I would have used available custom _iuser* field. You could also check if pev_model or pev_solid is null, since set when a grenade is going to explode.
  
  
• As get_pdata_bool and others have been added in 1.8.3, you should make sure your stocks are available only for AMXX version < 1.8.3, avoiding compilation problem.
  
  
• I would strongly recommend the use of Orpheu as you could hook directly a grenade explosion, resulting an efficient, reliable and custom mod-friendly plugin.

Some idea : Adding a customizable delay before a grenade explosion. It would be appear probably more realistic if there is some slight [random or not] delay.

[BeasT]

Thanks for the suggestions, once again. I guess I wont't escape orpheu, ha Will post an update soon.

[ConnorMcLeod]

There is no requirement to use orpheu, if you don't feel to use it, just stick with Think hook, but as it was suggested, hook Ham_Think as POST and check owner or effects, when owner has been set to 0 it means nade has just exploded.

[Arkshine]

This is not a matter to feel or not, but what is the appropriate method to use considering the existing tool, generated code (efficiency, reliability, readability, etc.) and keeping custom mod in mind. Using orpheu is just the best way.

[BeasT]

Check the update. What's new:
remade the plugin with Orpheu; added a slight, distance based, explosion delay for nearby grenades.

[Arkshine]

Hm, why don't you use pev_dmgtime for smokegrenade ?

[BeasT]

So I could know which sgs are affected by exploding HE and then detonate them on SG_TumbleThink.

[Arkshine]

I mean, you could have used pev_dmgtime. I'm not sure to understand the use of a custom field here.

[BeasT]

I could, but then the sg only explodes when it reaches the ground.

[Arkshine]

That's the purpose of hooking as post. You let all the checks be done, if time is up but grenade is not on the ground, it's fine, you will catch up in your hook as post.