What's a good indication that a mod incompatibility report is going to be useless?

[DoomRater]

So far, each mod incompatibility report I've seen deals with a mod getting an NPE from FarPlane2. Are there any other indicators we should look for? Another common sign is that it's crashing on startup. before the game finishes loading.

Current mods that don't work with FP2 include Dynamic Trees, WebDisplays, and generally anything that needs to use the renderer in some nonstandard way. Phosphor will also nag endlessly about it if not told to shut up. I wouldn't mind having a list of mods that simply don't work over here.

[DaMatrix]

generally speaking, you should assume that everything other than the bare minimum dependencies (plus optifine) is incompatible for the time being. it'd probably be more interesting to have a list of mods that do work :P

[DoomRater]

Camera Mod and Armouer's Workshop are examples of mods that I would have thought would cause things to break, but apparently don't. In fact the entire list of mods after I removed WebDisplays (And the Chromium Embedded Framework, as that was only needed for WebDisplays) seemed to load just fine, including LittleFrames which can render YouTube pages on a LittleTiles surface. What I'd need to see is if loading a video on such a surface, then backing up such that it's only in view of a Farplane causes a crash.

[DoomRater]

I can now confirm WebDisplays now loads with FarPlaneTwo as of 0.0.1.552. This mod is getting wild.