Here's a few helpful pages [for learning to edit the wiki]:
https://docs.megaglest.org/Glest:Policies
https://docs.megaglest.org/Glest:Style_guide
https://www.mediawiki.org/wiki/Help:Contents
https://www.mediawiki.org/wiki/Help:Getting_started
As well, because this is the same software as Wikipedia (Mediawiki), most formatting for it works here as well, and Wikipedia has some very good guides and policies, many of which are used on our wiki, but not directly mentioned.
What a page must have:
- At least one internal link. If a page does not have an internal link, Mediawiki does not consider it a page (and thus, it will not appear when searching, nor on the page counter in the sidebar). Internal links are easy, as Glest (https://docs.megaglest.org/Glest), Tileset (https://docs.megaglest.org/Tileset), Faction (https://docs.megaglest.org/Faction), Mod (https://docs.megaglest.org/Mod), Map (https://docs.megaglest.org/Map), and many more very popular keywords have pages, and if there is no way to add an internal link of at least some kind, you are doing it wrong.
- It must be linked from another page, anywhere. Pages can be imagined as a web, starting with the main page, which links to most of the popular pages, which in turn will link to all the individual pages. If a page does not have anything linking to it, it is considered an Orphaned page, which also annoys Mediawiki. Factions/Techtrees can have pages linked from Mods/List (https://docs.megaglest.org/Mods/List), while maps have Maps/List (https://docs.megaglest.org/Maps/List), and tilesets have Tilesets/List (https://docs.megaglest.org/Tilesets/List). Even scenarios have a page at Scenarios/List (https://docs.megaglest.org/Scenarios/List).
- An introductory paragraph. This is something many older pages lack (and I add it as I find pages that lack it). This is the first paragraph in the article and is NEVER preceded by any type of header. This paragraph (or paragraphs) should summarize what the article is about, or the point of the page. Please do not start pages with a header. Even if the page would seem obvious by the title what its about, always start with an introductory paragraph. It doesn't have to be long. It can be one sentence, but it's gotta be there.
What a page should have:
These are not necessary when creating a page, especially if the page is a stub or there is insufficient data to expand the page, but you should try to get these anyway.
- If the page is a faction, map, tileset, techtree, or unit, it should have the associated infobox at the very top of the page. This summarizes the page, and, like most templates, you will have to use code display to insert them, so you can't use the WYSIWYG editor (I strongly recommend that if you are experienced enough, to set the code version as the default by disabling the WYSIWYG editor in your preferences). They are all named accordingly, so the infobox for factions is found at Template:Faction (https://docs.megaglest.org/Template:Faction). Likewise, maps is Template:Map (https://docs.megaglest.org/Template:Map), etc. The instructions for using these templates can be found on the associated page, along with examples. Even more examples can be found by looking at pages that are using the template (every template is used in at least one page). Please avoid making new templates for any of these categories (for example, I noticed GIS made a unit template, which, ironically, has not been used on any pages). Sure your unit might have more features, but those can be discussed in the actual article. The infoboxes are meant to summarize the faction/unit/whatever in a standard (meaning the same across all like pages) way.
- Avoid using external links in the body of the article unless necessary. Try and group the external links at the bottom of the article, under a new level 2 header "External Links". Whenever possible, link to an internal page. So if you mention GAE in your article, do not link to the sourceforge page of the GAE project, but link to the actual GAE page (https://docs.megaglest.org/GAE).
- Relatedly, try and have a "See Also" section at the bottom of the article (above external links) that links to associated pages (even if loosely). This gives the reader more pages to read when they finish reading one page, and is an easy place to add internal links (for the minimum one internal link rule previously mentioned). Even if the link was mentioned multiple times in the article already, post it again, because people tend to read other pages after they finish reading the current one, rather than while in the middle of it.
- The Glest Wiki is known as the "Glest Wiki". Wikia is just the host, who modifies the MediaWiki (note the absence of the trailing "a") software on which the Glest Wiki runs on. The MediaWiki software is the same software used to run Wikipedia, and thus the origins of the word Wiki (I could go into a long dialogue on what Wiki means, but just to sum it up, it means "fast"). This might sound a bit of a nitpick, but no more so than those folks at Lua (http://www.lua.org/about.html#name).
In other terms, I think I may go and try to fix up the main page. I tried to fix the image on the main page which is too large for the size of the article, but realized my HTML code wasn't working correctly... More oddities... Anyone know a good documentation on using HTML on wikias? I'm sure wikia's code is fine for internal links and the like, but for advanced formating, nothing beats HTML (noticed there was some there, so the style att MUST work, yet it wouldn't for me).If what you are only talking about formating, I'd say CSS is the way to go:
Another problem with those changes is in the wikimedia:CSS coding language.
Firstly, you can't vote for me cause I ain't available! heh @ jda :PWell, tough, I'm still voting for ya... :P
The easiest thing to do would be to use the artwork Glest theme by Omega. Based on Diablos3 theme by Vaun using media by Josepzin from here and graft them onto the main (front) page - wikia allows for large banners and web-styled themes just like we see here. These things are done via use of wikia media-frames and blah blah blah.That sounds good to me (for someone else to do ;D ). I believe it will look good if its looks are similar to those of glest.org and glest.org/glest_board. ;) :thumbup:
The wikia information pages are in decent shape.You mean those of the Wikia itself for editing wikias in general, not the Glest Wikia in particular, right? :|
The glest wikia sub-pages need to be renamed/optimized - search engines do not like the current naming conventions.As long as that doesn't break internal (re)links. ;) :thumbup:
I tried to copy the Starcraft main page style/formatting but it was never finished - and apparently no one cared until I actually began working on it - and at that time they became very keen on wikia work but soon thereafter lost interest in working on the wikia - effin' funny how that works! yes?I plea myself guilty as charged. ;D :-[
I care! :angel:That makes... three of us?... ;)
In my opinion, there's a few things I look for in an article:100% agreed! :thumbup: :thumbup: :thumbup:
-Proper understandable english
-Organization
-NPOV
I consider having tons of information USELESS if it is too messy to read.
@Concerning wiki code/html: Wikicode is good for many things, particularly headers (==My Header==, with more ='s for smaller headers) as well as internal links ([[my_link]]). HOWEVER, it doesn't allow for advanced styling, which should be done in HTML. I did notice some HTML on the main page using a div tag with a style attribute, which is my favorite styling method (well, second favorite, after individual CSS/HTML pages).Again... breaking coherence is what bothers me. I mean, look at what you get when you go to the main page alone: There is this kind of frame with some custom colors (which BTW disregard the fact the links colors DON'T fit that color-theme) and everything around is just your regular wikia colors. Looks d*mn ugly to me. :P
The wikia could also REALLY use a cleanup at the sidebar on the left, where the main navigation links are. I'm used to using THESE for navigation, NOT a bunch of links on the main page... :look:You're welcome to by me (in case my opinion matters any) but do be aware of SEO impacts! The links in there are what will probably come under the "Glest Wikia" website "quick links" on your search engine and what you'll get when searching for such particular subjects. :look:
There's also some general bad web design techniques scattered throughout the wikia that not only make it more difficult to navigate, but can look bad and add a negative appeal to the wikia.Like what I mentioned about colors above?
We want more people on the wiki? It needs better quality.I think that works both ways... If we want more quality, we need mor quality people working on it too! ;)
I am not an expert in wikia code, nor pretend to be, but I do have some degree of experience with it and have spent a good amount of time on other wikias and have admired their quality. In particular, one I found that was very good looking is the runescape wikia, where I've spent the most time.I'm pretty sure you're one of the most qualified for the job, much more than I am no question about it! ;) :thumbup: 8)
To adapt text to the standards and facilities of a wiki.http://en.wiktionary.org/wiki/wikify
Yeah, already looked at that/saw that... I was kinda wondering if someone had a better... ::)Quote from: wiktionaryTo adapt text to the standards and facilities of a wiki.http://en.wiktionary.org/wiki/wikify
Ok, anyone know who created the wiki? I talked with martino and it wasn't him, and he doesn't seem to know either...Maybe this person? Not sure...Only person in the admin category...I think :|
Jda, good luck with password recovery (it should work well, assuming you use the same email).Yes, good luck :) :thumbup:
You can get admin rights at wikia gaming central. Its that simple.Alright, I did not find it there, but I guess this will maybe work too... ::)
There are a handful of people on the Glest Forums that are willing to all lend a hand to help fix this, including me, Trappin, and Ultifd. We would like to see the Wiki become a standard in our community, especially as Glest's download count grows (over 1 million since 2001's beta). It would be greatly appreciated if you could make one or all of us admins of the Wiki so that we could fix it up and improve it.
This is where the rubber meets the road!Somewhat true...yeah. ::)
I figured there would be a flurry of activity now that the last hurdles have been cleared.Yeah, well,...we all wish.
Ah, so you won't actually do anything on the wiki ? No editing?No, just not for today... :|
Don't get me wrong here - its fun to tell other people what to do !Alright. :|
# Unit XML
9 days ago by Unregistered contributor
# edit InstallGlest
11 days ago by Unregistered contributor
# edit Glest Advanced Engine
14 days ago by Zaggy1024
# edit Main Page
15 days ago by Charitwo
# edit Map editing
16 days ago by Thokul
(Next)::)
# edit Mods
16 days ago by Ultifd
I've got some free time tonight. Give me an article to fix up, and I'll see what I can do.Hmm, probably the main page needs the most work, if you could contribute on editing that...that would already be great, IMO... ::)
Hi, i have decompressed a units(deamon) tga file and redesigned the texture, but then i compressed it with its text file and try´ed to start it in g3d viewer it says "id field is not 0" what is wrong, and how do i fix it? (sorry if i spelled wrong somewhere)From this
This one probably needs to be deleted:Huh.
https://docs.megaglest.org/Developing_ideas (https://docs.megaglest.org/Developing_ideas)
Feature requests? On my wiki? It's more likely than you think!
Why?I could do some art...
1) we don't have artists willing to contribute to the wiki.
2) we don't have coders with the experience to setup wiki templates.
3) we don't have users willing to commit time and effort to a community project and see the project through to completion (example mod: dark magic)
I arrived at this conclusion after 1200 edits and six months of wiki work.
Code: [Select][img]http://img713.imageshack.us/img713/404/darkmagictitlewikia.jpg[/img]
Hmm, that will be helpful Archmage. I might change some of the screenshots to updated more ones, like this one
http://images4.wikia.nocookie.net/glest/images/0/08/Install_Mods.jpg Tongue
But the title should be "Install Mod" with a space. IMO.
Another thing is that for megaglest, it will be different/it is. We now have a "My data" folder...so maybe you can ask softcoder about that. And other things in the future.
Uh dude, that's from the old guide. ::) If you scroll down you'll see the new one.Oh ok, I must have missed that.
NOTE: The version number is just for kicks. :P
Oh, I didn't see that, I'll fix it right now.....I don't think I can, I don't know how to change the page title....... :|OK, I changed it. I just wanted to make sure...although any registered member of the wiki can move a page.
I'll worry about that later.Yeah, was just telling you. It will be important in megaglest.
I also forgot I wanted to mention a good site for those learning how to edit the wiki. The official site is help.wikia.com (http://help.wikia.com)Yeah, it is kinda helpful. If you don't know how to do something, check it. It covers a lot...not all, of course. But most of what is needed...
Also, I recently contacted Wikia Central and got glest.110mb.com taken off the spam blacklist, so now it should work fine if you wish to use it for links.Nice! :thumbup:
For a list of Double Redirects, click here. To "solve" Double Redirects, either point it to the actual page to be redirected to, or delete it if the page is meaningless.If needed please rephrase it and put it on the right place on that section, thanks.
Quoting sources is unnecessary (though, optional)Really? I think it is half/half. A lot of times it is unnecessary, but on the other hand it is very important to have sources...Especially now, with people adding new content and info.
(first page to get this slapped on: MG/FAQ (https://docs.megaglest.org/MG/FAQ), unfortunately, MegaGlest isn't my strong area, so that's best left for other editors).Could you tell me what is wrong with it? (I'm not saying nothing is wrong with it)
They should be made with the first letter of the first word being capitalized, and all following words lowercase (ie: 'Dark magic')Hmm, currently the DM page is not even like that. :-/
Indeed, most pages aren't, but that can be fixed by moving the page and creating a redirect. Though, the case isn't a huge deal, it does help greatly in searching and it's a good idea to standardize the naming of the page, so that if you want to go to a page, but don't know the exact URL, it's still possible to type what it most likely is and end up in the right place (I've done this before on other wikis, as well as wikipedia and similar sites).QuoteThey should be made with the first letter of the first word being capitalized, and all following words lowercase (ie: 'Dark magic')Hmm, currently the DM page is not even like that. :-/
Anyways, why should it be like this? Is it for the search engines? Or? Because in the end there will just be redirects for this, or related...
Allrighty! After hours of work, I've finally got the template page up.Awesome! I was looking for a page for that before, but since there wasn't one I knew you would create one later.
I've also filled in the primarily empty Magitech page, and will proceed to do so with the likewise empty Tech and Magic pages.Thanks
I think having pages for individual factions, techtrees, and units is a great idea, and would like to see more pages (Magitech has been started) and certainly more editors could be very helpful for such massive tasks.Yeah, it is a great idea. Although most of the time when I create the pages, I kinda fail to have information on it...just basic stuff usually. Hopefully others will help.
A quick note that pages for individual maps ARE allowed, though because of the large number of them, and the possibility of name conflicts, they should be a sub-page of 'Maps' (ie: in the forest map would be 'Maps/In_the_forest'). Happy wiki-ing!Good idea. Although I still don't know why there is a Glest Map wiki...but anyways speaking of maps, should the image for it be the map editor image or should it be an actual image of the map (probably/like when you zoom out all the way in GAE/MG.)?
Stubs are fine. By the way, with the templates, its worth mentioning that if you create a stub (a short article with just the basic information), please add the {{Stub}} template to the bottom of the page. This will automatically add it to a stub category (allowing editors who wish to expand stubs, such as myself, to easily find them), as well, lets the viewers know the article is not fully complete and may be expanded in the future.QuoteI think having pages for individual factions, techtrees, and units is a great idea, and would like to see more pages (Magitech has been started) and certainly more editors could be very helpful for such massive tasks.Yeah, it is a great idea. Although most of the time when I create the pages, I kinda fail to have information on it...just basic stuff usually. Hopefully others will help.
Well, I would think that having an actual image of the map is infinitely more useful, since most people can't read the map editor well and even those that can may be surprised by the actual output. One can post the map editor image in there as well though.QuoteA quick note that pages for individual maps ARE allowed, though because of the large number of them, and the possibility of name conflicts, they should be a sub-page of 'Maps' (ie: in the forest map would be 'Maps/In_the_forest'). Happy wiki-ing!Good idea. Although I still don't know why there is a Glest Map wiki...but anyways speaking of maps, should the image for it be the map editor image or should it be an actual image of the map (probably/like when you zoom out all the way in GAE/MG.)?
Stubs are fine. By the way, with the templates, its worth mentioning that if you create a stub (a short article with just the basic information), please add the {{Stub}} template to the bottom of the page. This will automatically add it to a stub category (allowing editors who wish to expand stubs, such as myself, to easily find them), as well, lets the viewers know the article is not fully complete and may be expanded in the future.Oh yeah...that is the word and template for that...
Well, I would think that having an actual image of the map is infinitely more useful, since most people can't read the map editor well and even those that can may be surprised by the actual output. One can post the map editor image in there as well though.OK, but if people were to add to the map editor image too, where would they put it on a map page?
Well, as you know, the {{Map}} template has a place for on picture, which should generally be an actual picture. After that, we can have whatever there is for an article (ie: description of the map, etc) and the image can be on the page too, generally as a thumbnail, floated to the right (worth mentioning now that all thumbnails should be floated to the right unless they would benefit more from being placed as normal. I think right is the default as well, but not totally sure.QuoteWell, I would think that having an actual image of the map is infinitely more useful, since most people can't read the map editor well and even those that can may be surprised by the actual output. One can post the map editor image in there as well though.OK, but if people were to add to the map editor image too, where would they put it on a map page?
Wow, thanks. Although, I think it's rather you that should be featured...for obvious reasons. :-/Nah, you deserve it bud. Besides, do you know how bad it would look to go, "User of the month: Meeeeeee". ;)
I'll probably also create some more stubs or more pages of techtrees, factions, and/or maps later...Yes, we'll eventually need pages for all the map editors, as well as, my dream is to see a full Wiki. After all, the Granity rule states that no matter how small it is, if it's glest related, it deserves an article in the Wiki. I recently made a G3D page, and would love to see some technical data about the format from those who are more experienced with it. As well, I'd like to eventually get started on the full unit list for Magitech, then expand onto my own mod, military, which is getting a bit left behind in all the edits, but first of all, I set my priority as fixing up all existing pages. Better off to improve existing pages before making more. Particularly the pages linked from the main page. I also noticed some of them have names that are unnecessary and actually detrimental for searching, and am moving them to new names, leaving behind the redirects (note: if you plan to do this, keep an eye on the double redirect page to make sure you don't accidentally create a double redirect).
I do wish others could help more, as it would be really...helpful. We're all busy, but I'm pretty sure that some people can give a little bit of their time to help edit or create a page... Especially for people who have made maps or mods...
For the map editor page, I'm kinda confused about it...after all, we have the new map editors, which are both (at least a little bit) different from each other. Then we need to update info...etc.
RfD...Request for Deletion. Wouldn't just "Deletion" be better? Maybe not, but I guess I'm just thinking that it would be better since it has always been like that before and at other wikis... :-/Good point. I can't believe I forgot a reason slot for that. :P Added. As well, I created a duplicate of {{RfD}} called simply {{Delete}}. It's the exact same, though RfD is the main one mentioned on the Template page. For the most part, most of my Wiki skills are orientated from other wikis I frequent, such as the Runescape wiki. The set a good example to me of what a wiki should be like.
Anyways, moving on... Now it isn't possible to put a reason...
Also, the template page is supposedly up for deletion (https://docs.megaglest.org/index.php?title=Category:Requests_for_Deletion&action=edit&redlink=1)... :-/ I guess that can't be fixed, or can it...
Nah, you deserve it bud.Well, I think I would deserve it more some other time...or maybe once I create all those pages it'll be ok. :O
Besides, do you know how bad it would look to go, "User of the month: Meeeeeee". ;)It might be bad, but that would be the only thing bad about you being it. :-/ I mean really, the wiki is much better only because of your editing...mostly. For example, the templates, the main page, and the info... Oh well, everyone knows you're like the good dev of Glest, MG, or GAE... just for the forum and the Glest wiki :O Anyways...
Yes, we'll eventually need pages for all the map editors, as well as, my dream is to see a full Wiki. After all, the Granity rule states that no matter how small it is, if it's glest related, it deserves an article in the Wiki. I recently made a G3D page, and would love to see some technical data about the format from those who are more experienced with it. As well, I'd like to eventually get started on the full unit list for Magitech, then expand onto my own mod, military, which is getting a bit left behind in all the edits, but first of all, I set my priority as fixing up all existing pages. Better off to improve existing pages before making more. Particularly the pages linked from the main page. I also noticed some of them have names that are unnecessary and actually detrimental for searching, and am moving them to new names, leaving behind the redirects (note: if you plan to do this, keep an eye on the double redirect page to make sure you don't accidentally create a double redirect).Yeah, that is true...
(To be honest, I'm not even 100% sure what other logged in users see... Anyone wanna share? I assume they still see the default for now.)I saw...just the old format of the wiki page, with no skin. So everything was white...cept the ads...
Am I the only one who thinks the layout is much too narrow? I always have to scroll sideways to see all the content in the XML examples.Yes, I agree too. Can we can do anything about it? Since that is just how the new wiki layout is...
I *can* do edit it, but am not allowed. The stupid new TOS means you can't change the width of it for everyone. Likewise, you can't modify or move the GUI elements, nor can you remove the pointless image attribution. Frankly, I'm not the only one upset with the new TOS, but nothing I can do about it. It's way too narrow though, you're right... You'll have to try and keep that in mind when you edit.Am I the only one who thinks the layout is much too narrow? I always have to scroll sideways to see all the content in the XML examples.Yes, I agree too. Can we can do anything about it? Since that is just how the new wiki layout is...
edit: unless Omega can edit it...not sure if he can.
Hmm...can you create a tileset template, please.Done. (https://docs.megaglest.org/Template:Tileset)
Are you slackin'? ;D (In all honesty just because I have a section on the glest guide doesn't justify for not having a wiki article on it. (for the record: my dream, a wiki with all the popular factions and every single unit and upgrade in them!) Besides, that elves webpage I made was totally amateurish and I'd rather forget it (it remains largely for posterity). Though, I did like the concept of drop down menus, though next time I will code said feature myself.)I know :O , but I just feel that since you already have a good guide there, then I'd kinda want to transfer the info, and then...ugh, I'll just do it in a few days. But uh, I haven't been slackin' ;D , the community has...it's always been me or you when we create the pages, or even add information to them...(mostly).
Hmm... can you create a background image, please.Hmm... that's not really my expertise. :| Maybe PM Modman?
Page Request: Glest Blog... Or maybe just add a "stub" page, and I'll add more information to it. I have trouble starting pages like that...Sure thing.
Can you explain why things are messed up on the Japanese (https://docs.megaglest.org/Japanese) Page? I don't understand why, and it's really annoying. Can it be permanently fixed?I'm not sure what you mean? What should it look like?
Also should we create a section on the "Engines Page" for Comparing the Engines' Tools (G3D Editor and Map editor) Or should it be a separate page?I don't really consider them a part of the engine (I use MegaGlest's map editor and G3D viewer even when making a GAE mod!), so I'd go with a separate page, preferably on the existing (at least, I think existing) tools page.
https://docs.megaglest.org/Special:DoubleRedirectsAh, yes, I kept forgetting to mention this. I posted this on your talk page at the wiki today. It's because I requested a name change to the wiki, from "Glest" to "The Glest Wiki" (because having a page where the titlebar would read "Glest - Glest" sounded a lot worse than "Glest - The Glest Wiki". However, Wikia changed the project namespace too (that is, the namespace where we store pages related to the wiki, such as our policies (namespaces can be denoted by their prefixes, such as "Glest:Policies"). Thus, it broke all the links. I tried to manually move them back to the old positions, but didn't completely understand how namespaces are created, so those pages ended up considered mainspace (that is, pages not in a namespace, such as all the article pages). I have a pending conversation with Wikia, and have already moved them back to their old pages (noting that links are likely broken) and now we just have to wait for them to fix that. That's the reason the double redirects are WIERD. But please refrain from editing them, as I'm not entirely sure if pages with the "Glest:" prefix will be kept. Most likely they will be lost and the pages with the "The Glest Wiki:" prefix will replace them. I backed all the pages up to be safe.
The DRs here don't make sense... :confused:
I'm not sure what you mean? What should it look like?Well for the "Units" part of the page, the images and text looks squished almost always, and people would have to press enter 8 times or so to make them even. (But weirdly, when you preview it, it looks fine.) :-X
Ah, that's a problem. I hope Wikia fixes that sometime...Ah, yes, that's because of Wikia's poor choice of a skin, where we not only have the content area compressed to 1000px, but we don't even get to use that much. Notice the sidebar with the recent edits, recent images, etc? That takes up a fair chunk of that 1000px, so leaves us with very little space, giving that cramped look you see. For some reason, the sidebar does not appear on the preview, so that's why it would seem to have more room then.QuoteI'm not sure what you mean? What should it look like?Well for the "Units" part of the page, the images and text looks squished almost always, and people would have to press enter 8 times or so to make them even. (But weirdly, when you preview it, it looks fine.) :-X
I finished revamping the tilesets page. (Finally!) I suppose it could be polished a bit more, and of course be updated too. https://docs.megaglest.org/Tilesets/ListNice job Ultifd. I'd like to propose we make download links for them all though, so that players who don't have or can't download the megapack can still use them on one of the other engines. Pretty much every one of them has a link elsewhere, except maybe a couple like pine woods which we could just upload ourselves.
I don't know about that. I think most of the megapack tilesets will soon have cliffs textures, and I'm not sure if then the tilesets would work with GAE...Never mind, found it. It's "In the Forest". And no, megapack tilesets will not break GAE or vanilla Glest. They will just ignore the 6th texture. :)
OK, awesome. One day I'll upload them on gamefront. (Faster for people than mediafire, has public stats.)I don't know about that. I think most of the megapack tilesets will soon have cliffs textures, and I'm not sure if then the tilesets would work with GAE...Never mind, found it. It's "In the Forest". And no, megapack tilesets will not break GAE or vanilla Glest. They will just ignore the 6th texture. :)
Some of the existing links might be broken too. I noticed that when making the volcanic page, so had to reupload toOK, awesome. One day I'll upload them on gamefront. (Faster for people than mediafire, has public stats.)I don't know about that. I think most of the megapack tilesets will soon have cliffs textures, and I'm not sure if then the tilesets would work with GAE...Never mind, found it. It's "In the Forest". And no, megapack tilesets will not break GAE or vanilla Glest. They will just ignore the 6th texture. :)
Addonwise=Compressed, right?Non-solid 7z (or zip, but 7z beats it by far) in a folder structure relative to the installation directory of MG and Vanilla Glest, or the shared directory of GAE.
7z_addon.7z/techs/magitech/factions/<...>7z_addon.7z/tilesets/volcanic/<...>7z_addon.7z/techs/military/factions/<...>
/tilesets/evergreen/<...>
/data/core/menu/<...>
/maps/<...>
The archives name can be anything, and doesn't impact it at all, though it's best to give it a unique name related to what the addon actually is. In order for scenarios to be done like this though, you must have both the MG/Glest and GAE method of storing scenarios. In MG, scenarios are stored as simply "scenarios/", whereas in GAE, it's "gae/scenarios/category/". It's possible to have both of these, though, as the engines will just ignore the scenarios that aren't meant for it. This is useful, though, as scenarios are something that have vastly different Lua codes between the two engines, and if a scenario uses MG only code, it can be secluded from GAE.
OK, I will do that when I think it's the right time...I agree. Modders should be trying to make pages for their own mods. If they need an example of how to do so, take a look at the Military page. While no where near to be being done, it is currently the most complete Techtree page, surpassing Magitech (which only has 2 unit pages).
Can we try to put a policy or encourage one where modders (Creators of tilesets, factions, scenarios, maps, and etc) would update their own specific page or create their own page themselves? I mean, this would require just minutes of that person's time. This would be very helpful and it would expand the wiki much faster than just Omega and I... Please? :-X
Yeah, sometimes the uploading tool on wikia doesn't work...after a few refreshes and cache clears, it eventually works.Occasionally, I've seen that in the editing screen, though, I've uploaded hundreds of images and only had problems once or twice like that, which usually worked by closing the popup (for lack of a better word) and retrying. The nastier problems is when it complains that the MIME types don't match (which is expected when converting a JPG to a PNG with alpha, but very difficult to get around, as you must delete the JPG, upload the PNG, and edit all pages where the old image was found. Fortunately only had to do this once. :P
Here's a few helpful pages [for learning to edit the wiki]:
https://docs.megaglest.org/Glest:Policies
https://docs.megaglest.org/Glest:Style_guide
https://www.mediawiki.org/wiki/Help:Contents
https://www.mediawiki.org/wiki/Help:Getting_started
As well, because this is the same software as Wikipedia (Mediawiki), most formatting for it works here as well, and Wikipedia has some very good guides and policies, many of which are used on our wiki, but not directly mentioned.
What a page must have:
- At least one internal link. If a page does not have an internal link, Mediawiki does not consider it a page (and thus, it will not appear when searching, nor on the page counter in the sidebar). Internal links are easy, as Glest (https://docs.megaglest.org/Glest), Tileset (https://docs.megaglest.org/Tileset), Faction (https://docs.megaglest.org/Faction), Mod (https://docs.megaglest.org/Mod), Map (https://docs.megaglest.org/Map), and many more very popular keywords have pages, and if there is no way to add an internal link of at least some kind, you are doing it wrong.
- It must be linked from another page, anywhere. Pages can be imagined as a web, starting with the main page, which links to most of the popular pages, which in turn will link to all the individual pages. If a page does not have anything linking to it, it is considered an Orphaned page, which also annoys Mediawiki. Factions/Techtrees can have pages linked from Mods/List (https://docs.megaglest.org/Mods/List), while maps have Maps/List (https://docs.megaglest.org/Maps/List), and tilesets have Tilesets/List (https://docs.megaglest.org/Tilesets/List). Even scenarios have a page at Scenarios/List (https://docs.megaglest.org/Scenarios/List).
- An introductory paragraph. This is something many older pages lack (and I add it as I find pages that lack it). This is the first paragraph in the article and is NEVER preceded by any type of header. This paragraph (or paragraphs) should summarize what the article is about, or the point of the page. Please do not start pages with a header. Even if the page would seem obvious by the title what its about, always start with an introductory paragraph. It doesn't have to be long. It can be one sentence, but it's gotta be there.
What a page should have:
These are not necessary when creating a page, especially if the page is a stub or there is insufficient data to expand the page, but you should try to get these anyway.
- If the page is a faction, map, tileset, techtree, or unit, it should have the associated infobox at the very top of the page. This summarizes the page, and, like most templates, you will have to use code display to insert them, so you can't use the WYSIWYG editor (I strongly recommend that if you are experienced enough, to set the code version as the default by disabling the WYSIWYG editor in your preferences). They are all named accordingly, so the infobox for factions is found at Template:Faction (https://docs.megaglest.org/Template:Faction). Likewise, maps is Template:Map (https://docs.megaglest.org/Template:Map), etc. The instructions for using these templates can be found on the associated page, along with examples. Even more examples can be found by looking at pages that are using the template (every template is used in at least one page). Please avoid making new templates for any of these categories (for example, I noticed GIS made a unit template, which, ironically, has not been used on any pages). Sure your unit might have more features, but those can be discussed in the actual article. The infoboxes are meant to summarize the faction/unit/whatever in a standard (meaning the same across all like pages) way.
- Avoid using external links in the body of the article unless necessary. Try and group the external links at the bottom of the article, under a new level 2 header "External Links". Whenever possible, link to an internal page. So if you mention GAE in your article, do not link to the sourceforge page of the GAE project, but link to the actual GAE page (https://docs.megaglest.org/GAE).
- Relatedly, try and have a "See Also" section at the bottom of the article (above external links) that links to associated pages (even if loosely). This gives the reader more pages to read when they finish reading one page, and is an easy place to add internal links (for the minimum one internal link rule previously mentioned). Even if the link was mentioned multiple times in the article already, post it again, because people tend to read other pages after they finish reading the current one, rather than while in the middle of it.
- The Glest Wiki is known as the "Glest Wiki". Wikia is just the host, who modifies the MediaWiki (note the absence of the trailing "a") software on which the Glest Wiki runs on. The MediaWiki software is the same software used to run Wikipedia, and thus the origins of the word Wiki (I could go into a long dialogue on what Wiki means, but just to sum it up, it means "fast"). This might sound a bit of a nitpick, but no more so than those folks at Lua (http://www.lua.org/about.html#name).
When updating the Malevolent Rising mod page I stumbled across the 3DS Max page and noticed it was kinda small so I decided to buff it up and include MD5 info as the bridge between Max and Blender or other applications such as Lightwave as md5 can store, textures, triangle meshes, skeletons and skeletal animation. I then decided to make a whole page about the MD5 format, stating it is not currently supported by any version of Glest but that it is useful for moving animated models into Blender for G3D exporting.Thanks for your edits :). Please try and keep the external links and internal links separate though. The "See Also" links should only link to other wiki pages, while the following external links can go to the other sites.
https://docs.megaglest.org/3DSMax_Modelling (https://docs.megaglest.org/3DSMax_Modelling)
https://docs.megaglest.org/MD5 (https://docs.megaglest.org/MD5)
[URL=http://img801.imageshack.us/i/ss232.png/][IMG]http://img801.imageshack.us/img801/7764/ss232.png[/img][/URL]http://www.glest.org/files/contrib/tilesets/http://www.glest.org/files/contrib/tilesets/Why? Well, all those tilesets are just retextured, and not even well retextured at that. I do believe they were created before the G3D exporter was even made public. As for jglest, it is incomplete and abandoned.[IMG]http://img23.imageshack.us/img23/9959/samplehowlongago.jpg[/img]I also still think all units should have individual pages on the wiki (as per Tech, Magic, Military, etc) listed on their faction pages instead of having a large table. Tables have disadvantages in loading, as well, we strive to keep pages as small as possible. Besides, tables have issues with the extremely small size that wiki gives us for editing.Yes, I still think this as well. But I also think tables are OK...for me, the wiki is there to find info...so that's why I think tables with description and a screenshot.
Another thing: for the mod list page, I feel its best to not include information that isn't currently true...so what I mean is no stats for upcoming techtrees, tilesets, maps, etc...or else later on it'll be messy and etc.I think the only one that holds future information is Mrising? Go ahead and remove the future based content. Later, once that part of the mod is complete, we can add it back in (only a few words anyway).
Right...But can't we just change the official format of the dates to be by month date, year? I always found this annoying...Nope. The international date format is Day Month Year, so it should always be output as so, and without any commas. So "March 12 2011" is wrong, as is "March 12, 2011", etc. The correct way to do it is "12 March 2011". Why? Because the wiki, and Glest itself, is an international project, and at the moment, the americans, the majority of the users who would use "Month Day Year" are outnumbered by the other countries. ;)
I tried updating it recently, but I had some problems so I couldn't update it...I'll try again later.
Well, for me, I couldn't edit/I couldn't publish or preview...Then I cleared my cache, it was fine for one preview; then I couldn't press Publish or Preview. Hopefully it'll work for me now. Perhaps we should check the Wikia Blog, I guess. :-XI tried updating it recently, but I had some problems so I couldn't update it...I'll try again later.is it because you cant edit nor can you sign into facebook? yeah, it's doing that for me too....
[URL=http://img218.imageshack.us/i/ss238.png/][IMG]http://img218.imageshack.us/img218/6279/ss238.png[/img][/URL]
[URL=https://docs.megaglest.org/User:Hofmic][IMG]http://img806.imageshack.us/img806/6480/prooo.png[/img][/URL](And if you don't have the time to create pages for every single unit, create tables...at least.) :)I'm gonna be blunt, sooner or later, you're going to have to make time. Making a mod is a big commitment, and it doesn't take too long to at least spur out a quick fill in the blanks of a unit template coupled with a description.
{{Unit
|Unit Name = Worker
|Image = Worker.png
|Health = 600
|Resources = 75 gold, 1 food
|Armor = 0 (leather)
|Faction = [[Tech]]
}}
The worker is the most important unit in the [[tech]] [[faction]] and is capable of constructing buildings and harvesting resources.
There, done. That's the simplest form. Sure, my examples for Military are more advanced and explain everything it can build, usage, production, etc, but that's all optional. At the core minimum, just slap on the unit template (https://docs.megaglest.org/Template:Unit) and a one sentence description (be sure that there's at least one internal link on every page!). Yes, I wrote that real time (not copied or pasted) in less than 5 minutes, no real effort put into it. You can too. All fields in the unit template are also optional, so if a unit doesn't use energy, you can exclude that attribute, just as I did with the worker above. Of course, you'll have to use code view.
But will they really do that? Don't be greedy... :angel:I can only hope. Hey, can't blame a guy for trying! :angel:
hm this?Done (https://docs.megaglest.org/XML/Unit#max-unit-count)
<max-unit-count value="#"/> <!-- Maximum number of these kind of units (not mandatory) -->
Perhaps we could have options to filter XML Definitions for MegaGlest only, Vanilla Glest only, and GAE only?There's already enough Javascript overhead, though it would be possible.
I have a wiki at my own website so I'll consider documenting the MG features there for now, at least it will be safe.Which also has 2 pages, neither about Glest at all, and will never be expanded to match the over 200 page repository of the Glest wiki. One single unified source will match one single unified audience better. Also, there will be a wiki link on the menu bar on the forums, which links to the Glest wiki, which happens to conveniently explain all the engines.
I really don't like Introductions like these:So change it. No page can be perfect if it's only written by a single author. You don't need permission to make a change, just jump in and improve it any way you can, just like how our friend 188.108.12.131 (probably Tomreyn) improved the explanation on how loading screen images work on MegaGlest.
From the introduction for scenarios:
All three engines of Glest, the original one, MegaGlest, and GAE support scenarios, but all to different degrees. MegaGlest and GAE expanded on the original Glest, and thus have all its features and more. GAE has the most support for scripting, so is the most common choice for scenarios.
Great, but the HP cost thing actually doesn't work in MG.Huh? Is it broken?