[joaquimandrade]

Some days ago, Stupok (talking about the conversion of functions provided by the cstrike module to fakemeta) made this question:

Originally Posted by stupok I know that people request this kind of conversion a lot, but I don't see how this is better than just using the functions in the cstrike module. Am I missing something? Is there some benefit?

After some talk and some tests it was made clear that using converted functions using the fakemeta module to replace those provided by cstrike is not only inefficient but also doesn't bring any benefit.

I became curious to see what happens between Engine and Fakemeta . So, i profiled some functions provided by "fakemeta_util.inc" against engine natives (that do exactly the same).

The results go as attachment. If you think that the tests are not correctly made feel free to do them yourself and post.

[Hawk552]

It's great to see someone finally pick apart these things. The "Fakemeta high" was starting to get very annoying.

[Arkshine]

I'm not surprised at all since more natives are called with fakemeta. These natives which generate also more code each time where engine does the job directly.

ok, now, time to convert all fakemeta plugin to engine.

[Dores]

So, coders should use the original modules(CS, Engine) instead of Fakemeta?
It might take a while to get use to that.

[joaquimandrade]

Originally Posted by Dores So, coders should use the original modules(CS, Engine) instead of Fakemeta? It might take a while to get use to that.

Yes. And, talking about the cstrike module, there is also this:

Originally Posted by Hawk552 Completely agreed. I went on a rant like this a while ago. Using FakeMeta in place of cstrike is a terrible idea. If the offsets ever change, the AMXX team will jump right on it and release a new cstrike module right away. This would require anyone using this header to update it themselves or hope that you're still around to do it. There are many, many other problems but most have already been covered in this thread. EDIT: Here it is: http://forums.alliedmods.net/showthread.php?p=734716 It's not directly related to the cstrike module, but many of the concepts still apply.

Not that it will certainly happen but, it is possible.

[Arkshine]

Originally Posted by Dores So, coders should use the original modules(CS, Engine) instead of Fakemeta? It might take a while to get use to that.

For functions which can be done with Ctrike or Engine, it would be more efficient than using Fakemeta.

[Hawk552]

You should do some more benchmarks and post this in the tutorials section. I'd love to see everyone back away from using Fakemeta for everything. Unfortunately, not all scripters look here.

[joaquimandrade]

Originally Posted by Hawk552 You should do some more benchmarks and post this in the tutorials section. I'd love to see everyone back away from using Fakemeta for everything. Unfortunately, not all scripters look here.

Ok.

[SnoW]

Did someone mention engine and cstrike? I mean, isn't fakemeta the only module exists!?
Anyway... I'm so new coder that when I came here everyone was using FM and I got used to it. Like that I've never actually used engine. Ofc I've transfered some old plugins etc, but all coding still with FM. It would get little weird to start using engine bah.

[ot_207]

Interesting ... Nice job testing these things out.

Question. Is it a good idea to combine them? I mean, in the past I saw a lot of people saying. You should not use both fakemeta and engine.
I think this is the problem that made the people get "Fakemeta High"