Account: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 12: | Line 12: | ||
[[Category:Scripting Concepts]] | [[Category:Scripting Concepts]] | ||
[[hu: | [[hu:account]] | ||
[[ru:Account]] | [[ru:Account]] | ||
[[pl:Account]] | [[pl:Account]] | ||
[[it:Account]] | [[it:Account]] | ||
[[de:Account]] | [[de:Account]] | ||
Revision as of 09:49, 14 December 2018
The account class represents a player's server account. You can get the account object associated to any client using getPlayerAccount.
Accounts are unique to each client and can be used to store information that is persistent across map changes and user sessions. Clients that join without an account are given a temporary 'guest' account. This can store information like any other account, but isn't saved across sessions.
When a user logs in or out, the account object assigned to them will change. As such, you must not assume that the account attached to a client remains constant during their session.
PHP code to check password hashes from the MTA server database is here.
Related scripting functions
Server
- addAccount
- copyAccountData
- getAccount
- getAccountData
- getAccountName
- getAccountPlayer
- getAccountSerial
- getAccounts
- getAccountsBySerial
- getAllAccountData
- getPlayerAccount
- isGuestAccount
- logIn
- logOut
- removeAccount
- setAccountData
- setAccountPassword
- getAccountByID
- getAccountID
- getAccountIP
- getAccountsByData
- getAccountsByIP
- setAccountName