Distribution strategy and incentives redux

Earlier on in my project planning I was attempting discussions on distribution incentives and I think I may have reached the point where I have to plan accordingly thereof (primarily because achievement journal) and I may be stuck on the new macOS expansion because of this. Not sure if the decision to include journal tracking is 100% to blame, however I just noticed during the initial process of the port job (as I finally decided to break down and get myself a Mac of my own) that I had a broken game off my first such build, and because I'm using an integration plugin for which I suspect that I may have a problem I obviously need to rule out the possibility thereof. It's not confirmed yet as I'm visiting family (because reasons) however if so I will either be duplicating my journal update mechanism (meaning two or three common events based on targeted services) or duplicating the game itself.

Anyway, this brings up the purpose of my question. As neither of these is going to be an ideal situation I'm obviously going to have to determine the best way to proceed thereof, and in a way that minimizes overhead (and deployment across multiple distribution services). This is specifically regarding these incentives and the related network integration materials (plugins, commands etc.) Primarily this is for GameJolt as my first such target, but in the case of my journal entries the same applies equally to distribution on Steam.

I will of course be following up with screenshots in the support section when I get a chance to do so (as this is literally my first time dealing with multiple distribution targets) but in the meantime I am going to require some Ideas on how to plan for this change.

EDIT: Due to a lack of time I had to leave the Mac set up for 1.6.1 which may also be a possibility for having this problem. So obviously I'm gonna have to verify this.