By providing general purpose functions/actions/conditions/events with proper documentation and utilization of them in a single package. It was cool when UMSWE back in WC3 added useful actions in the Trigger editor. It is 100x easier to contribute something like that now.
Sooo... a library packed with general purpose triggers from the community?
Rollback Post to RevisionRollBack
Member since 2010. Made the -The Thing- [Revival] game. Nostalgic of the WC3 days.
The main problem with "improving the editor" is that everyone has a different understanding of what would be useful and what wouldnt.
Why import a gigantic library if you just use 5% of its functionality? Its better to have several smaller libs with a clearly defined role than creating one big "all in one" library for everyone.
On another note, of course its also a lot of work to create a well coded library, which is tested for bugs, optimized for performance and well documentated. There really isnt much reason to do so currently, since the only thing you will probably get in response is annoying questions via PM.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumBy providing general purpose functions/actions/conditions/events with proper documentation and utilization of them in a single package. It was cool when UMSWE back in WC3 added useful actions in the Trigger editor. It is 100x easier to contribute something like that now.
Sooo... a library packed with general purpose triggers from the community?
Member since 2010. Made the -The Thing- [Revival] game. Nostalgic of the WC3 days.
@Vicboy: Go
I agree with you
What exactly would be included?
I agree this would be cool but there would need to be some list of needed functions
This is a similar idea right?
http://www.sc2mapster.com/forums/resources/project-workplace/27296-gax3-star-craft-ii-editor-enchant-mod-mod-download/
There are a lot of custom things so you might want to start their?
The main problem with "improving the editor" is that everyone has a different understanding of what would be useful and what wouldnt.
Why import a gigantic library if you just use 5% of its functionality? Its better to have several smaller libs with a clearly defined role than creating one big "all in one" library for everyone.
On another note, of course its also a lot of work to create a well coded library, which is tested for bugs, optimized for performance and well documentated. There really isnt much reason to do so currently, since the only thing you will probably get in response is annoying questions via PM.
@Vicboy: Go
There's already a few projects like that. Although manned by single entities rather than a community. For example, the GAx3.