i meant how is it harder to hack in big features like what problems do you encounter at first, how many extra files do you have to edit in comparison what makes it harder.

With vB3, you have to worry about all your phrases, new template engine, function files, cached data, etc. etc. etc.

larger hacks for vB3 take far more planning and consideration, compared to vB2. At first, it'll be a major headache to keep track of up to 5x as much data and files, but after a while, when you get experience with the new system, you'll find that you can do a lot more with less :) (more functionality with less file edits and the like).

hmm, i'm gonna have to look at a hack so i can see where someone else have done it before me and learn that way, sounds good tho :)

Once vB3 hacking is allowed here, you can go take a look at my Hack Tracking Log, for example. It's a fairly big hack, about 3500 lines of code (so far, not yet 100% done), 250 new phrases (I tried to be as efficient and reusable as possible ^_^), half a dozen new files, but only like.. 3 file modifications :) (and those three modifications prevent Countless new file modifications in the future, so they're REALLY very much worth their salt :D)

sounds good, hopefully this way i'll pick it all up and be able to find my way around hacking :)

Well, with the HTL and the Quality Assurance system both providing a lot of hacking guidelines, it should only be a matter of reading them and then trying them all out, by then. :)