Many script commands have a DENIZEN modifier to run the command on the NPC instead of the Player, and these should always be used when calling a Task Script from the TASK Activity. Therefor any commands that require a Player will not function in a Task Script called from the activity. For example: RUNTASK C:PROGRAMSMYPROG. This parameter can include path information, but not wildcards. EXE file for the application you want to run. RUNTASK executable command line parameter Parameters. Greetings Other plugins (like MythicMobs) cant execute custom commands created in Denizen. This is a special case, as Activities occur without a player. This command can also launch third-party applications such as Windows Notepad. CHAT "Welcome to my orchard, have some apples!" CHAT "Welcome to my house, have some apples!" This is a very basic example for something that can in theory be very complex. Denizen Script Commands Commands are always written with a - before them, and are the core component of any script, the primary way to cause things to happen. You could check the completion for each quest, or, you could have all the quests call a Task Script and check against that. Add arguments /c .Say, for instance, you have multiple 'quests' that all have the same outcome. Its syntax, aside from /ex is exactly the same as any other Denizen script command. Imagine a scenario where you'd like to check a single outcome from multiple sources. The /ex command is an easy way to run a single denizen script command in-game.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |