Create Build Numbers

Is there a way to stamp a build with a unique number? I deploy a lot to a web server, but as we know, sometimes it caches a little and the older version loads. Without a number, I can't tell if I'm working on the latest. Any thoughts on this?

Hate to be a bumper....Not looking for a real silver bullet here, just curious if anyone else ran into this.

Just hardcode it into the game? Put a text object that shows a build number you've manually entered into the text object.

I understand that is an option. I'm just curious is anyone had real automated solutions. In my C# world, this is handled inside a TFS build process template...Just thought it's one cool thing to help devs who iterate a lot with testers.

The other thing, as games get more professional, things like beta access becomes important and you really need to have a nice build system at that point.

I still see no need whatsoever for an automated solution for this.

You're already inside Construct editing the code when making changes. Thus correcting "Build 1234" to "Build 1235" on a piece of text/variable before you save/export shouldn't be that difficult.

You can use the "Version" project property, can't you ?

And as Xionor mentioned, display it in a text object or log into the console browser using the "projectversion" system expression.

You can use the "Version" project property, can't you ?

And as Xionor mentioned, display it in a text object or log into the console browser using the "projectversion" system expression.

I understand that as well. In more complex IDE's though, every time you hit export/build, there is a number that is incremented by either process templates in TFS or a script in the IDE, starting at 1000. you hit build, it becomes 1001. so your version # is 1.0.1001. I'm just used this being an option in .Net.

If I'm building twice daily, this is nice because if a tester comes in on saturday, he wants to test the latest, there are now 14 builds he can pick from since you built twice daily.

I understand to most developers this isn't a problem, but I think this something modern, larger scale projects must deal with.

If I'm building twice daily, this is nice because if a tester comes in on saturday, he wants to test the latest, there are now 14 builds he can pick from since you built twice daily.

I understand to most developers this isn't a problem, but I think this something modern, larger scale projects must deal with.

I personally took the habit to change that number on a regular basis when saving a new capx of my projects. Believe it or not, it's often far more than twice on a daily basis.

Don't mix the scale of projects and the renown laziness of developers <img src="smileys/smiley2.gif" border="0" align="middle" />

On a more serious note though, I think this had already been brought up, I'm not sure if it's on Ashley's todo list though.

A "build" property that would get iterated on export, maybe that's something quick that could get into a future release. But I'm not sure where/how you could display this.

This would probably be a value stored inside the .js file and would require you to keep a solid hierarchy/folder structures of your exports.

Until/if it's implemented, I strongly suggest to resort to updating the "Version" property by yourself though.