Can you go into detail on this new API? We actually got unlucky and ended up with a legacy version of JOGL and are just now in the process of converting to GL2 (no shaders for now, so if the new API involves that, I'm out of luck for now.)
EDIT: Another unrelated yet equally frustrating bug:
Each of our "Text Data" wrappers has a color field as well as several others (scale, rotation, x, y) that we can adjust in our "dynamictext" via "velocities" that adjust the values of these fields over time.
When we use this to adjust the alpha of the color that is used to draw the image, weird stuff like the image above happens, almost as though calls to GL statements are being made under the hood that apply the changes to our text color to the rest of the rendering engine.
EDIT2: Seems like this bug actually isn't unrelated at all and that there's some quirk with the text renderer that prevents it from dynamically rendering multiple text objects with different colors in the same rendering cycle. Instead of having each text object manually modify its own alpha over time, we had one global color that the renderer would look at for each text, and we slowly changed this color instead and were successful.
Seems like we need multiple renderers or this new API!
It seems like they were unrelated after all. I now use Color.white for the first draw step in my render delegate that draws the glyph vector. apparently this was what was causing the color bug.
The alpha bug persists, however.
EDIT 4 (AKA I'm dumb.):
For anyone using a Color class implementation like Slick's or awt... Never use the static color object if you ever plan to alter it in any way. For the base case of "white damage" I was passing the actual reference to the static object in Color and then altering its alpha.... thus spelling doom for every other image in our game.