PDA

View Full Version : When you burn Wii/GC games, do you always apply the BrickBlocker?


transcended
08-09-2007, 01:34 AM
Simple topic. I've just installed my Wiikey today and will begin to burn games tomorrow. I know you simply burn the ISO at a low speed, about 4x. But do you always apply the WiiBrickBlocker?

If I have the newest firmware version 3.0U would I automatically be protected from any game? I know Mario Chargers and Super Paper Mario had problems based on my search. Do you just keep track of what games have this auto-update feature or just BrickBlock every iso you burn? Thanks!

BlackDove
08-09-2007, 05:37 AM
It's only needed for new foreign titles.

fillup
08-09-2007, 11:21 AM
It wouldn't hurt. Unless there are negative consequences I'm not aware of.

BlackDove
08-09-2007, 11:48 AM
There wouldn't be any, but if the game is from your console's region then the update is harmless.

duros
08-09-2007, 12:01 PM
It wouldn't hurt. Unless there are negative consequences I'm not aware of.
There is no point applying brick blocker to GC games whatsoever.

emoray
08-09-2007, 07:04 PM
makes no difference.

flo1983
09-12-2007, 07:51 AM
i have another question, similar to this one. I also have the newest (european) firmware version 3.0E. However, i am not automatically protected from any game. when i try to play a PAL game, even if it's old, it will tell me it wants to install an update. i'm not going to try that, so i can't play the games. do you guys know what it is and what i can do about it?

transcended
09-12-2007, 06:14 PM
Aren't PAL games the European version? Because if it is in your format, there is no worry about doing the auto-update.

Regardless of the above statement, I do know this about the updates:
If you apply the brick blocker and burn the game, and the game doesn't boot properly, you must update.

Atleast that's how it went with Metroid Prime 3 for me on my native format of NTSC. I still applied the brick blocker, but it wouldn't load... I guess it had some sort of mini-update. I reburnt w/o the blocker, updated, and all was well... but once again, this was in my native NTSC format.