This wiki is archived and useful information is being migrated to the main bzflag.org website
Editing Bz eTickEvent
Warning: The database has been locked for maintenance, so you will not be able to save your edits right now. You may wish to copy and paste your text into a text file and save it for later.
The administrator who locked it offered this explanation: Archived wiki
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 3: | Line 3: | ||
==Overview== | ==Overview== | ||
| − | The '''bz_eTickevent''' is an API event that is called once for each [[BZFS]] main loop. The wait time between tick calls can vary | + | The '''bz_eTickevent''' is an API event that is called once for each [[BZFS]] main loop. The wait time between tick calls can vary grealy depending on server load network conditions. Plug-ins that wish to enforce a maximum wait time between ticks should call [[bz_setMaxWaitTime]] with the longest wait time that is acceptable. |
==Data== | ==Data== | ||
| Line 17: | Line 17: | ||
|bz_eTickEvent | |bz_eTickEvent | ||
|- | |- | ||
| − | | | + | |time |
|double | |double | ||
| − | |Local Server time of the event | + | |Local Server time of the event |
|} | |} | ||
