SKSE - Написание плагина - История изменений

Admin в 07:19, 18 апреля 2016

2016-04-18T07:19:51Z

Admin в 12:43, 10 февраля 2016

2016-02-10T12:43:20Z

Admin в 12:43, 10 февраля 2016

2016-02-10T12:43:12Z

Admin: /* Знакомимся с SKSE */

2016-02-10T12:40:46Z

‎Знакомимся с SKSE

Admin в 12:33, 10 февраля 2016

2016-02-10T12:33:30Z

Admin: /* Что может SKSE? Возможности и ограничения */

2016-02-10T11:49:59Z

‎Что может SKSE? Возможности и ограничения

Admin: /* Что может SKSE? Возможности и ограничения */

2016-02-10T07:34:29Z

‎Что может SKSE? Возможности и ограничения

Admin в 07:31, 10 февраля 2016

2016-02-10T07:31:10Z

Admin в 07:07, 10 февраля 2016

2016-02-10T07:07:11Z

Admin: /* Что может SKSE? Возможности и ограничения */

2016-02-10T07:05:57Z

‎Что может SKSE? Возможности и ограничения

@@ Строка 1: / Строка 1: @@
 [[Category:Учебники]]
 [[Category:SKSE]]
 {{Tutorial Index
 |series=Основы работы с SKSE

@@ Строка 3: / Строка 3: @@
 {{Tutorial Index
 |series=Основы работы с SKSE
-|chapter=1
+|chapter=2
 |Prev=SKSE - Приступаем к работе
 |Next=:Категория:Papyrus
 |espInitial=EmptyPlugin.esp
-|espCompleted=
+|espCompleted=-
 }}
 {{Incomplete}}

@@ Строка 1: / Строка 1: @@
 [[Category:Учебники]]
 [[Category:SKSE]]
 {{Incomplete}}
 = Что может SKSE? Возможности и ограничения =

@@ Строка 21: / Строка 21: @@
 = Знакомимся с SKSE =
 Now that you've settled into the development environment and you have a plugin that both compiles and runs in Skyrim, it's time to get familiar with what SKSE makes available to you and program away in C++.
-* If there already exists a function listed here that does something similar to what you're trying to do or works on the same type of objects, it's worth finding the corresponding Papyrus*.cpp file in the project and looking at the source to see how it works.
+* If there already exists a function listed [[:Category:SKSE|here]] that does something similar to what you're trying to do or works on the same type of objects, it's worth finding the corresponding Papyrus*.cpp file in the project and looking at the source to see how it works.
-*You might find yourself wanting to use Bethesda's native Papyrus functions in your SKSE plugin. For example, you might want to call AddItem on an ObjectReference. However, only a very limited set of the vanilla native Papyrus functions are available from within an SKSE plugin. The ones that are available you'll be able to find defined in skse\GameReferences.h. Some functions, like AddItem, are very complicated and hence difficult to decode so that we can call them in SKSE. You'll have to stick with calling these functions in Papyrus, or find a lower level way of doing the same thing in your SKSE code. All of the lines that look like this are bits of the Skyrim binary that haven't been decoded:
+* You might find yourself wanting to use Bethesda's native Papyrus functions in your SKSE plugin. For example, you might want to call AddItem on an ObjectReference. However, only a very limited set of the vanilla native Papyrus functions are available from within an SKSE plugin. The ones that are available you'll be able to find defined in skse\GameReferences.h. Some functions, like AddItem, are very complicated and hence difficult to decode so that we can call them in SKSE. You'll have to stick with calling these functions in Papyrus, or find a lower level way of doing the same thing in your SKSE code. All of the lines that look like this are bits of the Skyrim binary that haven't been decoded:
 <syntaxhighlight lang="cpp">
   virtual void    Unk_5C(void);
 </syntaxhighlight>

← Предыдущая		Версия 12:33, 10 февраля 2016
Строка 18:		Строка 18:
	Оба данных вызова функции, будь то консольная команда, или функция в Papyrus будут вызывать одну и ту же функцию в бинарном файле Skryim. В данном случае, SKSE has not bothered to decode the binary function for <code>kill</code> because it's already available in Papyrus, and you're going to have to call your SKSE functions in a Papyrus script anyway. Most of SKSE's efforts are focused on decoding functions that are not already available in Papyrus.		Оба данных вызова функции, будь то консольная команда, или функция в Papyrus будут вызывать одну и ту же функцию в бинарном файле Skryim. В данном случае, SKSE has not bothered to decode the binary function for <code>kill</code> because it's already available in Papyrus, and you're going to have to call your SKSE functions in a Papyrus script anyway. Most of SKSE's efforts are focused on decoding functions that are not already available in Papyrus.
	The reason for using SKSE is that it offers far greater performance and flexibility than Papyrus. It can expose game functionality that isn't already available in Papyrus. In SKSE, you have the full power of C++ behind you. In Papyrus, you're limited to the extremely weak capabilities of whatever Bethesda has already given you in Papyrus.		The reason for using SKSE is that it offers far greater performance and flexibility than Papyrus. It can expose game functionality that isn't already available in Papyrus. In SKSE, you have the full power of C++ behind you. In Papyrus, you're limited to the extremely weak capabilities of whatever Bethesda has already given you in Papyrus.
		+
		+	= Знакомимся с SKSE =
		+	Now that you've settled into the development environment and you have a plugin that both compiles and runs in Skyrim, it's time to get familiar with what SKSE makes available to you and program away in C++.
		+	* If there already exists a function listed here that does something similar to what you're trying to do or works on the same type of objects, it's worth finding the corresponding Papyrus*.cpp file in the project and looking at the source to see how it works.
		+	*You might find yourself wanting to use Bethesda's native Papyrus functions in your SKSE plugin. For example, you might want to call AddItem on an ObjectReference. However, only a very limited set of the vanilla native Papyrus functions are available from within an SKSE plugin. The ones that are available you'll be able to find defined in skse\GameReferences.h. Some functions, like AddItem, are very complicated and hence difficult to decode so that we can call them in SKSE. You'll have to stick with calling these functions in Papyrus, or find a lower level way of doing the same thing in your SKSE code. All of the lines that look like this are bits of the Skyrim binary that haven't been decoded:
		+	<syntaxhighlight lang="cpp">
		+	virtual void Unk_5C(void);
		+	</syntaxhighlight>

@@ Строка 16: / Строка 16: @@
 </syntaxhighlight>
-Both that console call and that Papyrus function will call into the same function in Skryim's binary. In this case, SKSE has not bothered to decode the binary function for <code>kill</code> because it's already available in Papyrus, and you're going to have to call your SKSE functions in a Papyrus script anyway. Most of SKSE's efforts are focused on decoding functions that are not already available in Papyrus.
+Оба данных вызова функции, будь то консольная команда, или функция в Papyrus будут вызывать одну и ту же функцию в бинарном файле Skryim. В данном случае, SKSE has not bothered to decode the binary function for <code>kill</code> because it's already available in Papyrus, and you're going to have to call your SKSE functions in a Papyrus script anyway. Most of SKSE's efforts are focused on decoding functions that are not already available in Papyrus.
 The reason for using SKSE is that it offers far greater performance and flexibility than Papyrus. It can expose game functionality that isn't already available in Papyrus. In SKSE, you have the full power of C++ behind you. In Papyrus, you're limited to the extremely weak capabilities of whatever Bethesda has already given you in Papyrus.