These points above are indeed good examples regarding "forcing bad practices":

If I have 3 free API calls after the API call, after the 3rd freebie, I can return it and call again for 1 core + 3 more that can branch off again. This is inefficient for BC, yet beneficial for end-users (thus, forcing bad practices since it costs and gives more if we avoid the pre and post hooks).

If a workaround to save API costs would be more work for the user, and costs more for BC, that's a lose-lose. If such a "hole" exists, shouldn't it be repriced for that consideration to make it the win-win you folks want it to be?

Apologies to necro bump, but this seems quite relevant:

With the GameSparks doomsday clock, I know several folks skeptical about BC due to the lack of an API to upload code to (for local edits/testing).

I saw this was planned for Nov 2020: Was this ever implemented?

Thanks!

These points above are indeed good examples regarding "forcing bad practices":

If I have 3 free API calls after the API call, after the 3rd freebie, I can return it and call again for 1 core + 3 more that can branch off again. This is inefficient for BC, yet beneficial for end-users (thus, forcing bad practices since it costs and gives more if we avoid the pre and post hooks).

If a workaround to save API costs would be more work for the user, and costs more for BC, that's a lose-lose. If such a "hole" exists, shouldn't it be repriced for that consideration to make it the win-win you folks want it to be?

Seems like the practice I've read is to have 1 giant master script to save API calls. This encourages INCREDIBLY bad practice for the overall architecture for all devs (and makes senior devs that know not to do this cringe and scratch the wall as if watching a horror film).

How about finding a different way to charge users to compensate this? Perhaps merge it elsewhere - this wasn't even good practice in the geocities/angelfire days. This... is just unacceptable from a modern BaaS, in my professional opinion. Why are in-house API calls even charged extra at all? Shouldn't it just be from client to server -> Do as many calls as you want since you're charged per CPU anyway (iirc?) -> Return the final result.

For example, if I have to CallSteamAPI() and CallDiscordAPI() in ONE script, that's just really horrible practice ... but seems like BC users are forced to?

Hey folks,

There were 2 GS games we were considering porting to: Unfortunately, seems like the prices scale too steep. Whew: Even packing in all kinds of API calls into 1, it gets rough with a PC multiplayer game.

Any indie prices coming soon, or promos for migration from GS? It's a shame because BC is so similar to GS in terms of structure (from what I can see): I'd love to port to BC, but the prices ... they just don't seem scale indie-friendly.

Apologies to necro bump, but this seems quite relevant:

With the GameSparks doomsday clock, I know several folks skeptical about BC due to the lack of an API to upload code to (for local edits/testing).

I saw this was planned for Nov 2020: Was this ever implemented?

Thanks!