[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 using Day of Defeat, uncomment the line at the very top of the plugin that says "Uncomment"
 */

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...

[Alka]

0o C00L...This will be very helpful! Gj man.

[stupok]

This sounds like a useful tool and I think I've figured out how to use it. However, it doesn't compile due to the error:

//// fmresearch.sma
// C:\hlserver\AMXX Scripting\fmresearch.sma(74) : fatal error 100: cannot read
from file: "fmresearch/constlist.inl"
//
// Compilation aborted.
// 1 Error.
// Could not locate output file C:\hlserver\AMXX Scripting\compiled\fmresearch.a
mx (compile failed).

[Wilson [29th ID]]

Hah, wow. Fixed. I put the const inside the sma for simplicity.

[Pro Patria Finland]

Will definetly test this when I get home.

[_Master_]

Wilson I hope you do realize that with minor modifications and additions some users may begin to code 4-th(!) party scripts for this (such as heros for ex.)... All hell will break loose then... prepare yourself

[Wilson [29th ID]]

Hah, master, I'm interested..what are you talking about?

[_Master_]

I'm talking about a cfg file with per-map settings for a specific(but not only) player.
Ex: A player is selected (via configurable algorithm) and his/hers pevs gets modified. Voila ! Your own custom hero, not limited by plugin design.

Players could be selected based on team, frags, deaths, IP, .... you get the idea. Variations on this are endless.

[X-Script]

;)

good job.

[Lee]

I don't really understand the point of this:

if(!expr)
    doStuff()
else if(expr)
    doOtherStuff()