BNETDocs
StarCraft: Brood War Remaster Rumors Recap
Starcraft

In early August, iNews24, citing an inside source, reported a StarCraft: Brood War remaster in the works that would include high resolution graphics and an improved user interface, and would be initially announced in September with another announcement coming in during this year's BlizzCon, which occurred from November 4 – November 5.

This rumor didn't come as a surprise to some people, job positions listed under Classic Games began appearing as early as October 31, 2015, as shown by the Wayback Machine. The job positions were interpreted by some as evidence of a remaster in progress due to its wording, namely, "We’re restoring them to glory" and "Create conditions for experiences that look as good as they play", and therefore supported the rumor by iNews24.

Various debates quickly arose following the rumor, most of which focused on what Blizzard should or should not change. The validity of the rumor was less discussed as many fans hoped that the evidence presented was just good enough. September rolled by and no announcement from Blizzard, though that did not discourage fans from believing an announcement would be made at BlizzCon instead. BlizzCon slid right by with no announcement as well, though Diablo 1 fans will be able to get a taste of the original Diablo remake inside of Diablo 3 if they have a copy of Diablo 3: Reaper of Souls.

Despite no announcement of a StarCraft: Brood War remaster, it's important to note that the possibility is not completely off the table (to the public's knowledge), unlike WarCraft and WarCraft 2 which Jack Pearce, Blizzard's co-founder, and Mike Morhaime, Blizzard's president, explained that they are choosing to not remaster the two WarCraft games and will instead focus on other efforts.

With the passing of BlizzCon, it seems as though we're back at square one again. Not quite however, the existence of the, albeit unpublished, 1.17.0 patch could provide us with some insight. There are two routes that Blizzard must choose between should they decide to remaster the game: 1) make a backwards compatible client so that those playing on the remastered version could play with those on the traditional version, and 2) make a non-backwards compatible client that will not be able to play with those on the traditional version.

The latter case would cause a significant split in the Brood War community regardless of the changes that will be made, unless this remastered client will be offered for free, which doesn't sound very likely for a remaster. Also, depending on the changes that could be made as well as its pricing, the Brood War community would most likely stick with the traditional client. Assuming, increased game resolution will be provided, the former would cause backlash from the Brood War community due to concerns about fairness of gameplay. In both cases, Blizzard would have to maintain both games as it appears that a remaster will not supersede the traditional client, due to the fact that a new patch for the traditional client exists. This does not seem like a good idea for Blizzard's Classic Games Team because having to maintain an additional game would consequently strain their resources more.

What are your thoughts on the possibility of a StarCraft: Brood War remaster?

Simplicity 1.0
Battle.net

It has been almost 4 years since the last update, but I am pleased to once again provide an update to this program. There are a lot of minor details with this update, but the biggest change is using custom named initiates in a newly created clan instead of just using the generated initiate names. The biggest issue that was addressed was the creation of clans in general. The last public version (version 0.72) did not handle clan creation very well.

If you're new to Simplicity, it is a clan creator that requires minimal configuration to use, relies on SOCKS4 and HTTP proxies, checks for clanned keys when creating a clan, and more.

You may download Simplicity here: http://www.codespeak.org/Simplicity/Simplicity.zip

BNETDocs General Status Update for August
BNETDocs

BNETDocs has been going through quite a few changes lately. I figured it was time for another status update. This is a follow-up news post to the previous status update.

A quick summary is the plot is thickening around Blizzard development and a few big milestones are soon to come for both BNETDocs and Blizzard.

General Notes

Blizzard visits

As some may know, Blizzard has been visiting pretty heavily recently. After the publishing of Brood War 1.17.0 Pre-release, the post was also shared on sites like Reddit, Facebook, and Twitter, and racked up around 17.5k hits and still climbing.

This of course spiked an interest from the folks who browse Reddit at Blizzard. I have strong evidence that they've been observing our documentation around game matchmaking and friends on Battle.net, even visiting BNETDocs in their browser without a referring website, multiple times per week.

Worth sharing is this YouTube video from Robert Bridenbecker on WC3 patch 1.27, where he makes note of how his new Classic Games team is working on improving matchmaking and friend integration.

Traffic volume

Here's the volume of traffic that hit BNETDocs following the Brood War 1.17.0 Pre-release announcement:

Most of the cached traffic is for assets like images, javascript, and css. The uncached traffic is mostly raw traffic to actual pages on BNETDocs.

Development environment

I've separated BNETDocs Phoenix into two environments: production and dev.

I hope you find that the BNETDocs production environment will become a lot more stable as of today. Before, all development to the site was implemented and tested in production. Now, all development will happen in the dev environment and get tested there before being promoted to production.

Both environments sport CloudFlare DNS & CDN and are using the same data sources with one exception: Memcache. So there should almost always be a one-to-one clone or feel to both of them, however differing Memcache key stores means that Anti-CSRF tokens and user sessions/logins are stored independently. This means that when you login to production, you will not be logged in on dev, or vice versa, and submitting a form from one environment to the other is also prevented due to the differing Anti-CSRF tokens.

Mobile site and Markdown enhancements

At the request of a few individuals of the BNETDocs community, I have spent time polishing the mobile site for BNETDocs and the Markdown CSS code. The result is now the entire site can benefit from better Markdown, like this news post, and users on mobile will have a much cleaner experience–including a navigation menu, which was previously missing!

Speed of development

This is just a general reminder that the speed of BNETDocs development is at the pace of myself. There are some individuals watching the development of this site, but aren't actively contributing. Unfortunately, while I do love to contribute to BNETDocs, I cannot spend 100% of my time on it, since I do have a full-time job and life is going on around me. That said, I do wish to hopefully be ahead of the game before the rumored StarCraft HD update in September.

Features

Since the last status update, the following features have been completed or partially completed:

  • Comment creation and deletion for news posts
  • Mobile site
  • Document creating, editing, and deleting
  • News post creating, editing, and deleting
  • Packet searching

The following features still need to be implemented:

  • Comment editing for news posts
  • Comment creating, editing, and deleting for documents, packets, servers, and user profiles
  • Document and packet relationships or otherwise content linking
  • Document searching and popularity ranking
  • Emails
  • Event log viewing
  • Packet creating, editing, and deleting
  • Packet popularity ranking
  • Server creating, editing, deleting
  • Server pages for each server, complete with history of uptime or other status changes
  • Password recovery
  • User index / list of registered users
  • User profile editing

Most of the enhancements above and more are currently being tracked on GitHub.

Carl Bennett Saturday, August 6, 2016 | Edited: Friday, August 12, 2016
Maelstrom CD-Key Tester 4.0
Battle.net

After last being updated November 1, 2012, I have finally released another update for Maelstrom CD-Key Tester on August 2, 2016. After being in development for roughly the last 2 months it has been improved in a number of ways. From a few new major additions to improvements in speed and performance.

Some of the major changes introduced in version 4.0 are:

  • Added a config GUI, removing the need for several different input boxes, having a better way of editing the config and a better solution to checking for errors
  • Added CD-Key Profiles as an option
    • Saves keys tested under \CD-Key Profiles\<profile name>\
    • Option to add the current realm to the profile (<profile name> @ USWest for example)
  • CD-Key loading changes
    • Maelstrom can now load CD-Keys from any file
    • Place the files in the \CD-Keys\ folder (they can be inside folders as well)
    • The folders/files in this folder will be wiped after the keys are loaded except the standard key files (STAR.txt, W2BN.txt, D2DV.txt, D2XP.txt, WAR3.txt, W3XP.txt)

Maelstrom started in August 2010 at the request of a few of my friends who wanted a better key tester than what was currently available. From there it became a popular tool of choice over the years. One such useful feature that people really like is its ability to test expansion keys.

It can be downloaded here: http://codespeak.org/Maelstrom/Maelstrom.zip

Vector Tuesday, August 2, 2016 | Edited: Wednesday, August 3, 2016
StarCraft Patch 1.17.0 Pre-Release
Starcraft

Blizzard has uploaded a copy of their new patch for StarCraft and StarCraft: Brood War version 1.17.0. It is currently not active on Battle.net servers (connecting using 1.17.0 displays an unsupported version error message), however it can be downloaded from their FTP site. It contains the new version byte 0xD5, a bump from 0xD3 as seen on 1.16.1. The patch was first reported at tieba.baidu.com on July 22 and at teamliquid.net on July 25.

Game Official Mirror
Brood War BW-1170.exe BW-1170.exe (Checksums)
StarCraft SC-1170.exe SC-1170.exe (Checksums)
Starcraft and Brood War Patch Information

--------------------------------------------------------------------------------
- patch 1.17.0
--------------------------------------------------------------------------------

Specific Changes & Improvements

- Increased turn rate to lower unit response times over Battle.net gameplay
- Fixed palette issues to correct "rainbow water" and other graphic artifacts
- Fixed text artifacting in the Battle.net menus
- First client run will migrate saves to avoid issues from Windows system admin changes

Known Issues

- Mac is not supported this patch, but is in progress

Some notes:

  • The patch introduces BlizzardError.exe and SystemSurvey.exe to StarCraft for the first time.
  • battle.snp, standard.snp, StarEdit.exe, and storm.dll are now digitally signed.
  • The latest digital signatures were signed on July 11.
  • W-Mode plugin is broken despite the author's claims that it works with any version of StarCraft.
  • Alt+tabbing out causes other windows to be resized to 640x480 resolution.
  • StarCraft's new base address is 0x01190000, old base address is base address is no longer fixed at 0x00040000.
  • Screenshotting in the Battle.net interface automatically saves to your clipboard instead of opening a dialog.
  • Screenshots are now saved in PNG format instead of PCX.
  • StarCraft now requires CheckRevision's .dll to be digitally signed.

Additional notes (2016-07-27):

  • Storm.dll's base address is no longer fixed at [TODO: FIND OLD BASE ADDRESS]
  • Storm.dll exports at least 2 additional functions: SErrSetBlizzardErrorFunction (ordinal 132) and SNetSetCodeSignVerifcationFunction (ordinal 148). These functions are now documented at Liquipedia.
  • StarCraft now extracts CheckRevision's DLL file to %AppData%/Local/Temp/
  • StarCraft creates files called Crash.txt and Minidump.dmp in %AppData%/Local/Temp/BlizzardError/year-month-day hour.minute.second/ when it crashes, instead of in StarCraft/Errors/
  • Example Crash.txt file: https://gist.github.com/RElesgoe/a5d23dae4b5003c7db50589c06dce33f
  • StarCraft now logs the total and monthly amount of games played on each protocol. These logs are stored in %AppData%/Local/Blizzard Entertainment/System Survey/ProductData/SEXP/ and %AppData%/Local/Blizzard Entertainment/System Survey/ProductData/STAR/
  • Example logs: https://gist.github.com/RElesgoe/fc9a9fda51d6e1b5f2f661fc621f6783
  • StarCraft no longer crashes when attempting to watch a replay in which a player has chat too much while the game was paused. Replay Fix is no longer necessary.
  • Blizzard seems to have modified an outdated version of StarEdit. The new StarEdit.exe binary displays 1.0.0.1 as its File Version and Version 1.00 as its Product Version whereas the StarEdit.exe that's installed with 1.16.1 displays 1.0.0.2 and Version 1.02 respectively.
  • Increased turn rate to lower unit response times over Battle.net gameplay means that the NetworkModeDelay while playing on a server is now the same value as playing on LAN, which is 2. See LatencyChanger

Dumps of the game version handshake can be found on PvPGN's GitHub.

xboi209 Tuesday, July 26, 2016 | Edited: Friday, August 19, 2016

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 >