I am creating a wiki for sc2mapster and the editor in general. This includes creating a full API on the triggers. The problem is that I don't know what all of the triggers do yet. (I haven't messed with Animations and Banks yet, for example.) So if anyone can help fill in those missing gaps that knows what those triggers do, I would really appreciate it. When this gets finished, it would be a huge help to people who are overwhelmed by the sheer amount of triggers, as well as a good reference to even seasoned veterans. If everyone did just a few triggers, say, one or two (or three, if you're ambitious), then this would get done really fast.
I have finished the Conditions API page, so that page can be used as a template for what the other API pages need to look like. It is essentially:
Example code in between pre tags, showing the trigger's syntax.
A paragraph in quote text displaying the helper text in the editor of what the trigger does.
A paragraph or two describing what the trigger actually does and how it can be useful.
I've already fleshed out the structure of the pages, so now the triggers themselves are all that is needed to be added. Thanks in advance for your help!
P.S. If anyone is willing, the wiki could also use some trigger tutorials, so if you would like to make one, or if you know of a good one that you would be willing to port, the wiki can always use more tutorials (and right now it definitely needs more tutorials).
What are you talking about? Do you mean like all the functions that can be placed in the values (like the conversion functions)? Because that's going to be in another part of the API (It's going to be Event API, Condition API, Action API, and Function API), and I haven't gotten to creating that page yet. It's also going to be a huge page, so I'm going to need to figure out how to organize it first anyway. Let's just focus on the first three APIs for now. :)
An API doc is essentially a place of reference for all the intricacies of a service. Programming languages have API docs that describe all of the built-in objects and functions and say what they do, what values they return, what class/struct/package they're a part of, etc. If you look at the API Doc at the top of this page, it takes you to something similar to that. The problem with it is that it is very unfinished and unrefined, and half of the information comes from pre-release times, so it is horribly out of date.
@Helral: Go
That API is very limited in its usefulness, as a lot of links are broken. The organization is a little weird, and a lot of topics are out of date. IMHO it would be easier to start over in a more organized structure than try to root through the existing structure.
@zeldarules28: Go
I'm pretty sure the user himself is legit. Its just the anonymous troll that we have to worry about. And yes, admins (just me atm) have the power to delete those.
And I would never think of taking over the mapster! The wiki is just for reference and tutorials. It's forum should only be used for topics specific to the wiki, such as suggestions or reports.
Lol....I wanted to make my own website over christmas break but I couldn't think of what to make it about...lol shoulda done something like that. Whatever. I'll stick to making tutorials.
Rollback Post to RevisionRollBack
Feel free to Send me a PM if you have any questions/concerns!
I don't mind adding some information concerning triggers, when I'm bored ;p
Also I'm planning already to add some data stuff like what does which flag mean for the ability flags.
I am creating a wiki for sc2mapster and the editor in general. This includes creating a full API on the triggers. The problem is that I don't know what all of the triggers do yet. (I haven't messed with Animations and Banks yet, for example.) So if anyone can help fill in those missing gaps that knows what those triggers do, I would really appreciate it. When this gets finished, it would be a huge help to people who are overwhelmed by the sheer amount of triggers, as well as a good reference to even seasoned veterans. If everyone did just a few triggers, say, one or two (or three, if you're ambitious), then this would get done really fast.
I have finished the Conditions API page, so that page can be used as a template for what the other API pages need to look like. It is essentially:
I've already fleshed out the structure of the pages, so now the triggers themselves are all that is needed to be added. Thanks in advance for your help!
http://sc2mapster.wikia.com/wiki/Trigger_API_Docs
http://sc2mapster.wikia.com/wiki/Trigger_Event_API_Docs
http://sc2mapster.wikia.com/wiki/Trigger_Condition_API_Docs <- - - - use this one for reference
http://sc2mapster.wikia.com/wiki/Trigger_Action_API_Docs
P.S. If anyone is willing, the wiki could also use some trigger tutorials, so if you would like to make one, or if you know of a good one that you would be willing to port, the wiki can always use more tutorials (and right now it definitely needs more tutorials).
I made a 'getting to know the trigger editor' tutorial and put it on there earlier :D
Anyway, I don't even get what an API doc is. But looking at yours, dont you need to be put in all the conditions? Like not just the operators.
@zeldarules28: Go
What are you talking about? Do you mean like all the functions that can be placed in the values (like the conversion functions)? Because that's going to be in another part of the API (It's going to be Event API, Condition API, Action API, and Function API), and I haven't gotten to creating that page yet. It's also going to be a huge page, so I'm going to need to figure out how to organize it first anyway. Let's just focus on the first three APIs for now. :)
An API doc is essentially a place of reference for all the intricacies of a service. Programming languages have API docs that describe all of the built-in objects and functions and say what they do, what values they return, what class/struct/package they're a part of, etc. If you look at the API Doc at the top of this page, it takes you to something similar to that. The problem with it is that it is very unfinished and unrefined, and half of the information comes from pre-release times, so it is horribly out of date.
@Abion47: Go
just wondering but, why not update that API then? ( http://wiki.sc2mapster.com/galaxy/main-page/ )
Everyone with an account at SC2Mapster can edit those API pages.
!! oh my ghosh there's a forum on the wiki, too!!!! Gosh dang it, Abion, are you trying to take over sc2mapster???!!!
oh and saw this http://sc2mapster.wikia.com/wiki/Slaydon
I don't care about that but if theres a bunch of stuff like that in the future, does somebody have the ability to delete it?
@Helral: Go That API is very limited in its usefulness, as a lot of links are broken. The organization is a little weird, and a lot of topics are out of date. IMHO it would be easier to start over in a more organized structure than try to root through the existing structure.
@zeldarules28: Go I'm pretty sure the user himself is legit. Its just the anonymous troll that we have to worry about. And yes, admins (just me atm) have the power to delete those.
And I would never think of taking over the mapster! The wiki is just for reference and tutorials. It's forum should only be used for topics specific to the wiki, such as suggestions or reports.
Lol....I wanted to make my own website over christmas break but I couldn't think of what to make it about...lol shoulda done something like that. Whatever. I'll stick to making tutorials.
@Abion47: Go
I don't mind adding some information concerning triggers, when I'm bored ;p
Also I'm planning already to add some data stuff like what does which flag mean for the ability flags.
I might contribute. I'm pretty busy with my RPG project right now, but I'll probably have some time in between programming sessions.
@Helral: Go
That would be awesome. The data editor is definitely something that we can't have enough help with.