Elements the Game Forum - Free Online Fantasy Card Game
Other Topics => Elements Portal => Elements Wiki => Topic started by: Xenocidius on May 28, 2012, 02:21:16 pm
-
With a new forum, it's time we had a Wiki that's not under the control of Scaredgirl. One under our new domain.
To this end, our new Wiki can be found here:
>> New Wiki << (http://elementscommunity.org/wiki/)
You'll notice that it's made in MediaWiki (the same software that Wikipedia uses) and not Wordpress (blogging software). This means we have tons of cool features, many of which you can see here (http://elementscommunity.org/wiki/Help:Editing).
One of the really cool changes is that the new Wiki is integrated with the forum. You don't have to create an account or anything like that - just make sure you're logged in on the forum and you'll be logged in on the Wiki, so you can start editing right away!
First thing's first: we want to port all the card articles from the old Wiki to the new. Here's how:
1. Go to the old Wiki (http://elementscommunity.com/wiki/).
2. Go to the page of a card article - for example, Aether Pillar (http://elementscommunity.com/wiki/cards-aether/aether-pillar-aether-tower/).
3. Click edit. Click on HTML (instead of Visual).
4. Copy/paste the HTML into the Wiki Conversion Tool (http://elementscommunity.org/tools/wiki/) and click Convert.
5. Create a new article using the non-upgraded card name as the name
6. Paste the code from the conversion tool.
Simple enough. I've done some Aether cards, so check them out to get an idea of what you should do. Once we've done that, we can work on converting all the other articles (for which the tool will probably not work, so we'll have to do it manually).
We appreciate your help, but please don't help if you don't know what you're doing. I really don't enjoy fixing things when they go wrong (that said, don't stress if something does go wrong). Thanks!
-
One thing i noticed: the card changes from 1.30 haven't been added. We could work on this, once all card articles have been moved. There are also a few formatting error, which we could work on afterwards.
Also, we might need a new standardized formatting to be used for all card articles. Currently, the formatting is inconsistent and looks rather bad.
Again, this could be done after we dumped all the card articles first.
For people without old wiki account, i've uploaded the html codes of all the card articles here (http://www.mediafire.com/?e3k3w0a8diq0e).
EDIT: all card articles added! Now to fix the formatting and clean them up before adding more stuff. And also update the card info which got changed after 1.30.
Also, these cards haven't been added to the wiki:
3rd gen shards (SoFo, SoFr, SoI, SoB, SoW)
Seraph
Psion
EDIT2: also, it would be nice to have the wiki tab added to top.
-
Very nice! It's great to see the wiki, one of my favorite places, finally getting updates with the new metagame. It looks great and I'll be very glad to help write articles for it. without screwing up hopefully
-
This is exciting to see. :D Needs some work but when this new wiki is fully done and with new features added, It will be very appealing. :)
-
I'm having trouble accessing the new Wiki; my forum account apparently doesn't give access to it. I've logged out of the forums and back in again, but to no avail. The login page on the Wiki isn't working either.
-
I'm having trouble accessing the new Wiki; my forum account apparently doesn't give access to it. I've logged out of the forums and back in again, but to no avail. The login page on the Wiki isn't working either.
Same here. It requests me to log in with no method of creating or linking a usable account.
-
It does say error now. Strange, it was working for me a while ago.
-
Sorry about that, I disabled the forum integration so I could do something. It should be working now.
We're making excellent progress. Thanks for your work, everyone!
-
Anything I can do to help? It seems all cards have been transfered now, so I'm wondering what else needs done.
-
Anything I can do to help? It seems all cards have been transfered now, so I'm wondering what else needs done.
Probably cards that haven't been done and/or expanding the articles and updating them with new cards and metagame.
-
Anything I can do to help? It seems all cards have been transfered now, so I'm wondering what else needs done.
3 things.
1. Clean up the formatting of the cards. Refer to Quantum Pillar article for example.
2. Add 1.30 and 1.31 changes. FFQ, Pharaoh, and many nymphs.
3. Put pillars, pends, marks, and such in their own categories.
-
Anything I can do to help? It seems all cards have been transfered now, so I'm wondering what else needs done.
3 things.
1. Clean up the formatting of the cards. Refer to Quantum Pillar article for example.
2. Add 1.30 and 1.31 changes. FFQ, Pharaoh, and many nymphs.
3. Put pillars, pends, marks, and such in their own categories.
Ok, I'll get on to it soon!
-
Another thing we need to do is set up redirects on every upgraded page name. For example, Quantum Tower should redirect to Quantum Pillar, Pest to Devourer, etc. This can be done by going to the page with the name of the upgraded card, then editing it to this text:
#REDIRECT [[non-upgraded page name]]
This should also be done for things like Schrodinger's cat -> Schrödinger's cat, Maxwells Demon -> Maxwell's Demon. In other words, redirects should be set up to any page with punctuation or unconventional letters.
-
The new wiki is great. I mean, that's a REAL wiki. :D
Is that #CardSection some hacked-in parser function? What about using templates for the same purpose? And maybe every card could have a data page like in the old-old wiki so you wouldn't need duplicate data at multiple pages. If you allow me I will do some experimenting as I will have enough time. ;D
-
For card pages, would it be acceptable to have auxiliary (wrong word choice) categories? For example, having a category for Shards, one for Creature Control, etc? Or possible individual pages for these? That way if someone asks for a list of all the, say, CC in the game, they can be directed there?
-
The new wiki is great. I mean, that's a REAL wiki. :D
Is that #CardSection some hacked-in parser function? What about using templates for the same purpose? And maybe every card could have a data page like in the old-old wiki so you wouldn't need duplicate data at multiple pages. If you allow me I will do some experimenting as I will have enough time. ;D
Yep, it's a hacked-in parser function. I didn't use templates because it needed to do some processing - for example, automatic card image generation, automatic filling-in-the-blanks and automatic categorizing.
So you mean that every card would have a template which stores its #CardSection entry? I like that idea, but I wanted to keep things simple to start off with. If you have enough time to help us do that once we've gotten everything ready, that would be awesome.
For card pages, would it be acceptable to have auxiliary (wrong word choice) categories? For example, having a category for Shards, one for Creature Control, etc? Or possible individual pages for these? That way if someone asks for a list of all the, say, CC in the game, they can be directed there?
Again, we'll wait until we've gotten everything ready, but this a good idea.
-
Small question: is there a way to embed links within images? For example, if I click on the 'Eternity' card image on any main page or subpage, is there a way to redirect that clicking of the image to the actual card image itself? I feel kind of slow with this...
-
Assuming you're using the card tag to post images, you can simply use the link parameter, as in:
<card link="http://elementscommunity.org/images/Cards/Eternity.png">Eternity</card>
Alternatively, if it is a non-card image, you can follow the directions here (http://elementscommunity.org/wiki/Help:Editing#Other_Images).
I'm not sure why you'd want to link directly to the image when you click on that same image though. Why not just let everyone right click -> Open Image instead?
-
Assuming you're using the card tag to post images, you can simply use the link parameter, as in:
<card link="http://elementscommunity.org/images/Cards/Eternity.png">Eternity</card>
Alternatively, if it is a non-card image, you can follow the directions here (http://elementscommunity.org/wiki/Help:Editing#Other_Images).
I'm not sure why you'd want to link directly to the image when you click on that same image though. Why not just let everyone right click -> Open Image instead?
Sorry, I meant to say that if I click on say, an image of 'Flooding' in a completely different card article, it would redirect me to the Flooding article instead, but I figured how to do it now looking at the 'Help' page. That being said, thanks, and it totally works now. :)
-
Can the link to the wiki in the main page (http://elementscommunity.org/)be fixed?
-
Can the link to the wiki in the main page (http://elementscommunity.org/) be fixed?
Looks fixed to me.
That being said, all :time, :darkness, & :aether articles from both BloodShadow's period to mine have completely updated articles (in terms of format, at least). Everything should look spiffy for those card sections, and I've also fixed the links here (http://elementscommunity.org/forum/index.php/topic,16848.0.html) so that they'll redirect to the new wiki. :)
-
Can the link to the wiki in the main page (http://elementscommunity.org/) be fixed?
I've also fixed the links here (http://elementscommunity.org/forum/index.php/topic,16848.0.html) so that they'll redirect to the new wiki. :)
Likewise, Elements the Game Wiki (http://elementswiki.co.cc/) will have a Featured Card each week.
This one needs fixing too.
-
I have started to do some templates. Only for experimental purposes for now.
But it seems that parser functions extension (http://www.mediawiki.org/wiki/Extension:ParserFunctions) is not installed or enabled in the wiki so I cannot use even a simple #if or #switch in a template.
So you mean that every card would have a template which stores its #CardSection entry? I like that idea, but I wanted to keep things simple to start off with. If you have enough time to help us do that once we've gotten everything ready, that would be awesome.
Yes, something like that. :) So if you changed the data page of a card, every referer page would be updated with the up-to-date info.
I can do this job without changing any of the existing articles. I will ask for your opinion when I can show something. I think, I will have further questions until then. :)
-
I have started to do some templates. Only for experimental purposes for now.
But it seems that parser functions extension (http://www.mediawiki.org/wiki/Extension:ParserFunctions) is not installed or enabled in the wiki so I cannot use even a simple #if or #switch in a template.
I didn't know about those. Enabled.
So you mean that every card would have a template which stores its #CardSection entry? I like that idea, but I wanted to keep things simple to start off with. If you have enough time to help us do that once we've gotten everything ready, that would be awesome.
Yes, something like that. :) So if you changed the data page of a card, every referer page would be updated with the up-to-date info.
I can do this job without changing any of the existing articles. I will ask for your opinion when I can show something. I think, I will have further questions until then. :)
Sounds good. Good luck. :)
-
Sounds good. Good luck. :)
I think I'm finished with the templates. You can check them on my user page (http://elementscommunity.org/wiki/User:Taffer).
I did not touch current card pages but if you agree we can start to use the templates. Not only the data duplication issue would be solved but the cards would be automatically categorized, too. Everything can be still fine tuned, of course.
I made a howto (http://elementscommunity.org/wiki/Help:How_to_add_a_new_card) about configuring cards. And if you install math extensions (http://www.mediawiki.org/wiki/Extension:Math) as well, it will be just perfectly readable :P.
-
Nice work, Taffer.
-
Nice templates, Taffer. I went and tweaked them a little bit. Here are the new ones.
As you can see, Table Block or Card Page are now default, chosen by comparing the card name to the page name. There are also some other things like the addition of sub-types, removal of unnecessary categories, and some more modes.
Since cards will almost always appear as pairs, that is now default, and there is only one data page for both non-upgraded and upgraded.
Out of curiosity, why did you go for a special card template - that is, using {{Card|Psion}} instead of {{Data/Psion}}, {{Data:Psion}} or even {{Card:Psion}}?
-
Found more than a few tags written as text in a page.
-
Nice templates, Taffer. I went and tweaked them a little bit. Here are the new ones.
As you can see, Table Block or Card Page are now default, chosen by comparing the card name to the page name. There are also some other things like the addition of sub-types, removal of unnecessary categories, and some more modes.
Since cards will almost always appear as pairs, that is now default, and there is only one data page for both non-upgraded and upgraded.
Nice refactoring :)
Combining common and upgraded data in Data page is a good idea - it just didn't come into my mind.
Out of curiosity, why did you go for a special card template - that is, using {{Card|Psion}} instead of {{Data/Psion}}, {{Data:Psion}} or even {{Card:Psion}}?
It came so intuitively... If you need to refer a card isn't that obvious to use a Card template? :P Like your <card></card> tags, but if I cannot access wiki engine I can only create templates. Isn't that natural? :) Btw. if something can be solved by templates I think that's the best choice because everyone can add value to it. But in case of a parser function you are the only one who can improve it, which is not so wiki-like. I think custom parsers should be fallbacks for problems cannot be solved other way.
Since I see that in this wiki the convention is to display cards in pairs not just on the page of an element but also in main card articles I created the Card Pair template. I admit using it as {{Card Pair|basic card|upgraded card}} is a redundant usage so it should be just {{Card Pair|Psion}}, for example, but I see you solved this issue.
I intuitively thought that single card is the "unit" and it can be possible that you want to display only a single card without its pair, usually in "Image Only" mode. What do you think is easier to use/comprehend: {{Card|Supernova|Image Only}} or {{Card|Nova|Image Only|Upgraded Only}}?
-
Out of curiosity, why did you go for a special card template - that is, using {{Card|Psion}} instead of {{Data/Psion}}, {{Data:Psion}} or even {{Card:Psion}}?
It came so intuitively... If you need to refer a card isn't that obvious to use a Card template? :P Like your <card></card> tags, but if I cannot access wiki engine I can only create templates. Isn't that natural? :) Btw. if something can be solved by templates I think that's the best choice because everyone can add value to it. But in case of a parser function you are the only one who can improve it, which is not so wiki-like. I think custom parsers should be fallbacks for problems cannot be solved other way.
Seeing as all the card template does is refer to the data page as a template, it seems like an unnecessary step compared to simply referencing the data page directly. Is there any good reason to have that intermediate card template?
Btw. if something can be solved by templates I think that's the best choice because everyone can add value to it. But in case of a parser function you are the only one who can improve it, which is not so wiki-like. I think custom parsers should be fallbacks for problems cannot be solved other way.
I agree, though we might end up protecting those templates anyway, as they make it way too easy for a vandal to globally, albeit temporarily, wreck the Wiki. Also, parser functions and custom tags are often more efficient than templates.
Since I see that in this wiki the convention is to display cards in pairs not just on the page of an element but also in main card articles I created the Card Pair template. I admit using it as {{Card Pair|basic card|upgraded card}} is a redundant usage so it should be just {{Card Pair|Psion}}, for example, but I see you solved this issue.
I intuitively thought that single card is the "unit" and it can be possible that you want to display only a single card without its pair, usually in "Image Only" mode. What do you think is easier to use/comprehend: {{Card|Supernova|Image Only}} or {{Card|Nova|Image Only|Upgraded Only}}?
True, though I actually removed Image Only mode. I prefer the <card> tag for image display purposes, as it's more extendible - for example, letting it float to the left or right, which is a must in featured articles. Adding this functionality to the card template would be inconsistent with its purpose and parameters - then you'll end up having the template split into image handling and table handling, which seems silly.
-
Seeing as all the card template does is refer to the data page as a template, it seems like an unnecessary step compared to simply referencing the data page directly. Is there any good reason to have that intermediate card template?
This is simple data-view distinction. Data is responsible for storing data while {{Card}} is responsible for displaying cards in various modes. Okay, technically Data page (in my implementation) also displays the card, by default in data page mode (http://elementscommunity.org/wiki/Data/Quantum_Pillar).
Another thing: I prefer if Data pages receive up to one input parameter. If a new card is introduced this is the only somewhat difficult part that a wiki editor needs to create. If there are mandatory {{{2|}}} {{{3|}}} etc. parameters to handle them in various modes it makes difficult to create these pages.
I agree, though we might end up protecting those templates anyway, as they make it way too easy for a vandal to globally, albeit temporarily, wreck the Wiki.
A wiki is always can be target of vandalism. My experiences that vandals usually delete/modify the main page or insert spams with irrelevant links, or make tiny changes like changing "Skill" of a card to some garbage. These don't affect templates. But you can protect sensitive pages so only registered or power users can modify them.
I actually removed Image Only mode. I prefer the <card> tag for image display purposes, as it's more extendible - for example, letting it float to the left or right, which is a must in featured articles. Adding this functionality to the card template would be inconsistent with its purpose and parameters
All is matter of approach. I made Card template for displaying single cards and not card pairs. With this approach it makes sense to use it even to display simple card images because even Image Only mode uses some information of the data page (link target, display name, image filename). Secondly, I prefer isolating responsibility and building complex thing of simple "bricks". So Card Pair uses Card to display pair of cards and both templates have simple source and clean purpose.
Your approach is different, which I don't take worse or better, it's just different. If we say that Card template is responsible for displaying cards in pairs, then you are right, displaying simple images would be unnecessarily difficult by this template. But in this case some logic are duplicated: <card> needs also to determine target link, display name and card image filename from some source.
And you are right, I would not add floating and such to the template. You cannot prepare all of the possible needs so I would use <div> instead. Or specific templates. :P
Check this (http://elementsthegame.wikia.com/wiki/Template:Deck_Import_Code), for example (btw, I wish to migrate this template, too). How would you prepare for these image placements in <card>?
-
Seeing as all the card template does is refer to the data page as a template, it seems like an unnecessary step compared to simply referencing the data page directly. Is there any good reason to have that intermediate card template?
This is simple data-view distinction. Data is responsible for storing data while {{Card}} is responsible for displaying cards in various modes. Okay, technically Data page (in my implementation) also displays the card, by default in data page mode (http://elementscommunity.org/wiki/Data/Quantum_Pillar).
Another thing: I prefer if Data pages receive up to one input parameter. If a new card is introduced this is the only somewhat difficult part that a wiki editor needs to create. If there are mandatory {{{2|}}} {{{3|}}} etc. parameters to handle them in various modes it makes difficult to create these pages.
True. Do you think that the upgrade parameter should simply be removed then? I'd suggest using another template to include the parameters, but I think we may have reached our technical limit. :P
I agree, though we might end up protecting those templates anyway, as they make it way too easy for a vandal to globally, albeit temporarily, wreck the Wiki.
A wiki is always can be target of vandalism. My experiences that vandals usually delete/modify the main page or insert spams with irrelevant links, or make tiny changes like changing "Skill" of a card to some garbage. These don't affect templates. But you can protect sensitive pages so only registered or power users can modify them.
Currently non-registered users can't edit at all, actually, and I'm not sure I want to change that. Deleting isn't a concern either, as only mods can delete pages.
I actually removed Image Only mode. I prefer the <card> tag for image display purposes, as it's more extendible - for example, letting it float to the left or right, which is a must in featured articles. Adding this functionality to the card template would be inconsistent with its purpose and parameters
All is matter of approach. I made Card template for displaying single cards and not card pairs. With this approach it makes sense to use it even to display simple card images because even Image Only mode uses some information of the data page (link target, display name, image filename). Secondly, I prefer isolating responsibility and building complex thing of simple "bricks". So Card Pair uses Card to display pair of cards and both templates have simple source and clean purpose.
Your approach is different, which I don't take worse or better, it's just different. If we say that Card template is responsible for displaying cards in pairs, then you are right, displaying simple images would be unnecessarily difficult by this template. But in this case some logic are duplicated: <card> needs also to determine target link, display name and card image filename from some source.
True, and with your approach it does make sense to let it display images. The <card> tag, however, can so far determine target link, display name and card image filename with 100% accuracy and minimal effort.
And you are right, I would not add floating and such to the template. You cannot prepare all of the possible needs so I would use <div> instead. Or specific templates. :P
Check this (http://elementsthegame.wikia.com/wiki/Template:Deck_Import_Code), for example (btw, I wish to migrate this template, too). How would you prepare for these image placements in <card>?
That's a clever template, but unnecessary with the <deck> tag. The nice thing about tags is that new parameters can be added indiscriminately, so x and y attributes could be added if need be.
Just an additional note: I like template names to be as short as possible if they're going to be used in a lot of pages. That's one of the reasons why I don't like Card Pair.
-
Do you think that the upgrade parameter should simply be removed then?
If we use a common Data page for basic and upgraded cards I'm not sure we can avoid it. If we use separated Data pages (eg. Data/Nova and Data/Supernova) we can avoid the extra parameter. I will accept your decision.
I like template names to be as short as possible if they're going to be used in a lot of pages. That's one of the reasons why I don't like Card Pair.
Hmm... "Cards"? :D
Firstly I created it as CardPair (without space) but then I renamed it due to wiki conventions.
That's a clever template, but unnecessary with the <deck> tag.
I like <deck> tag and I don't want to ignore it. It's perfect for displaying the deck as a single image. I would just create an optional "Interactive Deck" template because you can click each card of the deck as they work as links. Hmm, isn't the name "Interactive Deck" too long? :P
-
Do you think that the upgrade parameter should simply be removed then?
If we use a common Data page for basic and upgraded cards I'm not sure we can avoid it. If we use separated Data pages (eg. Data/Nova and Data/Supernova) we can avoid the extra parameter. I will accept your decision.
Well, you mentioned extra difficulty in creating the pages as a reason against extra parameters, but I think creating twice the amount of pages is more work than one extra parameter that is part of a copy/pasted template anyway. So, I'd say we keep them and go with the single card option.
That's a clever template, but unnecessary with the <deck> tag.
I like <deck> tag and I don't want to ignore it. It's perfect for displaying the deck as a single image. I would just create an optional "Interactive Deck" template because you can click each card of the deck as they work as links. Hmm, isn't the name "Interactive Deck" too long? :P
One thing you could do is try to create a template using the existing deck tag as a base and then adding carefully spaced hyperlinks. It would be tricky, but ever so pretty.
-
Do you think that the upgrade parameter should simply be removed then?
If we use a common Data page for basic and upgraded cards I'm not sure we can avoid it. If we use separated Data pages (eg. Data/Nova and Data/Supernova) we can avoid the extra parameter. I will accept your decision.
Ok, I made some further experiments (http://elementscommunity.org/wiki/User:Taffer) to make decision easier. I created a combined data page for Toadfish/Puffer Fish and made an alternative {{Card Display}} template (http://elementscommunity.org/wiki/User:Taffer/Template:Card_Display) to use such Data pages. Please note that {{Card}}, {{Card Pair}} and {{Card Display Table Block}} templates handle both variations; I needed only change the {{Card Display}} template. (I did not change the Data Page display template so it now displays the basic card data)
Pros:
- One common data page for both unupped and upped cards
Cons:
- 2 input parameters in Data page
- New {{Card Display}} is more difficult than the original one. When passing parameters to table block view many conditions has to be processed (slower)
- Though there is one actual Data page, upped Data page has to be created as well as a redirection
-
Oh I see you already answered. Okay then, let's do it. :D
But now I go to sleep ;D
-
Some suggestions because I don't feel I know enough about the game/wiki stuff to actually make these pages myself--at least not in any kind of efficient manner.
Links to elements on the card page seems redundant and not especially useful when you end up on the next page expecting something more like the elements pages and getting basically the same thing as the (uncategorized) omnilist at the bottom of the card page. If possible, make another section for cards listed by element (instead of alphabetically) with proper headers (instead of letters, obviously).
Overview pages instead of a list of links for creature, spell and permanent cards: like element pages. Leave the creature, spell and permanent links on the card page. --or the below ideas, which are a bigger undertaking (but more awesome).
Additional info tags to cards (hidden or perhaps replacing/adding onto "quick facts" on card page) that allow for a nice, sortable table to be made on the creatures/spells/permanents pages. Because of all the different tags that can be added to various types of cards, the tables would probably need to be broken down into multiple tables in some way.
Rough idea example: Permanents' sub pages Pendulums, Pillars, Shields, and Weapons each lead to a page with a sortable table. For example, the shields page would be able to sort things like element, name, damage reduction #, reflective yes/no, miss chance, stealable yes/no, destroyable yes/no, special yes/no.
Not sure how to handle upgraded cards--maybe different pages for upgraded creatures/spells/perms, linked on card page. Might not be too bad combined though.
Perhaps additional, specialized sortable table pages for cards that produce quanta (element, name, element of quanta produced, how many quanta, cost), poison, heal or whatever else might be useful. This might be too redundant if multiple tables are on the creature page for these things, but it would be nice to have all cards that do similar things in one place.
I think the sortable tables would be especially awesome to see an overview of everything you care about quickly. As a beginner, I know I would find it helpful for "finding that one card that does that thing that I need" and building decks. I'm not sure how much it would be useful to other players, but it seems like it'd be useful at least until they're able to remember all the cards and all their abilities.
Sorry about the long read, but I wanted to be descriptive.
Oh yeah: About the interactive deck incorporated with the deck image maker... what about bypassing the image maker and making it so the deck code produces a special thingie for the wiki? The (wiki-formatted?) codes would change into corresponding, linked cards--perhaps with a table for card count/cost/etc and with the un-changed code for copying. Might want a little tool to add a colon before each 3 character code or something for ease but I dunno if that's necessary with some kind of template. Seems easier than the fancy sliding, but I don't really know. D:
-
Then I think I start with doing Others and maybe one more element just to see if it will be okay.
-
Hang on there. I thought we agreed to use my template, so why are you using yours?
-
Hang on there. I thought we agreed to use my template, so why are you using yours?
Oh sorry, your last answer was this:
Well, you mentioned extra difficulty in creating the pages as a reason against extra parameters, but I think creating twice the amount of pages is more work than one extra parameter that is part of a copy/pasted template anyway. So, I'd say we keep them and go with the single card option.
I took it as a decision about using combined Data pages instead of separated ones, and I did so.
Sorry-sorry a thousand times if I did something wrong. :'( As I said I made only Others just to see whether it will be okay. So this is still not a final state and feel free to change the format or anything. Rest of the elements pages will be done as you decide.
As I see the main difference between our Data content is mainly just the parameter names (eg Life vs HP). And that I have split skills into more parameters (so Skill Name or Skill Element can work as a link). But this is still not a final state! Final word is yours about that. :-X
-
Sorry if I wasn't clear. I meant we keep the extra parameters and go with the single card option - i.e., my template. Sorry for the confusion.
So unless you have more suggestions for my template, I guess we can start using that. Regarding yours, I'm not a fan of splitting the description into active skill, passive skill and effect due to inconsistency, difficulty in determining which part goes where, and most of those that were chosen on the old Wiki are technically inaccurate from a coding point of view.
-
Since you moved Card template now Others has a lot of red links. I tried to insert a temporary redirection to the moved template until you finish your version but it didn't work (redirection disabled?).
Last version used a common Data page as you requested. Maybe you could have just modify the template until it meets your taste.
Edit: Sorry but until you finish I restored Card template because Others page and cards of Others were broken for a day or so. Feel free to modify it or I don't even mind if you delete it again but before that prepare Others to work with the new version.
-
Featured Card articles have now been updated - as in, all the previously featured cards should have fixed links and formats. The Featured card project has also been restarted. :D
Also, loving the new 'Other' section; the format there where you can click on the card image to link to the page directly should totally be used on the other Elements. :)
-
Awesome work, Kuro, and +rep.
Yep, that's one of the things we have to work on next - updating all the other element pages and card articles to use the new template.
-
Do you think the new templates are ready to use? I saw that you also modified Others only.
If testing phase still lasts I have some "review comments":
- If upped card has different name, it refers to a page with the upped name so there must be a redirection page to the basic card.
- If a card exists only in-game (eg. Malignant Cell, Ash) there should not be a sell price.
- I think if upgraded version of a card is not available (Malignant Cell, Shard Golem, Holy Cow) only the basic card should be displayed on card list pages and in the card article header. As an interesting fact, the card article may remark that an upgraded version technically exists and an image can be placed somewhere inside the article.
First two points were implemented in my original templates. I would just fix them if you allowed me, or do it yourself if you wish. :)
Third point is just a suggestion - I think that makes sense.
Btw sorry for my long silence, I was on holiday, etc. I thought I wait until you finish but meantime I noticed your post on my talk page. Actually there was a link on the main page but has been commented out recently due to the uncertain status of the new wiki. If you say it would help to the new wiki to place a link I can re-enable it.
-
Can we has false god articles?
-
Can we has false god articles?
Some already exist. (http://elementscommunity.org/wiki/Category:False_Gods)
-
Do you think the new templates are ready to use? I saw that you also modified Others only.
If testing phase still lasts I have some "review comments":
- If upped card has different name, it refers to a page with the upped name so there must be a redirection page to the basic card.
- If a card exists only in-game (eg. Malignant Cell, Ash) there should not be a sell price.
- I think if upgraded version of a card is not available (Malignant Cell, Shard Golem, Holy Cow) only the basic card should be displayed on card list pages and in the card article header. As an interesting fact, the card article may remark that an upgraded version technically exists and an image can be placed somewhere inside the article.
First two points were implemented in my original templates. I would just fix them if you allowed me, or do it yourself if you wish. :)
Third point is just a suggestion - I think that makes sense.
Btw sorry for my long silence, I was on holiday, etc. I thought I wait until you finish but meantime I noticed your post on my talk page. Actually there was a link on the main page but has been commented out recently due to the uncertain status of the new wiki. If you say it would help to the new wiki to place a link I can re-enable it.
To address your points:
- I already set up those redirections a while ago.
- Agreed.
- For consistency, completeness and so that the cards don't stand out awkwardly, I prefer having the upgraded version there. The Wiki page itself would naturally mention that the upgraded version cannot be obtained.
The new Wiki is definitely going ahead, so the link would be great.
For everyone, here's our current to-do list off the top of my head:
- Update element pages and card articles to use the new template.
- Add all False God articles.*
- Add some significant, well-known decks or deck archetypes (I've added Instosis so far). Note that this Wiki will not be a place for people to share decks at whim; that's what the forum is for.
*With the False God articles, you'll be getting information from the old Wiki, so when you're done edit the False God page on the old Wiki and add this line at the top:
<strong><a href="http://elementscommunity.org/wiki/{{False God name}}"><span style="color:red; font-size: 14pt;">>> Updated content available on the new Wiki <<</span></a></strong><div style="display: none;">Replace {{False God name}} with the False God name, obviously. This will hide the page's content and redirect users to the new Wiki page.
Let's get to it!
-
I'm also updating the false god articles to reflect the change of FG decks used. I don't know much about poison stalls such as PD SoSac, so can someone please fill that in?
(I think each article should have some strategies for 4 types: rainbow control (Flay 'em, CCYB mod), OTK (Limitless, Instosis), RoL/Hope, and Poison stall (SPlat, PD SoSac))
-
(I think each article should have some strategies for 4 types: rainbow control (Flay 'em, CCYB mod), OTK (Limitless, Instosis), RoL/Hope, and Poison stall (SPlat, PD SoSac))
This. As long as the differences between decks in each category are noted.
Transferred the Arena article over - I updated it to reflect ring and HP loss changes, simplified the list code, and elaborated on some things. Hope you don't mind Jenkar.
-
- Update element pages and card articles to use the new template.
I started with :earth cards, please check the result. If you like it I may do the rest, too.
Furthermore, I fixed some price level calculations and rarity-auto detection, and I removed the necessity of <noinclude> tags in data pages.
- For consistency, completeness and so that the cards don't stand out awkwardly, I prefer having the upgraded version there. The Wiki page itself would naturally mention that the upgraded version cannot be obtained.
Hmm... Now I did as you prefer that but I think displayed info of upgraded card is more awkward this way: both rarity and buy/sell info is a nonsense. I could set price level 0 also for the upped card to display "In-game card only" instead of a sell price; however, this is actually an "Out-of-game card". ::)
I inserted a comment in the row of Shard Golem in Earth page containing the basic-only version. It doesn't seem awkward to me - you did a good job with "No Upgrade" display mode - where else could we use that if not here?? :P So I still prefer hiding the upgraded version in the list and mentioning it only in the article as an interesting fact.
-
- Update element pages and card articles to use the new template.
I started with :earth cards, please check the result. If you like it I may do the rest, too.
Furthermore, I fixed some price level calculations and rarity-auto detection, and I removed the necessity of <noinclude> tags in data pages.
Looks good from what I can see.
- For consistency, completeness and so that the cards don't stand out awkwardly, I prefer having the upgraded version there. The Wiki page itself would naturally mention that the upgraded version cannot be obtained.
Hmm... Now I did as you prefer that but I think displayed info of upgraded card is more awkward this way: both rarity and buy/sell info is a nonsense. I could set price level 0 also for the upped card to display "In-game card only" instead of a sell price; however, this is actually an "Out-of-game card". ::)
I set price level to -1, which displays: 'Only appears in bugs'.
I inserted a comment in the row of Shard Golem in Earth page containing the basic-only version. It doesn't seem awkward to me - you did a good job with "No Upgrade" display mode - where else could we use that if not here?? :P So I still prefer hiding the upgraded version in the list and mentioning it only in the article as an interesting fact.
And where else could be use that lovely upgraded Shard Golem image if not there? :P
-
Skills are rendered as links by the new template; however, there are skills like "earth" or "unstable gas" that have conflicting name with articles. To resolve this I resurrected "Active skill" and "Passive Skill" pages and the template now links the skills on these pages.
Meanwhile I realized that all of the skill pages are already exist. Firstly I didn't noticed this because Xeno's resolve for conflicts were red links on Others page (dagger, hammer). Most of these pages are single-sentence chunk articles so skills seem really scattered to me this way.
What should be strategy now? Is it okay to have a common summarizing page for skills where you can see them together? I created a Wikipedia-like {{Main|main article}} template to reference the more detailed article where it is not a chunk (e.g. airborne skill is a well-written one).
Or should I undo the template to reference the separated single-sentence articles?
-
We use the same solution to this as Wikipedia does: naming the skill article "Earth (ability)". It was resolved in the data pages by adding * to the end of the skill name (i.e., Earth*). I didn't realize that it wasn't working.
If one wants to see skills together they can still go to one of the category pages. I'm not sure whether the Active skills/Passive skills pages are a good idea ... though if we were to use them, we'd naturally need to create a bunch of redirects as well.
-
Can we has card code for each card? It seems like it'd be nice.
I also did the SoW article and fixed the short sword | long sword info. Swords have 2 hp!
-
Can we has card code for each card? It seems like it'd be nice.
Here (http://elementsthegame.wikia.com/wiki/Template:Card_Name_By_Code?action=edit)
-
Xeno, what about improving element icons in wiki so they would work as links?
Now that the templates don't have Skill Element parameter I can solve it only for card cost. See here (http://elementscommunity.org/wiki/Light_Nymph) what I'm talking about: The icon in cost now works as a link and has a mouse hover box, while in description there are just simple images (because those images are rendered by ":light" function).
-
Xeno, what about improving element icons in wiki so they would work as links?
Now that the templates don't have Skill Element parameter I can solve it only for card cost. See here (http://elementscommunity.org/wiki/Light_Nymph) what I'm talking about: The icon in cost now works as a link and has a mouse hover box, while in description there are just simple images (because those images are rendered by ":light" function).
It seems kind of pointless, seeing as there's an element link right above the icon anyway. Nice for future reference though.
-
It seems kind of pointless, seeing as there's an element link right above the icon anyway. Nice for future reference though.
Errr... ::) Ok, bad example. This one (http://elementscommunity.org/wiki/Firefly_Queen) is a better one: card and skill elements are different. So is it pointless to turn :life icon a link here? At least a mouse hover box would be helpful, like here in the forum. A beginner might not recognize all of the icons.
-
Alright I can't figure out how to fix this myself since I apparently can't edit this, so...could someone change the bit where the wiki currently says Adrenaline is a Creature, not a Spell?
-
Alright I can't figure out how to fix this myself since I apparently can't edit this, so...could someone change the bit where the wiki currently says Adrenaline is a Creature, not a Spell?
Done.
-
Alright I can't figure out how to fix this myself since I apparently can't edit this, so...could someone change the bit where the wiki currently says Adrenaline is a Creature, not a Spell?
My fault (damn copy-paste). In card articles you can see the Edit Data link below the card. Hard to believe but it is good for editing data ;)
-
Sorry to post something you may have been already told, but why do we still have the old link of the wiki on the game? News players will be better if they go on the new one! (who seems great, I just discovered it)
-
Sorry to post something you may have been already told, but why do we still have the old link of the wiki on the game? News players will be better if they go on the new one! (who seems great, I just discovered it)
Because Zanz hasn't changed it yet.
-
I don't know much about poison stalls such as PD SoSac, so can someone please fill that in?
-
I see the old deck templates got moved over from wikia. They're so...bulky compared to what we usually use here, but I do like the idea of having the starter decks on the element pages.
Other than that, I want to go crazy with editing. It's been forever since I've worked on a wiki and there's so much we could do with this - it's still a hatchling.
-
I ... strongly suggest against using that deck template. It's ugly, bulky, inconsistent with the forum, and inelegant compared to our normal deck image builder. The card links are nice, but could be done with the current image builder (if anyone's up for this challenge, go ahead). I made it so that template parameters can be passed into <deck>.
In other news, I do like the little elements strip across the bottom of the element pages.
-
I ... strongly suggest against using that deck template. It's ugly, bulky, inconsistent with the forum, and inelegant compared to our normal deck image builder. The card links are nice, but could be done with the current image builder (if anyone's up for this challenge, go ahead). I made it so that template parameters can be passed into <deck>.
I agree. The bulkiness reminds me of the other other elements wiki, and it takes up way too much space. The current one we have is pretty nice.
-
I ... strongly suggest against using that deck template. It's ugly, bulky, inconsistent with the forum, and inelegant compared to our normal deck image builder. The card links are nice, but could be done with the current image builder (if anyone's up for this challenge, go ahead).
The single image deck is perfect for the forums.
As for the wiki, it depends on the article: I would prefer the interactive deck in reference articles (starter deck in elements pages, false god decks, other AI decks and user-submitted decks). For a beginner, it is impossible to comprehend all of the cards and keep them in one's mind. What a beginner needs is exactly the thing that is offered by the interactive template: to check the function of cards in the deck.
Though, when an article is not about a specific deck (for example, in card articles the possible synergies with other cards), I also prefer single deck images.
I made it so that template parameters can be passed into <deck>.
I'm glad you fixed this bug. Maybe you noticed that originally I made {{Deck}} to support both single image and interactive modes but unfortunately it was impossible to pass any dynamic code to <deck>.
Though I'm not so glad that you "lobotomized the active skills" of my template so quickly :'( Maybe you should have just started a poll first...
-
I'm thinking that instead of clicking on each card, perhaps a dynamic list of each card in the deck could be generated underneath the deck image. For example:
- 6x Shard of Readiness
- 6x Supernova
etc. And all card names would be linked to the article. Thoughts?
-
I'm thinking that instead of clicking on each card, perhaps a dynamic list of each card in the deck could be generated underneath the deck image. For example:
- 6x Shard of Readiness
- 6x Supernova
etc. And all card names would be linked to the article. Thoughts?
Would be very neat. I'd approve.
-
I'm thinking that instead of clicking on each card, perhaps a dynamic list of each card in the deck could be generated underneath the deck image. For example:
- 6x Shard of Readiness
- 6x Supernova
etc. And all card names would be linked to the article. Thoughts?
Not a bad idea but it requires more space and you complained about space wasting (think of a rich rainbow deck and its links).
Please note that the "engine" of the interactive deck is ready to use. You can forget the "bulkiness"; all we need to use the small card images to make it conform with the single image version. Since I made it to use the {{Card}} template, using the small images can be achieved easily by a "Small Image" display mode in {{Card Display}}. Is there a simple mapping from card image file name to small card image file name? If so, the task is 95% finished right now.
-
is the source code what I must put in the conversion tool? Because I don't have Edit ---> HTML
EDIT: Well, I passed the AI3 and AI2 article, putting the deck braces one by one.
-
Featured cards have text on synergies and decks making use of them. What about a section for cards that counter it? Like a reverse synergy that warns what the user has to watch out for, as well as teach readers how to counter certain cards. It's probably a low priority thing, but I'm just going to suggest it here.
-
Article (http://elementscommunity.org/wiki/Overview_of_the_elements). Thought the wiki could use more articles, and felt this was probably an interesting topic.
-
Article (http://elementscommunity.org/wiki/Overview_of_the_elements). Thought the wiki could use more articles, and felt this was probably an interesting topic.
I read it yesterday. It is very interesting thank you. If wiki lore (permanent and creature backgrounds etc.) is allowed to be on the wiki, I would very much like to contribute to it.
-
Article (http://elementscommunity.org/wiki/Overview_of_the_elements). Thought the wiki could use more articles, and felt this was probably an interesting topic.
I read it yesterday. It is very interesting thank you. If wiki lore (permanent and creature backgrounds etc.) is allowed to be on the wiki, I would very much like to contribute to it.
Probably not. It's not canon.
-
Wiki should be non-fanon. Any lore should be in the userspace only.