[Hoborific]

Title is some things I tried to search, I found nothing on housekeeping ( Maybe I am using the wrong word? I spend a lot of time with Java lately ), I also read the other day a user mentioned salting a users login, I know it's extremely unnecessary but it has been bothering me simply because I've never heard of anyone doing this in sa-mp, unless it's between the server and an external source, but I assumed it was client salting... I also couldn't find a decent thread on code layout structure..

Right now I use the following.

pawn Код:

#include "../NGZ/Defines.pwn"
#include "../NGZ/Commands.pwn"
#include "../NGZ/Functions.pwn"
//etc



main()


// Default calls here

but the readability has been hindering my development time and frankly, i'm just curious, it's quite readable but at the same time I like to overly do things to an Excessive point, thanks in advance, Hoborific.

[CodyCummings]

It's good to have everything organized the way you like it, I'd rather have multiple files instead of a single huge script trying to figure out what things are, where things are or where things go etc.

You're not doing anything overkill in my opinion, but it might take some getting used to if you haven't done it like this before, but believe me the development time should be quite a bit better than with a huge single file.

[Hoborific]

Thanks for the negative rep ( not you Cody. )

I hash the password well, so fuck off. last I checked was salting with information from the client, client generates a salt, salts hash, sends hash to server, gets stored there. or something like that anyway, sorry for asking, guess I should just start using plaintext then you ignorant cunts.

[RvGamers]

Well that escalated quickly.