The Powder Toy Portable 91.0.324 has been released. The Powder Toy is a game of physics and fluid mechanics. You can play with different materials whose properties and influences are simulated. And it has explosives! It's packaged in PortableApps.com Format so it can easily integrate with the PortableApps.com Platform. And it's open source and completely free.
Update automatically or install from the portable app store in the PortableApps.com Platform.
Features
Have you ever wanted to blow something up? Or maybe you always dreamt of operating an atomic power plant? Do you have a will to develop your own CPU? The Powder Toy lets you to do all of these, and even more! The Powder Toy is a free physics sandbox game, which simulates air pressure and velocity, heat, gravity and a countless number of interactions between different substances! The game provides you with various building materials, liquids, gases and electronic components which can be used to construct complex machines, guns, bombs, realistic terrains and almost anything else. You can then mine them and watch cool explosions, add intricate wirings, play with little stickmen or operate your machine. You can browse and play thousands of different saves made by the community or upload your own – we welcome your creations!
Learn more about The Powder Toy...
PortableApps.com Installer / PortableApps.com Format
The Powder Toy Portable is packaged in a PortableApps.com Installer so it will automatically detect an existing PortableApps.com installation when your drive is plugged in. It supports upgrades by installing right over an existing copy, preserving all settings. And it's in PortableApps.com Format, so it automatically works with the PortableApps.com Platform including the Menu and Backup Utility.
Download
The Powder Toy Portable is available for immediate download from the The Powder Toy Portable homepage. Get it today!
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Comments
updater
Insstalls, then when I check fo rmore updates it re installs same Powder Toy
Fixed
depp.jones had an odd package version on it I'd missed. It's fixed now.
Oops, what happened? I
Oops, what happened? I checked my package and it should have a package version of 91.0.0.0. That should properly update the old version (89.0.0.1) and stay there. Is there something wrong with that? What was the fix?
The display version is a combination of the release version and build number (they started that a while ago). The folks at powdertoy do some 'silent' updates from time to time. They state the download to be 91 build 323, but in the downloaded build is 324. That is the version of the source code a well.
Package and Display
Package and Display versions are always equal unless there are extenuating circumstances. I don't even check package versions for apps going out. The updater database had the package version as 91.0.324.0, which would be expected with a display version of 91.0.324. So, once a user updated, and had a package version of 91.0.0.0, the updater would still think there was an update indefinitely until I adjusted the database to use the odd 91.0.0.0 package version.
As a general rule, the package version is a simplified version of the display version but should match. 91.0.324 would become 91.0.324.0. Firefox 45.0.1 has a package version of 45.0.1.0. An app with a version like 9.01 would be 9.1.0.0. The only ones that are a little odd are letters. Those are treated as the next digit. So, 2.45a would be 2.45.1.0. That way when 2.46 is released (which should be greater), it has a package version of 2.46.0.0 which is greater than 2.45.1.0.
Ok. I'll do it that way with
Ok. I'll do it that way with the next updates. I changed to the odd display version when the folks at powdertoy started using the build number for versioning. I kept the old package numbering for consistency reasons.
We had the display and package version the same before, as the build number was not used for public builds but only in the source code.
I'll adapt the package number the next time. I think it should not interfere with updates as the digits in front will be increased, too.
4 value versioning
It could get fun though if a base app uses all 4 values in the base app, and we have to use a rev 2 or higher, and then the base app number on update is less than our rev version...
Although I don't recall this happening, it's a possibility.
It Happens
It happens with Chrome and some other apps that insist on the non-user-friendly 4 value versions sometimes. So version 1.2.3.4 of an app has a package version of 1.2.3.4. And then we do a revision. The last digit gets multiplied by 10 in that case. So 1.2.3.4 Rev 2 has a package version of 1.2.3.42. Version 1.2.3.5 of the app would then have a package version of 1.2.3.50 to ensure updater integrity.
Have you considered using 5 value versioning for PackageVersion?
As the only thing that ever uses the PackageVersion is the updater, I wonder if it would be feasible to add a 5th value. Are there any drawbacks, other than that (
AFAIK) nobody else uses 5 value version numbers?Not Permitted
The PackageVersion is used in the actual installer as well which only permits 4 position valid numerical values. There's no real need for it anyway.