i would suggest that we collect bugs, suggestions and glitches about the beta editor for a huge single post on blizzards beta editor forum.
perhaps blizzard will look it up and fix those things with the next patches - we can just hope.^^
here is already my small list:
Missing Functions:
A function to ...
- add an ability to a unit
- add an ability to an item
- add an event to a trigger
- change level or exp of a unit
- get level or exp of a unit
- change the name of a unit
- get the name of a unit
- change the name of an item
- get the name of an item
- change the item slots of an item container
- get the item slots of an item container
- get the current level of a unit's ability
- revive a unit
There should be support to display up to 5 attributes for a hero.
4 is too less and 5 would be a great number for many mappers.
Bugs/Glitches:
-Terrain foliage does not display in editor, but only ingame since 2nd editor start.
-It is very difficult to deselect triggers etc. after you "select all".
-If you switch in data editor to another data, the old one is still displayed until you selected a new one.
The problem appears if you just got one data object in an editor - for example if you just let your own
creations show up.
-There is just a "NoFlyZone" (doodad) in the pathing editor, but not a "NoFlyTexture".
It is not good that a full Galaxy script is disabled.
Many mappers just don't want to script in GUI because Galaxy would be more organized for them.
-> That is also my opinion.
The new GUI is really powerful - but i really would love to script in Galaxy and not with a GUI-Galaxy mix
with custom scripts. T.t
The non-english editor (german) got problems with interfaces.
Some option text's do not show up - but have functionality!
The ability to edit requirements would greatly help, currently the selection is to limited and not something I'd use as a map maker.
Also allowing an actor to be used for multiple units would be nice, seeing as how I have 3 copies of the same actor because I have 3 units using the same model set (this amount will grow).
Changing game error text would be great. Since currently when a player tries to use a resource it returns the game's error text which might not make sense in a game.
Essentially, if you make an all "void space" map (use the cliff down tool on the entire map so there is no land left) your camera will glitch out and testing the map itself will glitch out, giving your camera an incorrect location and making unit movement impossible to understand. So, you know, beware making maps without any land at all.
Changing game error text would be great. Since currently when a player tries to use a resource it returns the game's error text which might not make sense in a game.
I think there is an option to edit ingame text, but beware the current localisation issues.
......
- Apply force does not seem to work if the unit cannot move, even if it is a valid target for the force effect.
- There is no trigger that activates mouse look and makes the camera move to follow a unit. Moreover, you cannot combine the camera pan trigger with mouse look. This makes mouse look completely useless.
- When saving maps, the editor occasionally and randomly throws an error saying it cannot delete a temporary file. My SC2 is installed in a directory in the C:\ root so it is not a permissions error.
- The following does not seem possible: an ability casts a set on the target, which has a damage effect and a searcher. The searcher picks a nearby target and applies a similar set to it, doing damage and looking for a new target. Now you want a beam between both units (so basically chain lightning). The beam always originates from the caster and nothing you do seems to affect it.
- I have a set that spawns three searchers, which apply behaviours to every target in range (one for enemies, two for allies). When a unit gets in range, there is a noticable 0.5 second pause.
- Editing triggers gets incredibly slow when you have a long trigger. I have a trigger with 16 switch cases that each do a unit move and set an animation. It takes 5 seconds to process any edit whatsoever. The annoying part is that when you want to edit a line and you move the mouse too quickly, it drags it instead.
- You can't initially set a camera using triggers. You have to place it on the map and then move it.
If Blizzard is reading this, hear my plea: don't break compatibility with existing maps when you patch the editor. Come release, people may have invested months into their map already and you did tell map editors to get started. :)
hiho,
i would suggest that we collect bugs, suggestions and glitches about the beta editor for a huge single post on blizzards beta editor forum. perhaps blizzard will look it up and fix those things with the next patches - we can just hope.^^
here is already my small list:
Missing Functions: A function to ... - add an ability to a unit - add an ability to an item - add an event to a trigger - change level or exp of a unit - get level or exp of a unit - change the name of a unit - get the name of a unit - change the name of an item - get the name of an item - change the item slots of an item container - get the item slots of an item container - get the current level of a unit's ability - revive a unit
There should be support to display up to 5 attributes for a hero. 4 is too less and 5 would be a great number for many mappers.
Bugs/Glitches: -Terrain foliage does not display in editor, but only ingame since 2nd editor start.
-It is very difficult to deselect triggers etc. after you "select all".
-If you switch in data editor to another data, the old one is still displayed until you selected a new one.
The problem appears if you just got one data object in an editor - for example if you just let your own creations show up.
-There is just a "NoFlyZone" (doodad) in the pathing editor, but not a "NoFlyTexture".
It is not good that a full Galaxy script is disabled.
Many mappers just don't want to script in GUI because Galaxy would be more organized for them.
-> That is also my opinion.
The new GUI is really powerful - but i really would love to script in Galaxy and not with a GUI-Galaxy mix with custom scripts. T.t
The non-english editor (german) got problems with interfaces.
Some option text's do not show up - but have functionality!
Robbepop
Good call :)
Blizzard developers are reading our forums, so be sure that what you are writing down in here gets directly to Blizzard :)
The ability to edit requirements would greatly help, currently the selection is to limited and not something I'd use as a map maker.
Also allowing an actor to be used for multiple units would be nice, seeing as how I have 3 copies of the same actor because I have 3 units using the same model set (this amount will grow).
Changing game error text would be great. Since currently when a player tries to use a resource it returns the game's error text which might not make sense in a game.
Suggestions:
Bugs:
Posted this bug on the official forums: http://forums.battle.net/thread.html?topicId=24401515950&postId=243993115717&sid=5000#0
Essentially, if you make an all "void space" map (use the cliff down tool on the entire map so there is no land left) your camera will glitch out and testing the map itself will glitch out, giving your camera an incorrect location and making unit movement impossible to understand. So, you know, beware making maps without any land at all.
I think there is an option to edit ingame text, but beware the current localisation issues.
......
- Apply force does not seem to work if the unit cannot move, even if it is a valid target for the force effect.
- There is no trigger that activates mouse look and makes the camera move to follow a unit. Moreover, you cannot combine the camera pan trigger with mouse look. This makes mouse look completely useless.
- When saving maps, the editor occasionally and randomly throws an error saying it cannot delete a temporary file. My SC2 is installed in a directory in the C:\ root so it is not a permissions error.
- The following does not seem possible: an ability casts a set on the target, which has a damage effect and a searcher. The searcher picks a nearby target and applies a similar set to it, doing damage and looking for a new target. Now you want a beam between both units (so basically chain lightning). The beam always originates from the caster and nothing you do seems to affect it.
- I have a set that spawns three searchers, which apply behaviours to every target in range (one for enemies, two for allies). When a unit gets in range, there is a noticable 0.5 second pause.
- Editing triggers gets incredibly slow when you have a long trigger. I have a trigger with 16 switch cases that each do a unit move and set an animation. It takes 5 seconds to process any edit whatsoever. The annoying part is that when you want to edit a line and you move the mouse too quickly, it drags it instead.
- You can't initially set a camera using triggers. You have to place it on the map and then move it.
If Blizzard is reading this, hear my plea: don't break compatibility with existing maps when you patch the editor. Come release, people may have invested months into their map already and you did tell map editors to get started. :)
Physics and a proper z axis where you can jump on and off of things.