[Include] [INC] Progress Bar 1.3.1

[[HLF]Southclaw]

Some people complained about it, personally I've never had an issue with it I agree that it's a waste of memory.

Plus when I edited the script, I simply replaced the variable types and function names rather than mess about with the array. I will make an edit though, thanks for reminding me to!

[The__]

Tag mismatches on all of these :

SetPlayerProgressBarValue(playerid, hunger[playerid], PlayerInfo[playerid][pHunger]);
ShowPlayerProgressBar(playerid, hunger[playerid]);
SetPlayerProgressBarMaxValue(playerid,hunger[playerid], 100);
SetPlayerProgressBarValue(playerid, hunger[playerid], 100.0);
UpdatePlayerProgressBar(playerid,hunger[playerid]);

[The__]

Anyone ?

[Jessyy]

I hope that variable "hunger" & "PlayerInfo[playerid][pHunger]" is defined as a float one ...

new Float:hunger[...];

[The__]

new Bar:hunger[MAX_PLAYERS];
enum pInfo
{
      pHunger
};
new PlayerInfo[MAX_PLAYERS][pInfo];

[[HLF]Southclaw]

@Jessyy: if it's an enumerated field then he's not going to define it like that...

@The__: That's not a float is it!

Define it like this:

enum pInfo
{
    Float:pHunger
};

By the way, I have another update on the way for this, fixes some bugs, removes the array as the guy on the previous page reminded me it was still an array and thus a waste of memory

[The__]

Originally Posted by [HLF]Southclaw

...

So this is how I create the bar ?

new Bar:hunger[MAX_PLAYERS];

and this is a function which works, for example ? :

SetPlayerProgressBarMaxValue(playerid,hunger[playerid], 100.0);

[[HLF]Southclaw]

Yes, that's exactly how you do it.

[The__]

tag mismatch on

SetPlayerProgressBarMaxValue(playerid,hunger[playerid], 100.0);

[[HLF]Southclaw]

Oh if you're using player bars, the declaration tag is "PlayerBar:" not "Bar:".