This bug needs fixing: https://us.battle.net/forums/en/starcraft/topic/20753936973#post-1.

Also I dare there been a crash with Terran Ghost's die animations at some angle. Can please anybody who play snipers maps alot confirm? I'm not sure now if it does or does not depend on a vision with yourself. But there also been unrelated crashes when you turn off vision for yourself and go in and out of fog.

EDIT:
More info about Terran Ghost crashes. There is a map that was popular back in days: Hide n Snipe. If you have some fun playing it with friends you will encounter the crash on your ghost's death sooner or later. This map contains some sprites that were intended to crash the game when you see them for antihack reasons and it is protected, but I believe those sprites aren't crashing SC anymore and protection isn't very smart. I believe what indeed causes the crash I am talking about are either vision issues or ghost death animation or both interleaved.

Post has been edited 3 time(s), last time on Apr 11 2017, 7:41 pm by Wormer.

I skimmed over this document, I think it is a very well written and inclusive document. Thanks for the great effort in putting that together!

I think a lot of requests are unreasonable and really drowning out the simple asks. For example they would just enable a flag in the project that adds mp3 support (takes like 15 minutes tops), meanwhile additional terrain heights could take weeks of changing a ton of game logic and need heavy debugging/testing.

Then there are the billion ridiculous trigger requests (which also contain general engine requests), including changing the way the engine works. Most of them can be combined into one bullet point. "set any unit property to any value (i.e. current HP, max shields, weapon, collision boundary, velocity, etc)" would suffice for like 15 different bullet points.

I mean you can do whatever you want but the more you add, the more you drown out the simple things and overwhelm the recipient with your requests. I recommend combining many of the bullet points, leaving out controversial engine changes (only keep additions or changes that don't modify the 1.16 engine behaviour), and leaving out editor-only suggestions that community-based editors already support (or can support).

Yip.

These two posts are a far better starting point:
http://www.staredit.net/topic/17207/2/#57
http://www.staredit.net/topic/17207/3/#61

Honestly I just want what we have been able to do be properly added to the game. If it was possible with extremely simple memory overflow stuff, then it should be more than possible to add into the base game no?

Fair point. It is a good idea to trim some of it down. Certain things that we think would be very easy to do, but be highly beneficial to future UMS maps. Still, Zoan basically put together all our posts together, and have managed to organize them in some sense. We can edit that document and start prioritizing things we want to send. Btw, who is sending this document, and who is communicating with Blizzard anyway? Is this more of a vaporware wishlist or a wishlist that will actually be seen by decision-makers?

I'll be sending the list to BW:R DevTeam, I have the contacts from SC2, this is why I started compiling the data on the first place.

Here's the original listing: https://docs.google.com/document/d/1KRxV3nq3BQivvy_WVkUrhlIpZ1VFF9CVzvelaFQ5zSg/edit#heading=h.ufa6se2mjkr

I fully agree with you Heinermann, but I don't want to sound too brash, as my background of UMS BW mapping is basically null, and I don't want to get too much of my inputs on this list, I want it to be from you guys, but please focus on bug reports.

/version with comments allowed

https://docs.google.com/document/d/19f-HD_UbSC1O5XNDdTOCdICmIMps8FNc_1HyWS9cztA/edit?usp=sharing

Post has been edited 1 time(s), last time on Apr 12 2017, 6:22 pm by Kantu.

When I develop apps I prefer comprehension over priority in feedback. Priorities can be left to me, based on feasibility.

If there was consensus about what people wanted, sure ask for fewer things. But there is not, and while some items can be presumed to require engine overhaul, many cannot without access to the source code. Blizzard is best suited to decide what can and cannot be done.

I would also advise those commenting on the list, this is more about the backend than the editor UI. SI is the man to see about editor frontend changes.

In terms of presuming what can and cannot be done easily, the engine has been completely dismantled over the lifetime of 1.16.1 (See http://www.openbw.com/ ). Some of us have enough context to estimate the work required. It's not as good as having access to the source code, but it's fairly close.

After rereading your post I agree with your points. The list could be more concise and better prioritized if someone with context of the engine is willing to review it.

Saw a game of Temple Siege being hosted and my heart swelled. Joined, and they remembered me! Asking for a new version to be made and what not.

5 minutes in, after having died once in a nice little fight:
"Fucking feeding noob. Fucking sick your mom's dick" *leaves game*
I'M SO SILLY! Totally forgot how toxic ts players were!

Starcraft is coming back boys

So patch 1.18 has come out of PTR and gone live. The game is now free to play.

Anyone satisfied on what they've done with 1.18? Should we expect more patches to the non-remastered version of the game in the future, or is this it?

Thankfully they've fixed the leaderboard issue, and removed the text boxes, which were my main gripes. It's a damn shame the negative unit HP wireframes changed colours though.

Brood War is still awesome and having a community that wants to play older maps is amazing. It's the critical mass the game needed to spark attention again as SC2's popularity is dwindling.

What they've done with the UI is very buggy and most of the exciting features won't be here until Remastered actually launches (matchmaking, BNet 2.0 integration, widescreen, etc.) So hopefully that happens sooner rather than later, before people start to leave en masse again.

Personally I'm really excited.

I'll be 100% fine if the modding tools get updated and other than the core changes they've made the game behaves identically to 1.16.1. I doubt that will be the case, but one can hope. In the meantime, most of my works will remain compatible solely with 1.16.1.

So are we moving off ICCUP back to US EAST now or do we wait until remaster?

Definitely move back to US East. There's no reason whatsoever to use ICCUP anymore.

Okay well I'm having connection issues but hopefully will be back on there soon. All SENNERS follow me!!!

Also a new link has dropped showcasing the remastered artwork guys:
https://starcraft.com/en-us/articles/20695698

1.18 is an unfinished mess, and anyone could've seen this coming from miles away if they paid any attention to the ptr. Buggy as hell and missing tons of features, including hotkeys. I'm going to hold off until 1.19. I guess Live is the new PTR and PTR is the new internal test build.

They changed their mind about hotkeys and aren't going to allow them to be customized anymore.