[DiscordArchive] if you can do that without cascading changes it's not too bad i guess, but won't you limit yourself
[DiscordArchive] if you can do that without cascading changes it's not too bad i guess, but won't you limit yourself
Original source
if you can do that without cascading changes it's not too bad i guess, but won't you limit yourself with what files you can edit and/or how many updates you can make by doing that?
rektbyfaith
05-12-2022, 09:09 AM #1Archived author: <o> • Posted: 2022-05-12T09:09:22.098000+00:00
Original source
if you can do that without cascading changes it's not too bad i guess, but won't you limit yourself with what files you can edit and/or how many updates you can make by doing that?
Original source
Nope, I don't see why I would. You just split the installation files over X mpqs off Y size then there's an instruction list XML file that defines which MPQ each file is in, where to install it to, and the file size for verification
rektbyfaith
05-12-2022, 09:34 AM #2Archived author: stoneharry • Posted: 2022-05-12T09:34:22.633000+00:00
Original source
Nope, I don't see why I would. You just split the installation files over X mpqs off Y size then there's an instruction list XML file that defines which MPQ each file is in, where to install it to, and the file size for verification
Original source
The installer I'm working on will create a different structure to the blizzlike 3.3.5 client too, but it will be smaller because all unused data is removed. It's an experiment
rektbyfaith
05-12-2022, 09:38 AM #3Archived author: stoneharry • Posted: 2022-05-12T09:38:53.854000+00:00
Original source
The installer I'm working on will create a different structure to the blizzlike 3.3.5 client too, but it will be smaller because all unused data is removed. It's an experiment
Original source
do you automate the decision of what file goes in what mpq file as you package them on the server, or is this a clientside thing? I'm not sure i understand the role of your xml file here, that sounds like you've already decided where files go?
rektbyfaith
05-12-2022, 09:43 AM #4Archived author: <o> • Posted: 2022-05-12T09:43:01.930000+00:00
Original source
do you automate the decision of what file goes in what mpq file as you package them on the server, or is this a clientside thing? I'm not sure i understand the role of your xml file here, that sounds like you've already decided where files go?
Original source
I'm using the Blizzlike installer so it's not custom code. The installer comes with a exe and tome mpqs that hold the data. The mpqs are split over a fixed size. The first MPQ contains installer data such as artwork, audio, product data, localisation, and instructions. The instructions define which tome MPQ to extract from, and where to install them in the client destination. I'm going to automatically generate these instructions for the most part
rektbyfaith
05-12-2022, 09:45 AM #5Archived author: stoneharry • Posted: 2022-05-12T09:45:40.464000+00:00
Original source
I'm using the Blizzlike installer so it's not custom code. The installer comes with a exe and tome mpqs that hold the data. The mpqs are split over a fixed size. The first MPQ contains installer data such as artwork, audio, product data, localisation, and instructions. The instructions define which tome MPQ to extract from, and where to install them in the client destination. I'm going to automatically generate these instructions for the most part
Original source
that's cool, i think i misunderstood the point of your message. Splitting files across mpqs is of course possible and i'd say mostly advisable (we do this ourselves), regardless of how you distribute your patches granted you know what you're doing
rektbyfaith
05-12-2022, 09:52 AM #6Archived author: <o> • Posted: 2022-05-12T09:52:58.679000+00:00
Original source
that's cool, i think i misunderstood the point of your message. Splitting files across mpqs is of course possible and i'd say mostly advisable (we do this ourselves), regardless of how you distribute your patches granted you know what you're doing
Original source
but there are a lot of traps you can put yourself into depending on how big archives you decide to stuff things into that you may want to edit later
rektbyfaith
05-12-2022, 09:56 AM #7Archived author: <o> • Posted: 2022-05-12T09:56:37.810000+00:00
Original source
but there are a lot of traps you can put yourself into depending on how big archives you decide to stuff things into that you may want to edit later
Original source
Considering the amount of mpqs are currently used by the blizzlike client, I doubt this will be a massive issue. If we dedicate a set of files and internal structures to a set of mpqs, I can't see a way that this would lead to any space issues. It would also be easier to patch, as we always know what we're patching and where, which would make duplicate files a non-issue
rektbyfaith
05-12-2022, 10:08 AM #8Archived author: Foe • Posted: 2022-05-12T10:08:47.323000+00:00
Original source
Considering the amount of mpqs are currently used by the blizzlike client, I doubt this will be a massive issue. If we dedicate a set of files and internal structures to a set of mpqs, I can't see a way that this would lead to any space issues. It would also be easier to patch, as we always know what we're patching and where, which would make duplicate files a non-issue
Original source
With the blizzlike installer and patcher we can do incremental patching with only updating what's changed from a to b, and with static locations we'd eliminate duplicates entirely
rektbyfaith
05-12-2022, 10:10 AM #9Archived author: Foe • Posted: 2022-05-12T10:10:04.763000+00:00
Original source
With the blizzlike installer and patcher we can do incremental patching with only updating what's changed from a to b, and with static locations we'd eliminate duplicates entirely
1 Guest(s)
1 Guest(s)