If you'd like to support our preservation efforts (and this wasn't cheap), please consider donating or supporting us on Patreon. Thank you!
Bookworm Adventures Volume 2
Bookworm Adventures: Volume 2 |
---|
Developer:
PopCap Games
|
To do: Decompile the LUC files, there's more in them, they are compiled with LUA 5.0.2 but likely stupidly headered. |
Bookworm Adventures: Volume 2 is a sequel to the previous word-based Bookworm RPG from three years before. It's more of the same pretty much, except when EA purchased PopCap, at some point in 2016 they just decided to randomly delist all sales of the Bookworm series and pretend it never existed.
This game has been through a bit, is what we're saying.
Contents
Debugging Material
To do: Enable this if possible. |
Developer Cheats
scripts/cheat.luc appear to have developer cheats, functions are modify HP, level up, modify XP, instant kill, complete chapter, complete book, modify tile architectures, set particles, nuke profile, status testing, load debug profile, add items, beatdown multiplier modifiers, die, save, get selected chapter, modify treasure count, bypass/repeating tutorials, give player+enemy buffs/debuffs, enabling minigames, enabling bestiary, delete words, forcing an attack, and hiding treasures.
The game also looks for this file on bootup.
Beta Support
Some files mention BETA_BUILD, this likely refers to builds distributed from PopCap's game beta testing page and is also a flag for what current build type is used when released to the public.
Crash Handler
If the game crashes, a popup saying Fatal Error will appear to report the crash and see a log. A file called crash.txt will be created or replaced in the game's root install directory, containing the exact same text from the error message box.
LUA Error Handler
If an LUA or LUC has an error like file missing or damaged, the game will say: Oops! A lua error occurred and the game needs to shut down. Please contact customer support and provide them with your lua.log file. It will be created or replaced in the game's root install directory.
Bad String Handler
To do: Where is this detected? The LUC/LUAs and/or plaintext data? |
If the game detects a bad string, this text from scripts/common.luc will show in red: Someone passed in a string with invalid characters. Probably because they forgot to save the file as plain text and it contains some specially formatted Word characters. This is bad. We can't render those. I'll let the program continue, but it may result in messed up text. This would probably be a bug for Steve if you get this. I'll let the program keep running though, as this is just cosmetic.
Cheat Detection
To do: What triggers this? Memory edits, developer cheats or both? Test. |
scripts/BattleEngine.luc mentions CHEAT and YOUCHEATED in flagging terms, the game would most likely detect the use of memory editing or some sort of cheat format and force your best and longest word to be CHEAT and YOUCHEATED, it would be impossible to get YOUCHEATED as your longest word during legal play since that word is not in the in-game dictionary.
Uncompiled LUA Files
scripts/common has few plaintext, uncompiled LUA files along with mostly compiled LUAs, the game also supports loading uncompiled LUAs and compiling them as LUCs with debug compile info on after reading, but prioritizes loading the compiled LUA files with the extension LUC first when possible.
Leftover Source Binding Files
main.pak/scripts has a leftover scripts.vssscc and MSSCCPRJ.SCC file, the name of it is capitalized.
scripts.vssscc
"" { "FILE_VERSION" = "9237" "ENLISTMENT_CHOICE" = "NEVER" "PROJECT_FILE_RELATIVE_PATH" = "" "NUMBER_OF_EXCLUDED_FILES" = "0" "ORIGINAL_PROJECT_FILE_PATH" = "" "NUMBER_OF_NESTED_PROJECTS" = "0" "SOURCE_CONTROL_SETTINGS_PROVIDER" = "PROJECT" }
MSSCCPRJ.SCC
SCC = This is a source code control file [scripts.lup] SCC_Aux_Path = "P4SCC#perforce:1666##anthony##AntLaptop" SCC_Project_Name = Perforce Project [scripts.sln] SCC_Aux_Path = "P4SCC#perforce:1666##anthony##AntLaptop" SCC_Project_Name = Perforce Project
Revision List
To do: Check other OEMs. |
- 1.0.4.8465 = Initial release!
- 1.0.6.2376 = Bug Fixes
Copy Protection
If you remove or rename properties/partner.xml from your installation of the game and use the extracted game executable from the wrapper to play, the keyboard and main in-game GUI other than the Pause and Scramble buttons will stop working after 2 seconds of gameplay. This affects the entirety of the in-game GUI and the keyboard. The pause menu also doesn't have the black background fade.
The Bookworm series | |
---|---|
Windows/Mac OS X | Bookworm • Bookworm Adventures • Bookworm Adventures Volume 2 |
Game Boy Advance | Bookworm |
Nintendo DS | Bookworm |
Cleanup > To do
Games > Games by content > Games with anti-piracy methods
Games > Games by content > Games with debugging functions
Games > Games by content > Games with revisional differences
Games > Games by content > Games with uncompiled source code
Games > Games by developer > Games developed by Electronic Arts > Games developed by PopCap Games
Games > Games by platform > Mac OS X games
Games > Games by platform > Windows games
Games > Games by publisher > Games published by Electronic Arts > Games published by PopCap Games
Games > Games by release date > Games released in 2009
Games > Games by series > Bookworm series