Advice for Scripting - Revision history

TiMan at 09:33, 21 August 2020

2020-08-21T09:33:05Z

Mudbill: /* Listen to error messages */ typo

2020-08-13T21:46:22Z

Listen to error messages: typo

Mudbill: better flow

2020-08-13T21:45:37Z

better flow

Mudbill: Added a section for "reference" and "errors"

2020-08-13T21:40:47Z

Added a section for "reference" and "errors"

TiMan: Created page with "This article is designed to give beginners the right mindset of approaching scripting and programming in HPL. Remember that these are just tips intended to help you – you do..."

2020-08-13T21:07:19Z

Created page with "This article is designed to give beginners the right mindset of approaching scripting and programming in HPL. Remember that these are just tips intended to help you – you do..."

New page

This article is designed to give beginners the right mindset of approaching scripting and programming in HPL. Remember that these are just tips intended to help you – you don't have to follow them, but they may teach you something useful.

@@ Line 1: / Line 1: @@
 This article is designed to give beginners the right mindset of approaching scripting in HPL. Remember that these are just tips intended to help you – you don't have to follow them, but they may teach you something useful.
-==Use references==
+==Use References==
 If you are stuck trying to write a script, don't forget that you can always use Frictional's map scripts as a reference. They may help by giving concrete examples how you may use certain functions. This is particularly useful if you need to figure out how to set up a particular sequence of events that you remember from the game, for example how to set up a crowbar for use on a door along with effects, as is done in the Guest Room of [[HPL2/TDD|Amnesia – The Dark Descent]].
-==Listen to error messages==
+==Listen to Error Messages==
 If you get a visible error message, perhaps as a pop-up in-game or as a crash message, they always provide ''some'' hints as to where the issue lies. If you see something like <code>(123, 10)</code> that means the [[wikipedia:Compiler|compiler]] (which is responsible for changing your human-readable code into computer readable instructions) failed to process your script, and the numbers point to where in the script file the processing started to fail. The first number represents the line number in your file, and the second number represents the character on that line. The example above then means the problems starts on line 123 and character 10.
 Sometimes the numbers you see will simply point to the last line and character in your file. This often means that there is a required character missing somewhere, like a double quote for a string. The reason it gives you the final character is because, according to the compiler, the string never ends, and the code that is wrongfully included in that string is only considered as a string, rather than a piece of code. Thus, the compiler doesn't know that there are any problems until it discovers that the file ends before a closing quote is found. This kind of compiler error is usually accompanied by a message along the lines of <code>Expected "</code>.

← Older revision		Revision as of 21:46, 13 August 2020
Line 7:		Line 7:
	If you get a visible error message, perhaps as a pop-up in-game or as a crash message, they always provide ''some'' hints as to where the issue lies. If you see something like <code>(123, 10)</code> that means the [[wikipedia:Compiler\|compiler]] (which is responsible for changing your human-readable code into computer readable instructions) failed to process your script, and the numbers point to where in the script file the processing started to fail. The first number represents the line number in your file, and the second number represents the character on that line. The example above then means the problems starts on line 123 and character 10.		If you get a visible error message, perhaps as a pop-up in-game or as a crash message, they always provide ''some'' hints as to where the issue lies. If you see something like <code>(123, 10)</code> that means the [[wikipedia:Compiler\|compiler]] (which is responsible for changing your human-readable code into computer readable instructions) failed to process your script, and the numbers point to where in the script file the processing started to fail. The first number represents the line number in your file, and the second number represents the character on that line. The example above then means the problems starts on line 123 and character 10.

−	Sometimes the numbers you see will simply point to the last line and character in your file. This often means that there is a required character missing somewhere, like a double quote for a string. The reason it gives you the final character is because, according to the compiler, the string never ends, and the code that is wrongfully included in that string is only considered as a string, rather than a piece of code. Thus, the compiler doesn't know that there are any problems until to discovers that the file ends before a closing quote is found. This kind of compiler error is usually accompanied by a message along the lines of <code>Expected "</code>.	+	Sometimes the numbers you see will simply point to the last line and character in your file. This often means that there is a required character missing somewhere, like a double quote for a string. The reason it gives you the final character is because, according to the compiler, the string never ends, and the code that is wrongfully included in that string is only considered as a string, rather than a piece of code. Thus, the compiler doesn't know that there are any problems until it discovers that the file ends before a closing quote is found. This kind of compiler error is usually accompanied by a message along the lines of <code>Expected "</code>.

@@ Line 1: / Line 1: @@
 This article is designed to give beginners the right mindset of approaching scripting in HPL. Remember that these are just tips intended to help you – you don't have to follow them, but they may teach you something useful.
-== Use references ==
+==Use references==
 If you are stuck trying to write a script, don't forget that you can always use Frictional's map scripts as a reference. They may help by giving concrete examples how you may use certain functions. This is particularly useful if you need to figure out how to set up a particular sequence of events that you remember from the game, for example how to set up a crowbar for use on a door along with effects, as is done in the Guest Room of [[HPL2/TDD|Amnesia – The Dark Descent]].
-== Listen to error messages ==
+==Listen to error messages==
 If you get a visible error message, perhaps as a pop-up in-game or as a crash message, they always provide ''some'' hints as to where the issue lies. If you see something like <code>(123, 10)</code> that means the [[wikipedia:Compiler|compiler]] (which is responsible for changing your human-readable code into computer readable instructions) failed to process your script, and the numbers point to where in the script file the processing started to fail. The first number represents the line number in your file, and the second number represents the character on that line. The example above then means the problems starts on line 123 and character 10.
-Sometimes the numbers you see will simply point to the last line and character in your file. This often means that there is a required character missing somewhere, like a double quote for a string. That is because, according to the compiler, the string may start at one point in the script but without the closing quote, it never ends, and the code that is wrongly included in that string is only considered as a string, rather than a piece of code. Thus, the compiler can't know exactly where the issue is. This kind of compiler error is usually combined with a message along the lines of <code>Expected "</code>.
+Sometimes the numbers you see will simply point to the last line and character in your file. This often means that there is a required character missing somewhere, like a double quote for a string. The reason it gives you the final character is because, according to the compiler, the string never ends, and the code that is wrongfully included in that string is only considered as a string, rather than a piece of code. Thus, the compiler doesn't know that there are any problems until to discovers that the file ends before a closing quote is found. This kind of compiler error is usually accompanied by a message along the lines of <code>Expected "</code>.

← Older revision		Revision as of 21:40, 13 August 2020
Line 1:		Line 1:
−	This article is designed to give beginners the right mindset of approaching scripting ~~and programming~~ in HPL. Remember that these are just tips intended to help you – you don't have to follow them, but they may teach you something useful.	+	This article is designed to give beginners the right mindset of approaching scripting in HPL. Remember that these are just tips intended to help you – you don't have to follow them, but they may teach you something useful.
		+
		+	== Use references ==
		+	If you are stuck trying to write a script, don't forget that you can always use Frictional's map scripts as a reference. They may help by giving concrete examples how you may use certain functions. This is particularly useful if you need to figure out how to set up a particular sequence of events that you remember from the game, for example how to set up a crowbar for use on a door along with effects, as is done in the Guest Room of [[HPL2/TDD\|Amnesia – The Dark Descent]].
		+
		+	== Listen to error messages ==
		+	If you get a visible error message, perhaps as a pop-up in-game or as a crash message, they always provide ''some'' hints as to where the issue lies. If you see something like <code>(123, 10)</code> that means the [[wikipedia:Compiler\|compiler]] (which is responsible for changing your human-readable code into computer readable instructions) failed to process your script, and the numbers point to where in the script file the processing started to fail. The first number represents the line number in your file, and the second number represents the character on that line. The example above then means the problems starts on line 123 and character 10.
		+
		+	Sometimes the numbers you see will simply point to the last line and character in your file. This often means that there is a required character missing somewhere, like a double quote for a string. That is because, according to the compiler, the string may start at one point in the script but without the closing quote, it never ends, and the code that is wrongly included in that string is only considered as a string, rather than a piece of code. Thus, the compiler can't know exactly where the issue is. This kind of compiler error is usually combined with a message along the lines of <code>Expected "</code>.