FakeMeta Research

[Wilson [29th ID]]

/*
* FAKEMETA RESEARCH (v1.0)
* by Wilson [29th ID]
*
* www.29th.org
*
* DESCRIPTION
* This plugin allows developers to research through fakemeta several
* times quicker than they would normally take, by coding an entire
* test plugin just to find a PEV value, or ES/CD setting, or alter
* the said variables, or find that specific PDATA offset. FM Research
* allows you to read, set, log, and compare these values dynamically
* in game.
*
* USAGE
*
* PEV
* Read: fm_pev <ent> <member> read
* Set: fm_pev <ent> <member> <arg1> <arg2> <arg3>
*
* ClientData (CD)
* Read: fm_cd <ent> <member> read
* Set: fm_cd <ent> <member> <arg1> <arg2> <arg3>
*
* EntityState (ES)
* Read: fm_cd <ent> <member> read
* Set: fm_cd <ent> <member> <arg1> <arg2> <arg3>
*
* Pdata
* Read: fm_pdata <ent> <offset> read
* Set: fm_pdata <ent> <offset> <arg>
*
* Pdata Ranges
* Log: fm_pdata_log <ent> <low> <high>
* Read: fm_pdata_log <ent> <low> <high> console
* Store: fm_pdata_log <ent> <low> <high> store
* Compare: fm_pdata_log <ent> <low> <high> compare
* Search: fm_pdata_search <ent> <low> <high> <target>
*
* SHORTCUTS
* -For the <ent> argument, you can use keywords such as "id", "me", "wpn", "gun"
* -The pdata argument "console" can be replaced by "con"
* -To reset ClientData or EntityState data, use the "read" argument at the end, or the "reset" argument.
*
* NOTE
* If you are NOT using Day of Defeat, comment the line at the very top of the plugin that says "Comment"
*/


Something I've been working on for a while now - started to help myself but then realised there was not really another plugin out there that did this for everyone..So I made it more user-friendly in hopes that it can help others out as much as it has me.

Examples
Altering your origin
fm_pev me pev_origin 124 832 15

Altering your animation
fm_es me es_sequence 9

Making another player hold a punchangle
fm_cd 3 cd_punchange 120 120 50

Finding your weapon's pdata offset that holds the clip ammo
fm_pdata_search wpn 75 125 8

Finding out which pdata offset is different when you hold an awp and scope in with an awp
Non-Scoped: fm_pdata_log wpn 0 100 store
Scoped: fm_pdata_log wpn 0 100 compare

And so much more...

[diamond-optic]

weee

FINALLY

:P thanks wilson

[Wilson [29th ID]]

Updated - forgot to include the const list. Fixed.

[ghzero]

compiling of .sma failed:

//// fmresearch.sma
// c:\!dokus\AMXModX.org\compile\fmresearch.sma(936) : error 088: number of arg
ments does not match definition
// c:\!dokus\AMXModX.org\compile\fmresearch.sma(998) : error 088: number of arg
ments does not match definition
//
// 2 Errors.
// Could not locate output file compiled\fmresearch.amx (compile failed).
//
// Compilation Time: 0,73 sec
// ----------------------------------------


line 936:
get_pdata_string( m_pdata_ent, i, test_sz, 127 );

..I changed it to the defaults of the missing parameters like:
get_pdata_string( m_pdata_ent, i, test_sz, 127, 1, -5 );

..but dont know if it work well with this (compile are succesfully!)

[diamond-optic]

in the version i have that works (i think its a bit older) the 2 lines that fail in the version of this thread look like this:

get_pdata_string( m_pdata_ent, i, test_sz, 127, _, 4 );

which basically means use the default byref value (which is 1) and then the linux offset which 99% of the time is 4

[ghzero]

allright ..remember that _ means the default value..

what offset should I use to using fakemetaresearch.sma//.amx on my home-pc installation (windows) ?

[diamond-optic]

on windows it doesnt use the linux offset, only on linux...

so no matter what number you have there it ignores it basically