devtrackers.gg
Oh boy, first teaser. Here we go!
Oh boy, first teaser. Here we go!
Read more/u/RhysGGG, can you clarify this? And /u/_xhul_, FYI:
https://cdn.discordapp.com/attachments/175290321695932416/678285728093831177/unknown.png
I got the post on
==vs=but:I'm unsure whether the syntax is
SocketGroup "GGG"orSocketGroup GGG. There are 2 conflicting examples (in red).I'm also unsure how both Sockets and SocketGroup will behave when there are multiple color groups (with = and == we have 4 different cases)
It's also not specified whether the order of letters matters - you never published any EBNF spec or anything similar and the parser container multiple unintuitive/bugged assumptions previously so I'm asking if there is anything regarding syntax that is worth to know
It's unc...
The syntax for SocketGroup should be unchanged: SocketGroup GGG
Ordering of letters doesn't matter.
As with all rules, if you specify multiple matches if match against any (rather than all). So you could use SocketGroup == RRR GGG BBB to match items with exactly 3 sockets all the same colour. If you didn't use the == operator, it would also match items with extra sockets.
CorruptedMods actually takes any number, but currently nothing in the game drops with more than two corrupted mods. Not even Hands of the High Templar.
I've updated the post to be more accurate, thanks.
Its absence is accidental. I'm arranging for it to go on sale shortly. That means it's a short sale day for it but it should be included in the celestial sales in future.
Why you deliver full ggpk with steam? Some other MMOs deliver only launcher, which then download and update content files. This way you can fix such problem as long patching when small patches comes out and use one ggpk in steam and standalone client.
I don't really like that approach because most people just have steam running in the background and auto patching all the time, and if you don't use steam's patching then you don't get that. The game wouldn't patch until you run it.
The new way will be both friendly for steam, and have higher performance anyway.
but it will also come with a pretty significant improvement to loading speed of non-SSD drives
If it offers a big improvement to performance of some users and no hit for others why is this not going to just be the default for all users whether steam or standalone? Shouldn't standalone users also get the better performance that this gives on an HDD?
It will be for all users.
We need to get the existing non-steam patching system to be able to patch content for the new system first though.
If you don't mind my asking, why the single big file in the first place? I read somewhere that it streamlines the loading process, but it sounds like the console version's method doesn't do that and is faster.
Unpacked, Path of Exile is hundreds of thousands of tiny files. Many of them are tiny hand edited or tool generated text files that might just be 1KB or so. Packing them together is important for performance so you don't have to do so many disk seeks while loading files.
But so long as your files are still fairly large (32 MB or so per file for example) then the performance of seperate files is totally fine.
For conveniance of the original patcher, it was simple to have one big file. And it was a fairly common thing to do at the time ~13 years ago. Our patcher was modeled on the Guild Wars 1 patcher, and it's quite similar, but blizzard had it's MPQ files and so on. The big single file is structured such that it's very easy for us to work out the minimum set of files that need to be patched. We just check a single hash if nothing has changed, and only explore the file tree to the parts that have changed if not.
We didn't add steam support until the game was ...
Read moreSooo, in PoE2 or hopefully before?
It will be before PoE2.
The reason we don't do that is that it would mean redownloading almost the entire game again every patch.
The steam patcher breaks down big files into blocks and then only gives you the blocks that change. If you try rearrnaging the internals of a single file then basically every block of the file will be changed.
All of the "garbage" in the file is old file versions. By not removing them it makes the patch sizes smaller for existing users at the expense of making new full downloads by new users larger.
Of course, the big single file approach isn't good for steams patcher generally. The main reason is because steam makes a full copy of the entire file when it patches it, patches the copy, then moves it back over the original again. This is to prevent corruption in the case where, for example, you lost power while steam was in the middle of patching a game. This means that patching a 1KB file makes you computer rewrite the entire many-gigabyte file which is w...
Read more
