[Ingram]

okay... PM is much better at asking the same question

[Greenberet]

i want a callnative interface for this:

Sometimes you are in the game. Then you want to read e.g. speed. But you dont have an cmd for this. So you have to write one -> compile -> upload -> restart the server. Next time you want to change e.g. an effect. Hey you dont have an cmd for this. So you have to write one again -> compile -> upload -> restart the server...

Okay these 2 aren't the best examples, but i dont know a better example that is not mod specific.

There are 2 solutions for this problem:
Write an very big wrapper for each native
or implement something like callfunc for natives.

[Hawk552]

Originally Posted by PM It matters because I think that implementing weird features which you don't see any need for is not really the dev team's biggest hobby So.. You want to make an AMX Mod X plugin.. which.. interprets AMX Mod X plugins? Do you have any technical reason to do this or is it a "just for fun" project?

Is there any way to do it with #emit? That's the only other way I can think of doing it.

It's a 'just for fun' project, but isn't all of AMXX?

[Greenberet]

hawk i thought of emit also, but the problem is that you cant use arrays to call them you have to hardcode the native names

[BAILOPAN]

greenberet: missing solution... one command to set pdata values and another to set pev values. How hard can this be if you use numbers for the pev values to avoid enum lookup?

Hawk552: Yes and no. We try to only add features that will help a user solve a specific problem. But if it's trying to solve a problem that only one person will use for one specific thing, it's not worth the time. Thus, we attempt to see the reasoning behind the request first.

[Hawk552]

Originally Posted by BAILOPAN greenberet: missing solution... one command to set pdata values and another to set pev values. How hard can this be if you use numbers for the pev values to avoid enum lookup? Hawk552: Yes and no. We try to only add features that will help a user solve a specific problem. But if it's trying to solve a problem that only one person will use for one specific thing, it's not worth the time. Thus, we attempt to see the reasoning behind the request first.

Alright, so is there any chance this will come to be?

[BAILOPAN]

Probably not. At least I don't have any plans to do it for the next release.

But I'll keep it open.

[Obbin]

I could sure use a function like this.
For example It's just too much trouble having a whole plugin just to get/set my origin, speed or w/e when I'm in the early stage of a plugin development.

That post may look retarded since I'm not 100% sure we are talking about the same thing