I think it would make more sense to keep functions and actions separate. I don't see a reason to combine them (though I would like to know what the rationale would be if they were combined).
As for documentation of co-op stuff, that would be nice, but not an immediate priority. As they are mostly built from natives in the basic libraries, having basic library documentation might actually help people decipher co-op. Then more specific concerns can be addressed as needed afterwards.
If you look at legacy wiki they were combined for some reason and this was carried over into the current one. I think it had to do with how they file dumped the action/function definitions. I also feel they should be separated.
So you are saying start with natives and then work up from that?
Rollback Post to RevisionRollBack
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
I know I haven't been there for months... but omg, I just can't find the time to settle down for few hours and focus on something, either the wiki, a sc2 map, or even just gaming.
I really wish to finish what I started, but I think the best would be to help you with suggestions and stuff that could be great to do... I feel sorry for not being able to be there more. It's really something that I wanted to complete.
Eatch of these pages contains main navigation links between eatch parts. They also contain navigation links within the same page such as "AI, Animation, Banks, Cameras, Dialogs..." If a navigation link contains nothing (no trigger for example) it will not be a link, but the text will stay there for more uniformity between eatch categorie pages.
The idea is to move all events together, all actions together, all variables together... in such that when you enter the page, you can either use the navigation to find where is what you want to find or the navigator search Ctrl+F to find the exact text in the page. No more digging into sub-pages. All information will be easy to find.
The sub-category pages like this for example "https://sc2mapster.gamepedia.com/Triggers/Category_AI" for AI, will instead contain any usefull information relative to that category "AI" in this case. It could also contain links to usefull tutorials about AI. It could contain usefull information about what other things you would need to make this category works fine. It could contain examples of usage, most common uses, stuff like that. For eatch sub-category (...Cameras, Cinematics, Game, Math, Order, Ping, Selection, Timer, UI, Unit...)
The downside of doing it this way is that the main pages will be huge. But since mapster just got updated to a new faster platform than it's mostly fine. Navigation links are there to help navigate within the page. And if it is really a problem, there might be another solution about using some kind of "spoiler" function to show/hide information within eatch section.
Another downside is, it removes the trigger sorting that was used in the wiki before which was based on how you find them in Built-in Library of the editor (like the link above which uses sorting by group of actors of the same usage and not alphabetically overall). But since you rarely search triggers in how they are categorised in the library, I though it would be more usefull to sort them as how you find them when trying to find triggers when doing mapmaking, which is sorted with the main category (Animation, Bank, Camera...) and then sorted alphabetically. So the sorting you see in the editor is what you see in the wiki sorting.
That's what I was aiming when redoing the trigger part of the wiki. Lots of copy pasting between the sub-sub categories to get that all in the same page sweet and easy to find. Then remove the useless pages and modify the sections like said before with more information about what you can do with Ai, Camera, etc.
Before slacking on the job, I was working on continuing to regroup the Actions together. I was going one by one between the wiki and the trigger editor to make sure that all new triggers are included. There was still more than a day of work just for that to do. Once all the actions are in and that all the wiki trigger is ready, we'll have to remove the useless pages and relink few parts correctly like the main wiki page. Oh and... relink many other individual pages to be able to navigate back where you was. Ex.: when you are in condition category and click on Action Damage that it can links back to the category and not to the main trigger page. That's what I would call polishing, but still it would be usefull.
Then, it's all good to go for tutorials linking to triggers and stuff. It will be great. I'm sure about that.
Note: About functions and actions, to me they are truely different things in such that if you try to find an action and you search for a condition, you will not find anything and vice versa. Conditions are "if xyz..." actions are "do xyz..." They should be separated and the distinction explained.
We could also create a reference page which shows the main links and how they are written and how to use them in the wiki like:
[[Triggers/Category-Events]] (to go to a category)
[[triggers/Category_Actor|Actor]] (to go to a sub-category, note the difference in capitals and the underscore)
[[triggers/events/player-sends-ai-wave]] (to go to a specefic page)
Sadly, in rare occasion the links are shorter than the description or slightly differ from it. At best anyone who creates a new pages with links, he should make sure these does not exist at first. Redoing all the page naming for uniformity would be a monumental task that I doubt anyone is willing to do. I think risk vs rewards tends too much on the risky side for that. So let's just get used to how it's named.
Records are as simple as this, a group of variable. It just needs a basic description of what it is and heavily suggest to use them to organise your variable and that's it.
Functions are the same as conditions, kind of. All conditions are functions. Not all fonctions are conditions. But overall, they differ by just a little.
Definition like Action Definition are pretty much the same thing as triggers with some variation to it. Again, doesn't need a whole page dedicated to it, just a good explication of what it is and again, to suggest to heavily use them if you don't need an Event.
All these can be added to the main trigger page sort of like this, but not limited to and definitly better polished and explained. From the ground up so anyone could get into the information found there and understand how a trigger works, what contains a trigger, etc.
What do you mean by "reformatting most links"? Exacly what I said above about the differences in the links so they will be more uniform, thus better organised and prevent duplication?
Redoing the links will be a monumental task, but fully feasable.
I have just a minor concern, are there still that many mapmaker that uses the wiki and make maps? It feels like just few people actually do triggering, and barely few new maps seems to come up in the arcade. Is it worth to rename all links for simple uniformity?
The main page is great, although I feel like it would benefit the same navigation links as the other main pages for the top.
You used the redirect fonctionnality for the wiki for many main pages which actually confuse the links... i mean, when you was say on the "Event" page, the Event link on the Event page was no more a link so you knew you was on the Event page. Now since it's all relinking, its not on the original page so the wiki thinks its another page thus you can click on it again and again... I though when you was going to rename the pages, in fact it would have not been relinking.
I'm a bit confused as where are the variables, conditions, etc. I guess you know what you are doing. I miss so much the editor, learning new stuff, helping others, making awesome map...and the wiki. Sorry for the half-way update I left behind, it was all well-intentioned.
Yeah the relinking is a work in progress. If the page may be important and I have not yet got around to changing the link on other pages I leave a relink behind. There never was a list of trigger events to begin with that is why it is empty. If you would give me those pages in question I will look into them. Most of the trigger pages just inherited the legacy wiki syntax so have lots of - symbols so I will have to update them all.
There were 4 pages with the same info on types. I synced them onto the types page (including your variables page). There was another page linked to the main page that again was a types duplicate so I decided to make that variables and records. Only later did I find you already had a variables page that only had the info of the types page. With conditions you had mistaken functions for conditions so I split the two pages. A lot of the trigger editor sections of the wiki were circular in logic with an amazing amount of duplication. To be honest I would like some help with sorting everything. By the way how do you like my page on action/event/function definitions?
Anyhow I am working on it. Although I am putting off updating that toxic page of a code of conduct LucidIguana made. Even the discord mods hated it.