Differences

This shows you the differences between two versions of the page.

--- create_your_first_cartridge [2013/05/25 13:46] – external edit 127.0.0.1
+++ create_your_first_cartridge [2016/06/25 11:03] (current) – [Uploading media files] Boettchers
@@ Line 3: / Line 3: @@
   * I sugest to open the table of contents that is located to the top right of this statement. It will help you to locate information in the tutorial.
-  * You can use the Wiki search to locate topics in the whole Wiki. It is located in the top right corner, below the "EARWIGO WIKI" banner.
+  * You can use the Wiki search to locate topics in the whole Wiki. It is located in the top right corner.
   * You can also use the search function of your browser. Use CTRL F to search for keywords on the current page. The search field will pop up above (IE) or below (FF) the main text window.
@@ Line 276: / Line 276: @@
 ==== Uploading media files ====
+=== Image format ===
+Wherigo Players will not display all image formats. The safest way is to stick to jpg images.
+  - Make sure that the images are .jpg or .jpeg and NOT .png
+  - Use an application to remove all EXIF (Exchangeable Image File Format) data from photos and pcitures
+  - Software that will do the trick PC: IrfanView, Mac: ImageOptim
 === Copyright side note ===
@@ Line 683: / Line 690: @@
 === Message Button Event ===
-The buttons are handled on the Events tab of the message. Since we are only using one button we can use the button event without the need to check for the pressed button. Since there is only one butto the Event “When a button is pressed” is always invoked by our “OK, I will go back” button. We will react on this button by presenting the direction to the bridge (which is our Zone “Start”) to our human player.
+The buttons are handled on the Events tab of the message. Since we are only using one button we can use the button event without the need to check for the pressed button. If there is only one button the Event “When a button is pressed” is always invoked by our “OK, I will go back” button. We will react on this button by presenting the direction to the bridge (which is our Zone “Start”) to our human player.
 {{:create_your_first_cartridge:buttonevent.jpg|}}
@@ Line 689: / Line 696: @@
 You might be wondering why we have not used the more convenient Wherigo command: “Show_a_screen Zone:Start”. Good thinking but due to a Garmin bug this is not a good idea. Since we want to keep our cartridge usable for all players we have used a slightly different approach to ensure the cartridge will work on all devices.
-Only one Show_a_screen command is save to be used on all devices. It is the command “Show_a_screen Standard_screen:Main”. This command will show the home or main menu page. The home page will not directly guide the human player back to the starting position but we can point him towards it with a little extra work. The idea is to present a message with instructions followed by the “Show_a_screen Standard:Main” command. If you have a look at the “ToLateToTalk” message you can see that we have already provided the required extra information for the human player. All we need to do now is to present the main menu and hope that the player can find the described page (they typically do ;-)
+Only one Show_a_screen command is safe to be used on all devices. It is the command “Show_a_screen Standard_screen:Main”. This command will show the home or main menu page. The home page will not directly guide the human player back to the starting position but we can point him towards it with a little extra work. The idea is to present a message with instructions followed by the “Show_a_screen Standard:Main” command. If you have a look at the “ToLateToTalk” message you can see that we have already provided the required extra information for the human player. All we need to do now is to present the main menu and hope that the player can find the described page (they typically do ;-)
 ===== Backup of your cartridge =====
@@ Line 764: / Line 771: @@
 ===== If Else EnfIF Statements =====
-[[create_your_first_cartridge#ToDo_List|ToDo List 6)]]
+[[Quick_and_dirty_IF_Then_Else_Intro|(the quick and dirty IF Then Else intro can be found here)]]
+[[create_your_first_cartridge#ToDo_List|(ToDo List 6)]]
 Item 6 on the ToDo list is to enable the Zone "Tree". I know that you can enable Zones by now (	Set_value Zone:Tree:Active => true) but this time we have to remember a condition. We have started the last 5 sections of this tutorial because we need to built an IF ELSE EndIF Statement. You might want to [[create_your_first_cartridge#Decisions_(Continued)|read this section again]] to remember what we intend to achieve.
@@ Line 949: / Line 958: @@
   * Use this command to display the previously created [[create_your_first_cartridge#Displaying the completion code|completion code message]]
-You might be curious why I am using a command and a message to display this information. The item description looks like a much easier way to do this without all the trouble of creating commands and messages. This is actually a good question and if you have really asked yourself something along this line I think you are ready to put your own cartridges out there ;-). Coming back to the question: the item description is created together with the item itself when the cartridge is started for the first time. At this time the cartridge is still incomplete and there is no completion code available. If you display a message however this will look up the current value of any variable (for example Player.CompletionCode) and display it to the human player.
+You might be curious why I am using a command and a message to display this information. The item description looks like a much easier way to do this without all the trouble of creating commands and messages. This is actually a good question and if you have really asked yourself something along this line I think you are ready to put your own cartridges out there. ;-) Coming back to the question: the item description is created together with the item itself when the cartridge is started for the first time. At this time the cartridge is still incomplete and there is no completion code available. If you display a message however this will look up the current value of any variable (for example Player.CompletionCode) and display it to the human player.
 == Presenting the "Completion code" item at the end of the game ==
@@ Line 956: / Line 965: @@
   * Save the cartridge
   * Inform the player about his new item
+=== Testing the "Completion Code" ===
+The emulator and the test compilations will not have a working completion code in it. You will see a dummy code "completion code".
+This is the theory behind it: The completion code is connected to the human's GS player account and can only be used by this account. If you get the code from someone else, you can not mark a cartridge as completed. The test run and compilations will not create a valid useable code.
+Should you really desire to see a working completion code, this is how to get there:
+  - Upload the cartridge to GS www.wherigo.com
+  - Secretly publish the cartridge (invisible, not referenced in search engine)
+  - Download this published cartridge with your own GS player account
+If you run the resulting *.gwc in the emulator things should work out as expected (I would not really do this because I have done it once and I now believe that it works. ;-)
 ==== Uploading your cartridge to wherigo.com ====