Having to update MMF2 to 249 for flash build?

**N64Mario** · 28th November 2009, 05:07 PM

When the flash build is released (whatever day that will be), would that mean having to update MMF2 to the new builds currently in beta (249)? Or will the flash build be completely different update of its own?
My game currently has a list of its own group organization that use the 'unused' qualifiers 24-99 that I named. And from what I could tell, v249 replaces, or renames all unused 24-99 qualifiers into actually named uses of qualifiers. I fear it may cause a confusion in my game engine as with myself, if not any software confusion of the game built from v248 into v249. That is to say when I update to v249 for the flash build.

**Fanotherpg** · 28th November 2009, 07:04 PM

You still will have to update to 249, and Flash probably will be in 250.

**Yves** · 28th November 2009, 07:16 PM

In the Event Editor preferences in the build 249 there is a "Use old qualifiers" option. I suggest you install the build 249 and select this option.

**N64Mario** · 28th November 2009, 07:34 PM

Wait....... The flash build will be in an update v250 and not 249? Because 249 is what they are working on finishing now. At the same time working on the flash build. So I would think if they are working on these, that the flash build would be in v249 if an update is required.

Given the fact that we have to pay for the flash build anyway, in theory, I think the flash built add on could work as an update of its own without us having to update MMF2. Though if the flash build is going to be on a new build, may as well be under MMF3 for that matter, since we would have to pay for MMF3 anyway. X_X

**Pkeod** · 28th November 2009, 07:39 PM

You're thinking too hard about this, bro. Version numbers are largely irrelevant, and updating is a good thing.

**N64Mario** · 29th November 2009, 06:30 AM

Not if they are still going under BETA testing. I don't like updating to things that are still under development. There could be more bugs.

But that's not my point here. My point being is this. Maybe instead of packaging the flash build with an update to MMF2, the flash build update can be a totally separate update of its own. For example, MMF2 v248 users install the flash build update, and still have MMF2 v248. v249 users install flash build, and still use MMF2 v249.

Though I agree updating is good in most cases. But sometimes its best to wait until the development is done out of BETA before updating. That goes to say that if Clickteam decides to release the flash build one day, while v249 is still under BETA development.

**Pkeod** · 29th November 2009, 06:51 AM

Likely the Flash beta will install like the HWA beta is with a separate executable, so you have nothing to worry about. Do you make commercial products? If not then don't worry about the beta versions and use them! You'll likely find bugs and help out with development.

**Yves** · 29th November 2009, 07:14 AM

Not if they are still going under BETA testing. I don't like updating to things that are still under development. There could be more bugs.

The current beta version is very stable, we didn't release it sooner because there were some issues in the Java runtime, but the main program and PC runtime are safe. And now the Java issues have been fixed so we're going to release it officially.

For example, MMF2 v248 users install the flash build update, and still have MMF2 v248. v249 users install flash build, and still use MMF2 v249.

That's not possible, sorry. The Flash runtime will install a new build (either a slightly modified version of the build 249, or the build 250).

Yves.