Cartridge Version History

5 (7/9/2018)

The iPhone app does not support "mi" as a unit, so I switched the final zone's distance determination code over to using meters.

4.9 (5/8/2016)

Updated the final coordinates for the NC version.

3.3 (6/3/2012)

TEST 3.3: This should be a steady state, somewhat. This removes tasks and setting item names. I ran out of time.

3.2 (6/3/2012)

TEST 3.2: Yeah, I cannot set an item's name. This test brings back creating tasks.

3.1 (6/3/2012)

TEST 3.1: I could *set* the names and descriptions. The crash occurs when the player sees the main screen. Odd... This test removes setting the item names to see what happens.

3 (6/3/2012)

TEST 3.0: I could set one name, so I'll try setting all three again.

2.9 (6/3/2012)

TEST 2.9: Item descriptions can still be modified. Now, about the name...

2.8 (6/3/2012)

TEST 2.8: Silly me; the tests for setting item names and descriptions were never called. This one will call a test set of an item description.

2.7 (6/3/2012)

TEST 2.7: Good. I can set descriptions. Now to test the name.

2.6 (6/3/2012)

TEST 2.6: gsub works. Perhaps I can't set an item's name?

2.5 (6/3/2012)

TEST 2.5: Does this mean string.gsub does not work? This is a test.

2.4 (6/3/2012)

TEST 2.4: Previous version crashed again. This test removes only CreateTasks() and SetAmmoDescriptions().

2.3 (6/3/2012)

TEST 2.3: The cartridge was playable if I ignored everything after CreateBattleships(). Let's start putting things back. First up is CreateTasks() because that might not have been the issue after all.

2.2 (6/3/2012)

TEST 2.2: Nope. This test is to see what happens if everything after CreateBattleships() is ignored. The next test will remove the RefreshLocation call.

2.1 (6/3/2012)

TEST 1.11: The iPhone Player still crashed when I used pcall to generate the tasks. Let's see what happens when I go without the tasks.

2 (6/3/2012)

TEST 1.10: It looks like the iPhone Wherigo Player cannot create tasks on the fly. Let's see if I can stick it inside of a pcall so I don't have to go without it on other devices.

4.5 (6/3/2012)

VERSION 4.5: Added a space in the completion code message.

4.4 (6/3/2012)

VERSION 4.4: Adjusted my secret item, Admin Control, so I can restock my ammo whenever I want. I use this item for testing purposes. You cannot ordinarily get this item into your inventory. I usually comment it out before publishing.

4.3 (6/3/2012)

VERSION 4.3: Release candidate for the final version. I can create tasks on the fly, but it must be piecemeal for the iPhone Player to work.

4.2 (6/3/2012)

VERSION 4.2: Trying to create a task on the iPhone...

4.1 (6/3/2012)

VERSION 4.1: Back to the drawing board on creating tasks...

4 (6/3/2012)

VERSION 4.0: The first release candidate after testing the Battleship game on the iPhone. I have updated my comments in the game's code, applied my fixes everywhere, and removed my testing code. After my testing, if this works, you won't see another update here.

3.9 (6/3/2012)

TEST 3.9: Yeah, gsub was failing on the iPhone because I was using an integer as an argument. This casts the integers as strings when setting the item's description. I also added back setting the item's name to see if the cartridge would crash (it shouldn't because I'm guessing it was crashing because an empty string was used for the item's name).

3.8 (6/3/2012)

TEST 3.8: Perhaps gsub fails because I'm passing an integer as an argument? Let's see what happens when I join an integer with a string before using it as a gsub argument.

3.7 (6/3/2012)

TEST 3.7: Okay, so using gsub FAILS on the iPhone. Let's see what happens if I require the string library at the top of the cartridge.

3.6 (6/3/2012)

TEST 3.6: Test fix: I can't see the test message box if I'm calling Wherigo.ShowScreen after it.

3.5 (6/3/2012)

TEST 3.5: I was able to set the item's description without using string.gsub. Now, I will do a test to show what I'm assigning as a description inside a message box. Perhaps this will explain why I'm not able to assign an item's name.

3.4 (6/3/2012)

TEST 3.4: Resuming testing. This time, I'm testing assigning an item description without using string.gsub to do my string formatting.

4.6 (11/16/2012)

Resolved a critical bug: a person could win the game by starting the game, saving it, closing the cartridge, and resuming it. This is because it is not possible to save all the game data upon closing. It might be possible to restore the lost data upon resume. I will look into that later. For now, I have made it impossible to resume the cartridge unless the final cache zone is active.

1.5 (2/8/2011)

1.4 (2/6/2011)

After some testing with the Garmin Oregon and PiGo, I discovered neither Player likes the print() statement: the Oregon will crash and PiGo will show "Not implemented" for each print(). Thus, this update comments out the print() statement.

1.3 (2/6/2011)

Oops. I misspelled the geocache zone. In the next update, I'll put the cache's coordinates in the description by not using text. I'm pressed for time right now, so can't do that.

1.2 (2/5/2011)

1.1 (2/5/2011)

I set the cartridge's settings back to where they were: shell damage radius and shell quantities. I then gave you two extra 37mm shells and one extra 75mm shell. Perhaps I'll make it less challenging after the FTF, but, for now, you'll have to play with the settings with which I field tested.

1 (2/5/2011)

4.7 (8/15/2013)

Added a cache in Nevada.

4.8 (11/7/2013)

An update to let Urwigo load the cartridge without any error messages. The error message Urwigo reported was because I was using comments within a new zone method. Although syntactically sound, I believe Urwigo rewrote the command upon parsing so that it understood it as one line. Once it was converted to one line, the comments commented out the rest of the line.

1.6 (7/30/2011)

Switched the code to use # instead of table.getn. Thank you, matejcik, for notifying me of the function's deprecation!

1.9 (6/3/2012)

TEST 1.9: Testing the StartGame() function with a bunch of MessageBoxes. I don't know if that's too sloppy or its fine just yet.

1.8 (6/3/2012)

TEST 2: Wondering if the print statement works on the iPhone so I can see where and when it is crashing.

1.7 (6/3/2012)

TEST: Trying to figure out why the iPhone Wherigo Player crashes. Its browser won't let me download from my own domains, so I have to upload here. During these tests, I've removed this cartridge from the directory so no one can access it.