[klippy]

Originally Posted by Solokiller I've got you covered on that: http://samvanheer.github.io/SC_Angel...mInventory.htm Scroll down to the properties; m_pHolder is the first item_inventory property. Assuming they kept the AS API up to date with changes to the entity, this should be everything you need. See http://samvanheer.github.io/SC_Angel...BaseEntity.htm for CBaseEntity properties so you can filter out the stuff that isn't part of item_inventory. Also related to inventory: http://samvanheer.github.io/SC_Angel...ntoryRules.htm http://samvanheer.github.io/SC_Angel...entoryList.htm http://samvanheer.github.io/SC_Angel...entoryMisc.htm

Found out your documentation just after I posted this, but I felt too lazy to update variable names.
Thanks anyway.

Originally Posted by Solokiller There is a way to get the Angelscript engine pointer; with some tricks you can extract all of the data from it and get the offsets for every member variable, the address of every method, function and global. You can also use it to add new API functionality, though you'll need to use some serious C++ magic to get strings to work since they get their memory from the server library's heap.

Months ago I thought about getting the engine pointer and making an AMXX module that will allow other modules and AMXX plugins to extend AS, and possibly communicate with each other. However, I was lazy.
What I didn't know is that I could dump all that info from the engine itself. I guess I'll take a look at the AS API documentation.