That's great, I also didn't know it existed. The only thing I need to check is if it will copy the updated values to the archived ipa.

The script runs only when you Archive.

Which happens when you run Instruments.

I had a project with this exact setup about a year ago... The amount of time lost resolving conflicts wasn't worth it.

In the post, there is a workaround for the increment at each build/run. You just need to be sure to run the script only in Release

Well I'd like to know build numbers internally, just only when I change things. So if I put build 12500 on 3 iPads, I can track the crashes.

What do you mean? Do you want to read the build number on runtime? There is a way to do that, when you put them in the plist, just run [[NSBundle mainBundle] infoDictionary][@"CFBundleVersion"] to get the NSString.

Say I have 3 iPads in the office, and I want to load a build on each of them. I know I can use Testflight or similiar, but the easiest is to just plug them into my computer and press the play button. If I do that, it increments the build number, so iPad #1 gets build 4031, iPad #2 gets build 4032, etc.

No it doesn't, if you ensure it will run only on "Release". When you deploy an app to a device via Xcode, unless you specify differently, it will compile in "Debug", so that won't cause an increment. Every iPad will have the same build.