SC2Mapster

@avogatro: Go

Very nice. I'm still trying to get into the triggers. Looks like I need to step it up a notch.

@avogatro: Go

I have to say, the TriggerString looks really complicated to me, and to be honest I don't think I could really wrap my head around it, much less write a parser for it. For me at least, it would be much easier to do each trigger individually, even though that would take forever...

@Sixen: Go

Sorry, dude. That bites.

I've been speaking to vjeux on how he does his parsing, and as I said to him the trigger library seems to sort its triggers differently than the GUI library. For example, all of the broken links on the main page for trigger categories are categories that exist in the GUI library that don't in the trigger library (Selection and Unit Selection are actually the same category, but named differently.

It also only factors in the base dependency. It doesn't include triggers from, say, the Campaign library.

@avogatro: Go

I think I just found a way to view the files in the editor. Go to the trigger editor and click Show Libraries. I feel smart...

Edit: This is how to view the GUI function of the triggers, not the script function...

Quote from avogatro: Go

Object, Object Value, Link, Inheritance Reference: Object Types, Value Types, XML API Docs

Some time I just don't understand what did SCDude mean with object and link. Is Object Type = Class? CAbil or something like that?

Value Type: Data Type?

Inheritance is ok, but wtf is link?

Yeah I would like to know what these are since they are the last broken links on the main page.

Also, I would really like to know what vjeux did to get the info for the triggers, because I'd like to fill in the missing pieces as well as find out what's deprecated. Since there is both a Selection page and a Unit Selection page, I'm guessing that some information is now obsolete.

@TheAlmaity: Go

I will claim at least a part of the triggers. Just waiting until Sixen tells me if there's something special about the trigger API that I should know about.

I wish I could claim the data editor, but I'm not nearly confidant enough in my abilities to start telling other people what to do.

@Tattsoo: Go

Is this a reply from a user of SEN?

@TheAlmaity: Go

Awesome and informative! Just since it's a subtopic of Data Effects, the link probably should be on that page.

Ok, I tried to create the page for the markup link (http://wiki.sc2mapster.com/kb-markup-types/), and it said that I don't have access to modify that page. I think this is the case when someone without mod privileges or even just admin privileges tries to create or modify a root page (one without any slashes before it). So could someone with appropriate priviledges create it? All you have to do is go to create page, name the page "kb-markup-types", and copy the text from "http://www.wikicreole.org/attach/Creole1.0/wikicreole1.txt". If nothing else, this is a good placeholder until we figure out what exactly to do with that page.

Where do you upload the images into mapster to use in the wiki? Because I've just been using photobucket, and I've noticed that people are uploading their pics as attackments.

EDIT: Never mind. I found it.

@Sixen: Go

All you would really have to do is alter the pages so that they either give the GUI name of a function and it's scripting counterpart, or the other way around.

And you said that Vjeux had his coding method of getting the triggers? Does that mean that the trigger API is structured in a way that would be difficult to add to or modify? Because it is missing several categories (I will include the corresponding icons):

• - General (the "-" is important)
• Campaign
• Challenge
• Chat Bubble
• Comment

Also, the API should include something to say what dependency a trigger needs, so that when a person finds a trigger they really need they don't freak out when they can't find it in their map.

Wow. Suddenly everyone's so eager to fix the current wiki. I guess seeing as I prompted such a fervor, it's only appropriate that I take part as well. I don't really care if all the effort's done on my wiki, the sc2mapster wiki, or even galaxywiki. As long as there is effort being done somewhere, my goal has been realized.

Let's do it to it, people.

My biggest annoyance with the trigger API is that it gives the scripted versions of the triggers, which sucks for people who can only use (or just prefer) the GUI.

Quote from peeeq: Go

For big tutorials a wiki is not suitable in my opinion because people want to be seen as the author after they have spent some time in creating a long tutorial and many people do not want their tutorials to be edited by someone else.

But that's the whole reason behind putting tutorials in a wiki where they can be edited by anyone. As the pass of the beta showed, a lot of tutorials' content becomes obsolete or deprecated, and usually after someone writes a tutorial they just abandon it to the masses, and it never gets updated with the new content.

But I spent a lot of time looking at the GalaxyWiki, and it does seem pretty legit, even if it's really hard to navigate. I think that I may start moving some of the stuff I've gathered so far over to there, then start working off of that site. My purpose in starting my wiki was because I hadn't found anything that did what I wanted the wiki to do, but GalaxyWiki seems to fit the bill.

Quote from Lonami: Go

Wikia's forced skin is terrible

I completely agree. That's why I'm sticking with the default skin that looks like wikipedia.

Quote from peeeq: Go

Why not use galaxywiki.

GalaxyWiki is a wiki about StarCraft II in general. It has a few tips and tutorials about mapping, but it ultimately has the same problem I talked about before about sc2mapster, in that it's trying to incorporate every aspect, and some of the "lesser" aspects aren't getting the attention they deserve.

However, if you all really think it's not necessary, I'll drop the wiki. I'm still going to make a trigger API somewhere, because it is something that is desperately needed. (I also plan on incorporating a data API sometime in the future.)

@Sixen: Go

I just started the wiki because as I said before the wiki on this site looks nice but is somewhat unorganized. There are broken links all over the place, and a lot of the articles are horribly out of date. Also, as QueenGambit said, the wiki on this site is kind of obscure in spite of there being a link at the top of the page, and it is never referenced. (I myself didn't even know it was there until about a month ago.)

My goal in creating this wiki is just to give the current wiki a bit of a jump start, porting over tutorials and at the same time screening for outdated material. Also, as zeldarules said, mapster is incredible awesome for its project publishing services and the help community, but the tutorial section is in dire need of help. Correct me if I'm wrong, but I don't think that the tutorial portion of the wiki has been updated in months, even though people have been writing tutorials. Ultimately, I wanted to separate the community portion and the reference section of this site, so that each section can do its job in the most efficient and helpful way possible.

Sorry about the ads. It's mandatory for a free site to have those ads. However, if you install Adblock Plus (link is in an above post), you will never see those ads. I highly recommend getting it anyway, because it's just so nice to have an ad-free browsing experience. :)

Why is it bad that the wiki is owned by Wikia?

@MathiastIsOP: Go

"Pot. Are you there? This is kettle, over."

Thanks for the free bump, btw.

I'm hard at work making the trigger API, and I'm getting barebones laid down at the moment. Conditions is done, and all the events are in place to get their info, as well as the actions from -General to AI Advanced. Would appreciate it if anyone could stop by and plug in the info for a couple the triggers I've already added. I'm not asking for eternal loyalty to the project, just stop by and jot down what you can in 10 or 20 minutes. If I have to do this totally alone, it will take me forever.