- Joined
- Jan 1, 2014
- Messages
- 140
I have always been a java coder. Syntax is difficult to understand on deeper level. Once I undestrood similarities to WE i started to see bigger picture.
I feel bad for anybody who does not build everything at themself and use ai.
(merged)
Sorry for double post, but you get the idea that I wrote this comment after thinking hours after previous comment (and cant add this into previous post instantly by modifying)
So I thought today that it would be nice to 'transcode' wice engine from w3editor into java. And I made little bit designing already.
Because I think I can't never get any money from wice-engine I would like to share basic concept of this program that I made many years ago for wc3. (I did not receive enought enthusiasm for co-operate and develope wice-engine more with warcraft)
Basic idea:
-One trigger is a kind of loop (inside one), it's the mechanical part of the engine that does a lot of running. Loop ofcouse stacks but idea is mainly that one row of doodad writing is one loop.
-Other trigger is target trigger of the loop that activates when the loop reads from library that it is now turn to write
-And then there are libraries that describe when there should be doodad to be written..
The concept ofcourse expands greatly, and I also made implementation for third dimension instead it just being 2d.
I feel bad for anybody who does not build everything at themself and use ai.
(merged)
Sorry for double post, but you get the idea that I wrote this comment after thinking hours after previous comment (and cant add this into previous post instantly by modifying)
So I thought today that it would be nice to 'transcode' wice engine from w3editor into java. And I made little bit designing already.
Because I think I can't never get any money from wice-engine I would like to share basic concept of this program that I made many years ago for wc3. (I did not receive enought enthusiasm for co-operate and develope wice-engine more with warcraft)
Basic idea:
-One trigger is a kind of loop (inside one), it's the mechanical part of the engine that does a lot of running. Loop ofcouse stacks but idea is mainly that one row of doodad writing is one loop.
-Other trigger is target trigger of the loop that activates when the loop reads from library that it is now turn to write
-And then there are libraries that describe when there should be doodad to be written..
The concept ofcourse expands greatly, and I also made implementation for third dimension instead it just being 2d.
Last edited:






