Hendricks266, on 11 January 2014 - 03:37 AM, said:
TerminX, on 11 January 2014 - 04:33 AM, said:
Yes! It's like you two were speaking right out of my mind!
Fox, on 11 January 2014 - 08:43 AM, said:
- player_skill
- god
- eog
- volume_number
- level_number
- noexits
Going by TerminX explanation a code that uses this would never work out in a real connection. The solution would be to add non-userdef alternatives like there are VOLUME or LEVEL variables?
VOLUME and LEVEL are merely read-only aliases to the respective userdefs members. The general pattern is that you want to set these to affect commands that behave conditionally on them. So the real solution is to make the commands (in Lunatic: functions, for example in 'gv' if there's no better place for them) accept these conditioning values as arguments. For example, the Lunatic interface could (and probably will) look like that:
gv.currentLevel() -- will be one-based, I think. It's just more natural that way because it's how everyone thinks of these gv.currentEpisode() gv.currentMapName([ep, lev]) -- this one returns the current map name if passed no args, or that of E<ep>L<lev>

Help
Duke4.net
DNF #1
Duke 3D #1



