Make more explicit the sync issues involved in scripting
parent
cdbe27557b
commit
2607457400
|
@ -141,8 +141,9 @@ that does not change.
|
|||
\subsection{Object states}
|
||||
Most object states that are changed from the scripts are not in fact changed, but queued up to be synchronized
|
||||
among clients. This means that you cannot check the state later in the same script invokation and expect it to
|
||||
have changed. Instead, if for example you want to mark droids that have been ordered to do something, you can
|
||||
mark them by adding a custom property. Note that this property will not be remembered when it goes out of scope.
|
||||
have changed. This includes such things as giving orders to droids, setting production to structures, and so on.
|
||||
Instead, if for example you want to mark droids that have been ordered to do something, you can mark them by
|
||||
adding a custom property. Note that this property will not be remembered when it goes out of scope.
|
||||
|
||||
\subsection{Early research}
|
||||
You cannot set research topics for research labs directly from eventStartLevel. Instead, queue up a function
|
||||
|
|
Loading…
Reference in New Issue