I'm currently making my own private pack (154 mods). I have all ID conflicts solved and everything. I'm wondering how do I really test the pack for crash bugs, besides just playing? I'm asking because I decided to "just play" my modpack in single player and after loading a certain amount of chunks I was getting tiny lag spikes every couple of seconds. I'm wondering how I could locate and fix issues like that. (It's not my computer either. My computer is very capable). I have enough ram allocated and PermGen and everything else. I checked in the console and the only errors I was getting (besides the occasional "can't keep up" message which is only a short amount of time) were on these two lines:
2013-12-18 22:16:48 [WARNING] [IC2] can't expand chunkLazurite
2013-12-18 22:17:05 [FINE] [ForgeModLoader] The world 76ed2aac (Fun Survival) may have leaked: first encounter (5 occurences)
Even then, the "leaked" says fine.
I'm just wondering how I could fix that and test for other errors down the line without having to run into them on accident?
You should play it on a server to really test for bugs (certain kinds of bugs, like client-syncing, don't occur in SP).
If we assume that all of the mod authors thoroughly tested all of the individual components to their own mods, then all you really need to test is mod interactions. You could, for example, play on creative mode and build an example player home-base using as many of the new mod features as possible. Then switch to survival mode and spend an hour or two playing the game and using the base you made. Log out and back in while shooting projectiles and running machines to check for errors related to chunk unloading/loading.
Rollback Post to RevisionRollBack
My mods: Base Metals, Power Advantage, Steam Advantage, Electric Advantage, Minecraft Mineralogy, Dr. Cyano's Lootable Bodies, Dr. Cyano's Wonderful Wands & Wizarding Robes