| Zesstra | b6ac9f6 | 2020-01-21 11:11:16 +0100 | [diff] [blame] | 1 | SYNOPSIS |
| 2 | int set_next_reset(int delay) |
| MG Mud User | 88f1247 | 2016-06-24 23:31:02 +0200 | [diff] [blame] | 3 | |
| Zesstra | 715ec20 | 2025-07-09 22:18:31 +0200 | [diff] [blame^] | 4 | DESCRIPTION |
| 5 | Instruct the gamedriver to reset this object not earlier than |
| 6 | in <delay> seconds. If a negative value is given as delay, the object |
| 7 | will never reset (useful for blueprints). If 0 is given, the |
| 8 | object's reset time is not changed. |
| MG Mud User | 88f1247 | 2016-06-24 23:31:02 +0200 | [diff] [blame] | 9 | |
| Zesstra | 715ec20 | 2025-07-09 22:18:31 +0200 | [diff] [blame^] | 10 | Result is the former delay to the objects next reset (which can be |
| 11 | negative if the reset was overdue). |
| MG Mud User | 88f1247 | 2016-06-24 23:31:02 +0200 | [diff] [blame] | 12 | |
| Zesstra | 715ec20 | 2025-07-09 22:18:31 +0200 | [diff] [blame^] | 13 | Note that the actual time the reset occurs depends on when |
| 14 | the object will be used after the given time delay. |
| MG Mud User | 88f1247 | 2016-06-24 23:31:02 +0200 | [diff] [blame] | 15 | |
| Zesstra | 715ec20 | 2025-07-09 22:18:31 +0200 | [diff] [blame^] | 16 | EXAMPLES |
| 17 | set_next_reset(15*60); // Next reset in 15 Minutes or later |
| 18 | set_next_reset(0) --> just returns the time until the |
| 19 | next reset. |
| MG Mud User | 88f1247 | 2016-06-24 23:31:02 +0200 | [diff] [blame] | 20 | |
| Zesstra | 715ec20 | 2025-07-09 22:18:31 +0200 | [diff] [blame^] | 21 | HISTORY |
| 22 | Introduced in LDMud 3.2.6, adapted from Morgengrauen. |
| 23 | |
| 24 | SEE ALSO |