Difference between revisions of "Bethesda Tutorial Basic Quest Scripting/ru"

{{RussianPage|t}}

* Основы структуры скриптов и их присоединение к объектам в Creation Engine

* Как взаимодействовать с событиями при помощи нового скриптового языка

(Еще проще о скриптах ты можешь прочесть в статье {{ulink|Bethesda_Tutorial_Papyrus_Hello_World/ru|"Hello, World"}}.)

Скриптовый язык, используемый Creation Kit зовется Papyrus (да-да, тот самый папирус, который использовался в качестве бумаги в древнем Египте). Скрипты, написанные на Пупирусе - это обычные текстовые файлы, которые во время выполнения транслируются в байт-код.  

{{NewFeature|Новая система похожа на старую TESScript, но требует несколько иного образа мышления. Ты больше не можешь напрямую манипулировать объектами игрового мира; поток твоего скрипта может быть прервана посередине; куча синтаксического сахара, вроде всеми любимых скобок. В общем новый язык стал больше походить на [http://lua.org Lua] или, скажем, [http://python.org Python]. Если ты хорошо ориентируешься в TESScript, то ознакомься с {{ulink|Differences_from_Previous_Scripting|руководством по переходу}}.}}

Кликни по кнопке "Add". Редактор немного подумает, после чего отобразит список всех возможных скриптов, которые можно прицепить к этому персонажу. Ты создаешь новый. Дважды щелкни по пункту "[New Script]" в верхней части списка.  

Появится еще одно окошко, в котором ты можешь указать имя скрипта. Пиши: "GSQThiefScript" и щелкай по "OK".

=Properties=

Double-click on the script name to bring up the Properties Window for this script. On their own, scripts don't know about any objects in the game other than the one to which they're attached. We use properties to hook objects together so they can affect each other. In our example, we want to set GSQ01 to stage 20 when the thief is killed, so we need to tell the script which quest we care about.  

Press the "Add Property" button at the bottom left of this window. This is where we create the property. In the Type field, either choose "Quest" from the pulldown, or type in the word "Quest". Put "TutorialQuest" in the Name field, and leave everything else blank.  

We've now told the script that it should care about something called "TutorialQuest," but it doesn't know which quest that is. Click on the property we just made in the list, and click "Edit Value" on the right side of the window. A new pulldown menu will appear, listing all the quests in the game. Choose "GSQ01" from this menu, and hit OK.  

=Writing the Script=

Now that we've added this property, we should add some actual script to do something with it! Right-click on the script name and select "Edit Source" to bring up the script editor.  

The top line (<code>Scriptname GSQThiefScript extends ObjectReference</code>) is boilerplate that the editor made for us when we created the script. A few lines below that is the textual version of the property we made.  

At the bottom of the text, copy and paste the following snippet of code.  

Once again, ignore the <code>SetObjectiveDisplayed(20)</code>

If you're familiar enough with programming or scripting that what you just pasted made sense to you, feel free to skip ahead to the "Scripting the Amulet" section. For everyone else, we'll go through line by line.  

** This line declares that the script will respond to the actor dying. When the actor dies, the game will start executing the code from this point. The game will put whoever killed the actor into the "killer" variable, but that part doesn't matter to us.  

** Just like when we called <code>SetStage</code> on the owning quest in the dialogue tutorial, this will set stage 20 on the quest that we set with the TutorialQuest property.  

** We indent it for readability.  

** This signifies the end of our handling of the death event.  

Select "Save" from the file menu (or press Ctrl-S) and the editor will attempt to compile your script. An output window will pop up -- if your script is syntactically correct, it will look like this:  

If you see anything else in there, you typed something wrong. Try again!  

Once you're done, close the script windows and the actor window, and save your plugin. Now it's time to script the amulet itself.

=Scripting the Amulet=

Open up the GSQAmulet item we created in [[Bethesda_Tutorial_Creating_an_Item|the last tutorial]]. In the armor window, the scripts area is on the far right.  

Create a new script just like we did before, and call it GSQAmuletScript. Add a Quest property to it, but to see a nifty trick, call it "GSQ01" instead of "TutorialQuest" this time.  

It automatically set the value of the property for you, since you gave the property a name that matches an existing ID. If you're declaring a lot of properties, this can save you a bunch of time.  

Open up the script, and we're going to add an event to it. The amulet can't die (obviously), but we do want to know when the player picks it up. Our event script will look like this:  

Ignore it once again. It will be explained in the section about objectives.

There a few things to note in this script:

* The parameters in the declaration (<code>newContainer</code> and <code>oldContainer</code>) will get filled in by the game when it tells this script to handle the event.  

* Because the OnContainerChanged event will fire whenever this object changes hands, we need to make sure we only set the stage when it's the player taking it, hence the <code>if</code>/<code>endif</code> block.  

* <code>Game.GetPlayer()</code> is a convenient way to get a reference to the player without needing to set a property, and <code>newContainer</code> was filled by the engine when this event fired, so we can do a comparison in the second line to make sure the item is moving into the player.  

* The way this script is written, SetStage will be called every time the player picks up the amulet. This doesn't matter because each quest stage can only happen once - calling SetStage(30) has no effect after the first time.

This script is also good to go, then. Close the script and armor windows, and save your plugin.  

You can now play through the quest from start to finish, checking the console with [[ShowQuestVars|SQV]] to see its stage changing.  

Players can't use the console, though, so we'll learn how to give them better feedback about the quest in the next chapter.  

{{ProTip|The scripts for Skyrim are just text files that live in your data directory before they get compiled into bytecode. This means that if you've got a favorite text editor, you can use it to work on scripts. We've included setups for both [[Sublime Text Setup|Sublime Text]] and [[Notepad++ Setup|Notepad++]] that provide syntax highlighting, some basic autocompletion, and compilation shortcuts. If you're going to get heavily into scripting, these tools can make your life a lot easier.}}

|Prev=Bethesda_Tutorial_Creating_an_Itemru