[Library] STARCODE v1.2

[s3rius]

It's a function automatically created by the Editor when I integrated my script into a SC2Library.

[JademusSreg]

If it isn't necessary to the function of the library, it's a good idea to delete it.

For example:

//--------------------------------------------------------------------------------------------------
// Library Initialization
//--------------------------------------------------------------------------------------------------
bool lib1_InitLib_completed = false;

void lib1_InitLib () {
    if (lib1_InitLib_completed) {
        return;
    }

    lib1_InitCustomScript();

    lib1_InitLib_completed = true;
}

[s3rius]

This script part is automatically created.
Everytime you open a map containing this library, when these functions are not there, they will be recreated.

It's part of Blizzard's library handling and might even be of some use somewhen later (if I ever need to specify an initializer function).


PS: One thing I really would be interested in is to optimize the BigNum functions. I'm no mathematician, so I just searched for a way that would work. So if anybody got an idea..

[JademusSreg]

Right, those are artifacts. When copying the script into a map, rather than importing a library, those functions are unnecessary.

[s3rius]

Well, I put everything into a library to have a neat package with GUI support wrapped around my source. I'll have to accept these functions then.

A person who'll just include the source code itself to work with it should have enough knowledge to quickly get rid of it.

[Deaod]

Do those functions matter to anyone who doesnt have sufficient knowledge to remove those functions?
If not, then why are you keeping them? Its just bloat, and the majority of users wont give a shit about artifacts of the editor.

[s3rius]

As I said, the Galaxy Editor is automatically recreating them if they're amiss. I tried it. I do not keep them by choice.
These belong to the library and if I want to keep it as a library (which I do), then these functions have to stay.

I begin to think that the sc2c community doesn't actually have interest in my system, but instead only cares about trivialities and the format in which I post my stuff.
Please don't misunderstand - It's not that I can't stand critique, but I'd prefer something constructive.

[Ammorth]

Originally Posted by s3rius

I begin to think that the sc2c community doesn't actually have interest in my system, but instead only cares about trivialities and the format in which I post my stuff.
Please don't misunderstand - It's not that I can't stand critique, but I'd prefer something constructive.

I agree. This nit-picking about a single function is useless to the development of this resource. To keep the script in the realm of GUI within the editor, the function is included automatically by Blizzard. Case Closed.

Personally, until there is an all-encompassing mod for the editor that allows scripting directly in GALAXY (think Jass New Gen Pack), I would rather see code adopting GUI support.

[JademusSreg]

Speaking of scripting galaxy in the editor:
DerisiveDemonstration.jpg

Given the notorious 2MB limit on the galaxy VM, maintaining clean and efficient code is more important here than it ever was in WC3.

Since the script can be implemented independently of the GUI-library in a custom script within the map, the aforementioned functions can be safely removed from the script without any negative consequences. It's removal is a non-issue and the effort is trivial.

EDIT: Seems the IMG tag doesn't like me. Using ATTACH tag instead.

EDIT: Honestly, besides the artifacts, I don't see anything obviously wrong with the script. I look forward to testing it in game, when able.

[s3rius]

I have implemented the script in a seperate custom script section.
That is actually the reason of one of these two functions, as it serves as an initializer to the custom script.

I can only remove it completely by not using a library. And I think the bonus of having the complete library stuffed together and neatly packed into a seperate list is worth keeping the two unused functions. Also makes updating easier.

To be honest, when I'll use STARCODE I'll just scrap all the GUI functions and put there source code somewhere in my script. The easy packaging and GUI functions are mostly useful for mappers who're not using custom scripts.

I hope that STARCODE (or some similar system) will be eventually used extensively in maps that need to store a lot of information in banks (or use save codes). Just thought I'd spread the word to sc2c, too.