[TKZ227]

Quote:

Originally Posted by ****** If I were you I would forget about things like low-level information management systems, and focus on high-level code. Things like user systems have been done to death and there is ZERO reason to write your own when you can download one and have it running inside an hour! Writing your own, debugging it, securing it etc can take weeks of time better spent elsewhere. In fact this is true of MANY things - you want a language system, download it; you want a houses system, download it; you want an object editor, download it! Even if they don't have the features you want or some bugs, modifying them will a) STILL be faster than writing your own and b) benefit everyone else too! You could have a decent server set up in a matter of hours with all the mature systems out there now, most of them developed to the point where it barely even matters what backend they are on (but you can still base a decision of which to use on that information).

Oooh-******. I just remembered I have a quick question about y_commands when I saw your name. Kind of off topic, but I'll go for it.

I was reading up on y_commands and saw your built-in permission system..

Код:

Command_SetPlayerNamed(command[], playerid, set)

When I tried looking around for some example code of y_commands to get a feel for it, I saw many people neglecting this built-in permission system and instead reverting to calling on Player data within the command itself,
such as:

Код:

CMD:hi(playerid, params[], help)
{
      if(pInfo[playerid][Admin] > 1)
      {
              SendClientMessage(playerid, WHITE, "Hello!");
      }
}

Pardon the poor example.

My question is, does the built-in permissions in y_commands actually result in greater efficiency? Or is it just a tool for ease of access.