Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
Hello people! My name is DarkDez17 and I'm uploading this Alpha version of my map.
About gameplay: You choose your Hero, your allies choose their Heroes, everyone buys items and potions, the coolest person activates waves and you have to protect against 10 waves of enemies with a Boss in the end. After 10 waves you are able to do some stuff freely and start whenever you're ready. Yeah, well, and so on. Right now there're only 25 waves, but I intend to do much more.
Well, so, I really want to know your opinion if it's even playable atm. Please, check the map (It's in attached files) and tell me what do you think.
I don't usually review maps but hey, I'll give this a go.
Obviously it's early days so I can't give a solid answer as to whether it's good or bad, only time will tell. It reminds me of Legion TD with the bosses every 10th wave but clearly using heroes rather than towers to defeat the creeps. It's definitely not the worst I've ever played and it has potential, but again, it's too early to judge.
As for the gameplay, I didn't get very far; I died at the second wave twice in a row. I assume this is because you're aiming for a multiplayer game rather than going solo against swarms of creeps, so you'd have teammates to help you out. Maybe in the future, it would be nice to add some sort of scaling on the creep waves based on the number of players in the game (Eg: number of creeps per wave = 10 + number of players x 2). Additionally, you might want to add some warnings about important moments such as when the next wave will start, when it's finished, etc. Just throwing some ideas around. Personally I like these types of maps (TD/wave clearing) but I guess the issue nowadays in map-making is, "What sets your map apart from the rest?"
You also might want to have a look at the threads below about leaks. Triggers in general are what I'm about (or should that be was?) and so I had a glance at a few of your spell triggers and noticed a lot of leaks, which will eventually slow down the map as the game goes on. It would be best to learn about preventing leaks to avoid having to go back afterwards and try to sort them out when there are too many triggers to go through. Trust me... been there, done that. I've also added an example of how to fix the leaks in one of your triggers; I'll leave the rest for you to learn from.
Moved the trigger conditions from an 'And' to a 'multiple And' condition; it's the same thing but easier to edit if you need to.
Switched all references to Casting Unit to Triggering Unit (it's faster and apparently safer to use in most cases).
Created a location variable at the position of the Druid to use in the unit group action and to help remove the leak later on.
Used custom script (set bj_wantDestroyGroup = true) to remove the unit group leak.
Changed the unit group to only pick units within 750 range (slightly more than the aura AoE) to avoid filtering through all units on the map and improve performance. Also moved the condition into the If-Then-Else statement within the loop actions for some more performance improvements (and inherent leak IIRC; nothing major though).
Created another location variable for the leak in the special effect on the picked unit.
Destroyed the effect to remove the leak. Don't worry, most effects will still play even when immediately destroyed.
Used custom script (call RemoveLocation( udg_TempLocationX )) to remove both location leaks.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
