Is it possible for the preferences in BAM to sync up with those in projects, much like the projects do?

As BAM lagged some projects to support CPU usage limit, I relied on the projects to change this parameter, but then I had to sync BAM up with them afterwards...

Thanks.

No, that's not possible. That's not the philosophy of centralized account managing. BAM! does a one time attempt to get the prefs from the projects: during account creation. After that, BAM! is the central point from where prefs are distributed.

BTW: BAM! does support the CPU usage limit.

I am sorry to hear that I would also like to see the preferences propagate normally to and from BOINCstats. To me it seems against the ease of use goals since you have to use a specific web site to set the preferences rather than any one and having it spread from there.

Another issue: BAM! allows you to go beyond the boundaries of the BOINC prefs. The project websites only allow 4 sets of prefs, where BAM! allows almost unlimited prefs, with custom names. Propagating prefs from a project to BAM! would overwrite the custom prefs.

I never have understood how that worked. If the projects don't allow the added perfs how do they get to the clients? I though BAM! pushed the perfs to the project where they were picked up by the client.

The projects understand multiple venues, just that the web interface only allows 4 different sets. The additional venues that are pushed to projects from BAM! migrate nicely to the host, unless the project's web interface has been used to modify any of the venues - then additional ones get lost.