Notes |
|
|
It is because ARGO is a client, but not a character. So character-based functions don't work with it. |
|
|
(0001124)
|
babidi
|
18-06-11 17:17
|
|
is there no reason to have argo if can't be used
i remember it was put there because of message when reject login
like onchar_create
src.sysmessage doesn't work
but
argo.sysmessage works |
|
|
|
ARGO.SYSMESSAGE works fine in f_onaccount_login. The problem is that returning 1 indicates that the connection should be closed, and Sphere will only wait long enough to send high-priority packets before terminating a connection.
You could try ARGO.FLUSH after the SYSMESSAGE, which should improve the chances of the packet being sent. |
|
|
(0001132)
|
babidi
|
19-06-11 02:29
|
|
you're right
i solved this way
if (<argn1> == 3)
ARGO.SYSMESSAGE @021 LOGIN NON ALLOWED!
ARGO.FLUSH
elif (<argn1> == 4)
return 1
endif |
|