[^SmileY]

This Plugin show a teammate's money in hud (Using a set_hudmessage not direct_hudmessage) during a freezetime.

* If a no Freezetime, no money to show

PHP Code:

    /*Only Call event if Round is really End
    And Prevent to show money if
    server is restarted (sv_restart) or Game Commencing!*/
    register_logevent("RoundEnd",2,"1=Round_End"); 


I made a two versions :
- With a Freezetime and Without Freezetime, (See Attachments):

- 0.0.5 Fixed Hudmessage to CTs and TRs.
- 0.0.4 Added Pcvar 'pFreezetime', changed loops 'See: Optimizing Plugins (AMX Mod X Scripting) - AlliedModders Wiki'
- 0.0.3 (Fixed a set_task time + TRs & CTs Loop)
- 0.0.2 (Fixed Hudmessage)
- 0.0.1 (Initial Relase)

[Nur56]

PHP Code:

public RoundEnd() set_task(5.1,"RoundStart"); 


really bad practice

PHP Code:

new Float:Freezetime = get_cvar_float("mp_freezetime"); 


Use pcvars.. they are much faster and much more efficient

PHP Code:

    for(new i;i < iNum;i++)
    {
        new szName[32];
        get_user_name(iPlayers[i],szName,charsmax(szName));

        new Money = cs_get_user_money(iPlayers[i]);

        switch(cs_get_user_team(iPlayers[i]))
        {
            case CS_TEAM_T: posTR += formatex(HudTextTR[posTR],511-posTR,"%s ($ %d)^n",szName,Money);

            case CS_TEAM_CT: posCT += formatex(HudTextCT[posCT],511-posCT,"%s ($ %d)^n",szName,Money);
        }
    } 


Hogs CPU, cache iPlayers[i]

same goes for the other loop





Also.. why set_task(5.1) on round end when you can simply hook round start ???


Nice idea but needs some optimization

[^SmileY]

/*Only Call event if Round is really End And Prevent to show money if server is restarted (sv_restart) or Game Commencing!*/ register_logevent("RoundEnd",2,"1=Round_End");

Tested...

If used a sv_restart 1, the hudmessage dont appear.
Only if a round really is ended.

Example: If mp_startmoney is 16000.
Obviously you do not need a sample of the money.

Use witch round_start if you want..

[Nur56]

Make a global var, hook GameCommencing and Server restart, set var to 1, hook round start, check var, if it's 1 then don't print HUD, if it's 0 then print normally, hook round end, set var to 0.

much much better than hard-coding round start, if a plugin forces mp_freezetime to a different value then the admin can't use this plugin.

[^SmileY]

OK, i will be fix.

EDIT:

A Simple set_task() func. VS hook a 2 ~ 3 Events??

[Nur56]

Man you don't understand... hardcoding is always wrong... if any plugin forces mp_freezetime too, roundstart will be called late/early.

you have set_task(5.1).... if a plugin OTHER THAN YOURS has mp_freezetime 3, the admin will have to go and change that to maybe set_task 3.9 or something... do you understand now?

there is nothing to "test"

so just hook the events and it will be much better

[^SmileY]

Fixed

0.0.5 - Fixed Hudmessage to CTs and TRs.
0.0.4 - Added Pcvar (pFreezetime), changed loops (See: Optimizing Plugins (AMX Mod X Scripting) - AlliedModders Wiki)

[Nur56]

Man never post your first plugin...

You STILL didn't understand. sorry but I don't think this will be approved until you fix what I told you because an approver will tell you the same thing

[^SmileY]

First plugin?

Kkk...

[ConnorMcLeod]

Redundant, unapproved.