Because I have a specific goal in mind and I'm not sure how else to do it. I'm trying to extend the biome array, and by all appearances it's working perfectly. In order to make that accessible to mods while preserving vanilla-like functionality for those that don't understand the new biome structure, I need to implement new methods.
It's not vanilla-compatible and exhibits odd behavior with mods that attempt to change the current biome, so it isn't a candidate for inclusion in Forge. And I'm not so skilled at Java to be able to do it by ASM. (Besides, it would be royally difficult by ASM, whereas just changing what I need in Forge is comparatively easy.)
It's for personal use, and I don't intend to release it. If there's a really good reason I still shouldn't be doing it, and/or there's a better way of getting something similar, I'd be grateful if you could explain that, as I seem to have missed it.
But there's broader reason to want to build against modified Forge. I might be mistaken (it's entirely possible), but it seems to me there are other extremely valid reasons to build against custom Forge.
If I were adding a new Forge hook, especially given the tight quality control, I might want to build a test mod against custom-Forge to make sure everything was working properly.
If you can point me in a better direction, I'd be grateful to hear it, but even so it would be useful to know how to build against custom Forge.
Thank you for taking the time to help with this.