12 Jun 12, 07:19PM
To be honest, while it may be possible, recording/storing every action made to a map during its construction into a cubescript alias (or even aliases) is far-fetched.
It also would not be possible in coop, since theres no way of knowing what other clients are executing/manipulating via cubescript.
I brought it up because I noticed this mentioned in /source/src/CUBE_TODO.txt:
...which suggests that it was an attempted/planned original feature of CUBE.
---
About measuring the time elapsed between command executions, there is no current way of knowing no. Maybe there should be a hardcoded variable for such things.
Pseudocode:
[cubescript]echo $lastcommandtime
echo time since last command execution: (divf (- (millis) $lastcommandtime) 1000) seconds[/cubescript]
Should be do-able, could you give an example of what it may be useful for?
It also would not be possible in coop, since theres no way of knowing what other clients are executing/manipulating via cubescript.
I brought it up because I noticed this mentioned in /source/src/CUBE_TODO.txt:
Quote:- load demo of map editing -> crash?
...which suggests that it was an attempted/planned original feature of CUBE.
---
About measuring the time elapsed between command executions, there is no current way of knowing no. Maybe there should be a hardcoded variable for such things.
Pseudocode:
[cubescript]echo $lastcommandtime
echo time since last command execution: (divf (- (millis) $lastcommandtime) 1000) seconds[/cubescript]
Should be do-able, could you give an example of what it may be useful for?