Romek
Super Moderator
- Reaction score
- 963
If the coding can be improved without any downsides, you're expected to improve it.
If the coding can be improved without any downsides, you're expected to improve it.
In all honesty, who cares about speed in save and load systems.
By the way that reminds me, I plan on releasing a vJASS version.
So I'd rather not have any code comments, and have system comments instead. As long as the code doesn't leak.
As for compression, I think my code size is pretty small and my compression method is fine.
Dynamic coloring seems completely useless, the point of coloring is to better identify the characters case.
I can make the spacing symbol configurable but your spacing idea is also just completely useless, at least in my opinion.
So you are saying you don't want to make it easy for people to configure the coloring of characters for their own use: Use your colors or gtfo?
options for color coding of letters, like "aA", red (would make a and A characters red)
So you are telling me that You don't want to let people who use your system do whatever spacing they want: Use only one spacing symbol my way or gtfo?
Is compressed as much as it can be: I don't like big codes
Lets people change the colors of characters easily: I like to configure stuff without going thru the code
Lets people do whatever kind of spacing they want: I like to easily change the spacing.
Does have random encryption as it'd only be 1 extra character and it would make players who didn't know how to open an optimized protected map unable to crack the code.
That to me sounds wrong in so many ways and I can tell you that I'll never use your system. I'll just make my own that-
While the codes may be small, if they can be smaller then the system can be improved ; ).
Set Hero = (Your first unit)
Custom script: set udg_Save[udg_SaveCount] = CG_SaveHero(udg_Hero)
Set Hero = (Your second unit)
Custom script: set udg_Save[udg_SaveCount] = CG_SaveHero(udg_Hero)