[feldon23]

Jawelin originally said:
This reason, main problem I can see from here now is : what would be the behavior of vbhacker dealing with already hacked code it doesn't recognize when searching for text to replace ?
Increasing the number of blinded-eye installed hacks, I fear the number of unexpected (unpredictable) LOCs by the single n-number hack (because it couldn't know the n-1 hacks installed before...) could increase exponentially.

It gives you a very clear, nicely done error report telling you which pieces could not be installed.

I think the key here is try to make the matchtext as short as possible, so that one hack is less likely to render another hack uninstallable.

If there's one thing that's missing, it's the ability in the script to set which # occurrence of a certain string to match and replace.

For instance, the Quick Reply box. I only like it at the bottom. There's no easy way to make vbHacker find which occurence you want to change.