With cordite in the air, splintered steel, shell casings and powder burns, there’s only one explanation...
Everything about Smokin' Guns releases

Moderators: Tequila, torhu

Making sure old versions can't get in 1.1

Postby dbozan99 » Sat Dec 12, 2009 7:05 am

When 1.1 is released and everybody's server gets updated, 1.0 1.1b1 1.1b2 etc... shouldn't be allowed into 1.1 servers.
Perhaps with a nice notification that says something like "A New Version has been released! Go to smokin-guns.org to get it!" whenever somebody tries to connect to one with the old version...
User avatar
Posts: 43
Joined: Thu Jan 22, 2009 5:14 am

Postby Tequila » Sat Dec 12, 2009 10:47 am

Few points:
* engine 1.0 doesn't support the new QVM format from ioQuake3 SDK so you definitively can't use new PK3 since v1.1b1 with SG 1.0 engine
* As far as sg_pak1.pk3 is updated, you won't be able to connect on updated online servers unless you have auto-download feature activated on server and on client (like it is on current beta servers). When autodownload is activated, your PK3 is auto-updated to latest version. If client didn't activate auto-download, he will fail to connect with a pretty and clear message.

Btw the binary itself from previous beta could be used, but this is up to the client to update this program. And you should know we have activated "update" and "authorize" server tools, so we should be able to help admins to reject not up to date clients if it's really important.

Not updating engine is less critical than not updating PK3. This will essentially mean you won't benefit from features like FBO effects (bloom & rotoscope) is you don't have at least v1.1b3 engine... Updated engine means essentially better engine features support.

So don't worry
User avatar
SG Team
Posts: 1095
Joined: Thu Nov 15, 2007 11:33 pm
Location: Montpellier, France

Return to Release

Show Sidebar
Show Sidebar

User Control Panel