Inspected the site.
No obvious signs of a currently active malware infestation.
However, the recently observed downtime is in all likelyhood related to one (coin miner, if I were to wager a guess), and thus everything of that domain will remain flagged for awhile.
Their very own fucking damn fault for lacking the acumen to discern that this venture's doomed from the get-go.
If you sign up for a cruise on a ship that's fucking leaking everywhere, don't complain about the inevitable, ensuing shipwreck.
As long as we live, so shall 1.21/1.26-1.28.
Of that, you need not to worry. However, unless we attempt to unite what is left of legacy war3 it shall forever linger in twilight, myriadly sharded.
I do believe that now is probably the best time to attempt this as the odds of succeeding has never...
My point is that instead of wasting yours all breath on pointless duplicate efforts (like setting up yet another pvpgn server) it would be smarter to instead do something more worthwhile - uniting the legacy war3 community (improve on hostbots, setup hostbots, talk to/negotiate with pvpgn...
You're just parroting what I said, basically.
My point is, that unless we have a strong (read: sizeable) community in place, it will slowly wither in both the sense that it will bleed more players than it'll attract, and that short of the most popular games other public ones will die.
My point is that whether theres 1, 5 or 200 pvpgn servers out there is quite irrelevant - what matters, is uniting them (have hostbot chains that connects to all of them, amongst others). The War3 community's already fairly sharded - we don't need to shard it any further.
The thing is...
You don't get me.
What I am saying is that, right fucking now you're fucking wasting your time, as this is a wasted duplicate effort.
Setting up yet another pvpgn server is useless - you could've just used one of the existing ones.
Setting up hostbots and convincing people to play...
Yet another pvpgn server isn't what we need - there's already numerous of them out there.
What we do need however, is a coordinated effort to unite those communities including but not limited to,
- setting up hostbot (chains)
- setting up a service à la makemehost
- kludging a ghost that ensures...
They've been on the payroll for many a year already, yet all they managed to deliver is pure, distilled shit in the meanwhile. Do you honestly believe keeping them on the payroll for another half a decade will change anything about it?
(a) the worse blizztards fucks it up, the more likely a concentrated push for pvpgn will be
(b) it's either that or surrendering, in all likeliness.
I wouldn't expect greedy, retarded executives to see reason even if we were to bludgeon them to the death with it, so there's...
And just like that they're dropping 1.30.2 on us. (Yes, I'm a few days late because of reasons.)
At this time I'm honestly just about done attempting anything when Blizz is just super tryhard about killing off whats left of BNet.
Yes, with 1.30.1 confirmed being stable (enough), we'll be back in a jiffy; however coinciding with the 1.30 instability was me having a life (I'm still kinda busy); I'll see when I can set a night again, but should be soon! (likely 1st Sat of October)
yes of course
mind you, i'm not suggesting you to get rid of the preset game mode, merely to expand upon it (host choice) because this clearly looks like the best implementation of a pictionary/drawgame in war3 yet; and imo one of the most fun parts of it is the drawer selecting their own...
from what i can see the critical crashes for custom games still haven't been addressed yet, and i'd rather do clean skips than staggering the schedule
however, i will try a weekday night whenever we're back again, and see how it goes
may i inquire for your preference for that, if...
Next Game Night (Aug 11th) has been cancelled due to expected extreme 1.30 instability. Likely not worth our time to play 5x maps for 5mins a pop b4 crash.
We shall wait for 1.30.1 or 1.30.2 to address most of the most pressing issues instead.
As I may not be around for the 25th (bc of reasons)...
which potentially creates fifteen million security issues right there
also, its not the servers bandwidth that we're worried about but the users', and it doesnt matter whence your users have to fetch those files from
i use wget on my server to grab the maps, and whenever i dl from hive it names them download?token=somethingwhateverasdfcode34t3gwedfablah and i just rename it to whatever from there, thats why i'd suggest you to put it up on something like EpicWar because there i get the actual filename along...
Let me reiterate:
I understand that falling back to the default set of CASC tools is probably easier for Blizzard to deploy patches with, however reverting to the MPQ build isn't half as bad as you may make it out to be.
There's stuff like winmerge you can use to easily see which files...
the thing is they can't even delete mpq code from war3 or it'd delete all the old maps, they're actually bloating the client with (redundant) CASC code that exists in addition to the mpq one
so all it does is enabling blizz to use their CASC packing tools for war3, but then again you can just...
war3xlocal-enUS.mpq, war3xlocal-deDE.mpq, war3xlocal-enGB.mpq, should probably not be too hard to have the client only load the selected locale mpq
are you suggesting war3 to drop mpq0 support
(hint that will end in fire because it'll delete 16 years of maps)
because it'll delete 16 years of tools (gradually, unless you manually repack your post 1.30 client), and is generally a big fuck you to the entire modding community
oh, now doesnt it
if you properly pack your localised stuff into war3xlocal.mpq you'd be able to do that anyways (you change the...
if you write a correct tool that builds mpq archives from a working directory it shouldn't take more than a few clicks and a minute of computing (hell, mpqedit could do that ..)
as for proper localisation support, idt mpqs would stop you from that? the problem isnt with the mpqs itself (there's...
i however still fail to see how such a system would benefit war3 in any (realistic) way tho, you'd likely need a full rewrite of the code for it to be able to make use of the streaming feature (start playing with incomplete client), and even then, it'd be reasonably pointless because the...
The most Steam can do (for the vast majority of archive types anyways) is to verify their integrity through checksums
The very same would be sufficient for war3 (because lets face it no1 will rewrite it for more than the most basic of integrations), and im pretty sure you wouldnt have to be...
bnet app doesnt have to be able to read mpqs to do an integration like that tho, its like saying if you wanna post your game on steam the steam client must be able to make sense of all your games archives
you're still missing the point, there is literally no gain from integrating war3 into the app like that, it doesnt use bnet2.0, nor will it (closed ecosystem will kill game just like sc2, besides the fact that it'd require an extensive rewrite of the engine), and it's not like war3's got a 30...