Yes. What. You think the mouse in the Wc3 is so rare? ;D
Nah, it really isn't if you're familiar with JASS
BTW cool system, when I saw the picture for a second I thought that "II" means pause, I was like wut?
It's easy to do in GUI...
And yet impossible if you're planning on using trackables, which is actually a better solution considering it has on hover events. BTW the combination of units and trackables is godlike, because it gives you hover, left and right click events.
No, no I personally would have done it with arrow keys though, and a dummy unit for controls... But mouse works better I suppose, just harder to make.
And yet impossible if you're planning on using trackables, which is actually a better solution considering it has on hover events. BTW the combination of units and trackables is godlike, because it gives you hover, left and right click events.
140 MB, sounds like you'll have to boot the map and wait roughly 12 hours for the lobby to load, then another 8 for the game to start.
If your 12 hours = 3-4 seconds, and your another 8 hours on loading screen =
15-20 seconds... then yes, you're right. xF
But I remember from school, that seconds ≠ hours. xC
Edit:
As I said before: Only saving map in WE (No game) take about 1 minute.
No way it loads in 20 seconds, Curse of Time, (one of the crappiest maps ever) takes a minute to load... You must have a 4 ghz quad core lol.
No way it loads in 20 seconds, Curse of Time, (one of the crappiest maps ever) takes a minute to load... You must have a 4 ghz quad core lol.
Map size has nothing to do with map loading time; you'd know it yoruself if you knew a thing about WC3 triggers & object editor data.
Basically, the number of triggers in map is also slightly connected with loading time - not just the trigger size.
Map size has nothing to do with map loading time; you'd know it yoruself if you knew a thing about WC3 triggers & object editor data.
Do you have some sort of problem with me?
1. Triggers contribute to map size,
2. Object Editor entries contribute to map size,
3. Triggers that take longest to boot up (which are usually inits or run on 0.00), always slow load speed, whether it's inside the map, or on the loading screen.
? |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
? |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
? |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
? |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
? |
![]() |
![]() |
![]() |