Title: VM in PK3 Post by: fromhell on March 23, 2012, 06:19:06 AM For future versions should I still pack the VM in the pk3 or just keep it external?
Debian would probably most likely pick "no" here. but the way Q3 did things they usually had them in pk3s for protection and enforcing everyone played with the same game code Title: Re: VM in PK3 Post by: Gig on March 23, 2012, 07:06:46 AM Excuse me, could you please write "Pros" and "Cons" of that?
Keeping them in PK3s seems "natural" for me, because PK3s are the only files that clients can autodownload... I don't even know if a VM outside pk3s can be actually loaded when using a "pure" server... What would be the advantage of doing it differently? And how would that affect compatibility? Title: Re: VM in PK3 Post by: sago007 on March 23, 2012, 01:33:41 PM The ability to pack a game or mod as data and have all the benefits of compatibility checks performed by the engine seems like something I would hate to loose.
One could offer a way to overrule the vm file in the pk3-file but the pk3 file should always contain the safe pk3 (the one with guarantied compatibility). Debian already have an alternative way to find a compatible so-file to load. |