Introducing codename “Paq”. The Synq package and collection index

Read the full story over at http://play.withsix.com/posts/98-introducing-codename-paq-the-synq-package-and-collection-index

Introducing codename 'Synq', our new distribution tech

Read the full story over at http://play.withsix.com/posts/97-introducing-codename-synq-our-new-distribution-tech

TL-DR:

• New distribution technology nearly ready for release
• Multiple versions for mods now supported; e.g latest ACE stable, or dev, or e.g specific build 591
• You choose which version or branch (stable/dev/etc) you wish to use, and how many you wish to keep
• Saves diskspace and bandwidth, while still allowing quick switching between versions
• Still uses delta patching; only download changed bits when updating, saving time and bandwidth

Play withSIX news and info

As of recent, all information and news regarding Play withSIX,
the official replacement to the critically acclaimed SIX Updater and Launcher applications,
has moved to the official page: http://play.withsix.com  (news: http://play.withsix.com/posts).

No longer will blog posts about Play withSIX be posted on this (SIX Updater), page.
At some point the pages on this site will probably be redirected to the withSIX.com domain as well.

SIX Updater hotfixes released!

After more than 6 months, two new hotfixes have been released for SIX Updater, addressing game/mod version comparison issues and compatibility issues with Namalsk/Taviana, and their DayZ variants.

These should hopefully be the last updates to either SIX Updater or Launcher,
in anticipation of the Play withSIX replacement.

Play withSIX build 190 released - merry x-mas!

Play withSIX build 190 has been released,
see the release post over at Play withSIX.com for details.

ARMA 2 OA Build 100.000+, and JayArma2Lib

This mostly affects SIX Updater users.

Due to a bug in SIX Updater, the following symptoms could be experienced:

• @JayArma2Lib is activated instead of @JayArma2Lib_new
• Current game version (left down) is shown in Red because SU thinks the game version is older than the latest available version

The former issue is no problem - @JayArma2Lib and @JayArma2Lib_new are now identical.

We will deprecate @JayArma2lib2_new, and remove it a while after OA 1.63 patch release.

The latter issue is caused by how Ruby compares string build numbers. It is only cosmetical and will fix itself after OA 1.63 patch release.

Play withSIX several major updates

Several major updates have been released in the past few weeks:

• http://play.withsix.com/posts/84-play-withsix-build-166-released
• http://play.withsix.com/posts/83-play-withsix-build-160-released
• http://play.withsix.com/posts/82-play-withsix-build-148-released

Also it appears we've squashed the main issues surrounding the installer and the self update process,
as of build 170 and later, the experience should be much improved on next and subsequent updates.
http://getsatisfaction.withsix.com/withsix/topics/sorry_and_thankyou_pages_are_shown_on_major_upgrade_types#reply_10744178

Fingers crossed ;)