SphereServer BugTracker - SphereServer
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001816SphereServernew feature requestpublic15-09-10 07:2617-10-12 00:37
ReporterCoruja 
Assigned ToTerrikate 
PrioritynormalSeverityminorReproducibilityN/A
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version0.56c Nightly 
Nightly Version20-09-2009
Experimental FlagsNone
Option FlagsNone
Internal Build Number
Summary0001816: f_onaccount_create
Descriptionsphere_serv_triggers.scp:

[PLEVEL 7]
f_onaccount_login
f_onaccount_delete
f_onchar_create
f_onchar_delete
f_onserver_start
f_onserver_save
f_onserver_save_ok
f_onserver_save_fail
f_onserver_save_finished
f_onserver_exit
f_onserver_blockip

where's f_onaccount_create? :D
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
15-09-10 07:26CorujaNew Issue
15-09-10 14:27ShiryuXNote Added: 0000633
15-09-10 14:27ShiryuXNote Edited: 0000633bug_revision_view_page.php?rev_id=8
15-09-10 14:28ShiryuXNote Deleted: 0000633
22-09-10 21:37ShiryuXNote Added: 0000669
24-09-10 07:49CorujaNote Added: 0000675
17-10-12 00:37TerrikateStatusnew => resolved
17-10-12 00:37TerrikateFixed in Version => 0.56c Nightly
17-10-12 00:37TerrikateResolutionopen => fixed
17-10-12 00:37TerrikateAssigned To => Terrikate

Notes
(0000669)
ShiryuX   
22-09-10 21:37   
The only situation able to use this is 'Free Account' but is the same as using _login in there. For the rest of account creation methods, you either create them manually or with an automated script.
Any real use for this?
(0000675)
Coruja   
24-09-10 07:49   
It usefull in some cases that you must add accounts using SERV.ACCOUNT ADD ingame, since you cant create an MySQL table for this account just typing "serv.account add lol". It can be done with a custom function

[FUNCTION NewAccount]
//SINTAX: NewAccount login,password
SERV.ACCOUNT ADD <ARGV0> <ARGV1>
DB.CONNECT
DB.something
DB.CLOSE

But using f_onaccount_create we got more control over account creation because you can deny the creation without using workarounds (disabling SERV.ACCOUNT ADD function and make ppl use just the custom NewAccount function).

Btw its easier to use, because when I write SERV.ACCOUNT ADD the account info will be stored on SQL, and when this account get deleted it will delete account info on SQL too in the same way it get stored.

[FUNCTION f_onaccount_create]
//store account info on SQL

[FUNCTION f_onaccount_delete]
//delete account info from SQL