the PiPL.r (Plug In Property List) file was originally created to allow AE to get some info about plug-ins without loading them.
that was useful at the times where computers had 128mb of ram. nowadays it's mostly a nuisance for developers...
the values in the pipl must correlate to the values set in the plug-ins global setup call or an error message will be sent during the plug-in's launch saying theres a mismatch in the values. put a break point in the global setup function and you'll be able to see the numerical value being applied to the outfalgs and outflags2 vars. just copy these numerical values to the pipl, and you should be good to go.
just note that you must do a clean/rebuild for the change in the .r file to take effect, as the pipl_tool only generates a new .rc file when there isn't one already available. cleaning the solution removes the .rc file and forces a regenration.