Hello there, since I'm currently testing for new template maybe it's the right time for ask about CSS.
Previously, this wiki cater for both Monobook and Oasis theme and split the CSS/JS accordingly. But since Monobook has been retired, I have been wondering if we should merge all the Oasis custome into the main one. This wiki is pretty old (started around late 2012) and I'm not sure if everything will work normally if we reorganize the CSS and JS.
I'm so sorry for a late reply, but I was away from Fandom work over most of the weekend. Yes, the CSS should be merged into one, but you should be careful whether it has duplicate elements, or if anything gets overriden by some elements, for example.
I can help with this or even do it myself and you will check after me if it's done as you intended. This is not hard and will not break the wiki, it's just that it needs to be read over afterwards, not just copy & pasted into one place.
Please do. Most of the modifications and imports are done in Common.css so I don't really remember the specifics from Wikia.css or if there any other customization beyond what listed/imported in Common.css.
Preferably, I would like to keep one main basic CSS (outside of template specific imports) that can be reused in case Fandom is going to support additional skins again.
To be sure that everything in Common.css works, I switched off Wikia.css by deleting */ in the section titles (such as /* Global */) and adding /* before the imports, this way CSS placed in Wikia.css doesn't work at the wiki now, but is archived just in case. You can switch off any CSS this way.
If everything is fine, feel free to delete Wikia.css or keep it.
Hmm, the CSS imports are not working at this moment (for example, all pages that use Template:Card Table are not styled) so I'm not sure if the Common <> Wikia CSS switch are correct. Currently turning on the Wikia.css again.
Perhaps you can take a look at it again? Especially why the Common.css is not loaded properly.
Apparently this wiki doesn't have automatic loading for Common.css switched on. Common.css doesn't work if it's not imported to Wikia.css (see the import that's switched on now, the rest is switched off). I requested that and it should be enabled tommorow.
Thanks for the check, thing are slowing down here since the pandemic but it still roughly the same.
As for the forum, I prefer to keep it for the time being since it's rarely used and for historical purpose as well. In the event that it's retired, perhaps I'd like to have all of its contents archived somewhere else (maybe migrated to Discussions or something similar).
When Forums get eventually retired, the contents will be moved to Discussions. This way, you can have them there. However, if we enable them earlier, then the content won't get migrated. So you should wait and let the content migrate when Fandom disables Forums everywhere.
Hello there. There's nothing to worry about the technical stuffs for now, since stuff is basically the same.
That said, we might need some cleanup and compatibility check once the Mediawiki update and/or UCP is live for all wiki. Especially regarding the custom skin & mobile compatibility.
For basic stuffs, is there any list/references about the styles and code guidelines used by Fandom? We have some problem in the past regarding custom style (it conflicted with default style of the same name) so I'd like to use that for references in the future.
We will take care of the transfer to UCP and make sure it will go well when it happens. Us WMs will be notified about the process and you can be sure I'll come have a look here when the mass moving of wikis to UCP happens.
You mean the visual look of the wiki? The MediaWiki pages with CSS? I think the best place to research that and find cool scripts to import or ask people to tell you more would be Dev Wiki. There aren't many resources on Fandom about CSS, but Dev Wiki have some. Also, you can always ask me about anything.
Greetings! I would like to ask a simple question about the new shift mechanic.
The player-shifts vessel conditions asks for a overboost of certain name, like "Fated Shift" Blue Star Princess, Rigel asks for a Overboost with Azumi in its name.
But should I overboost in another card, like 'Destiny Mentor Engage, Polaris' while using Azumi as a player. Would I be able to shift in Rigel? I mean since my overboost should get the player name Azumi for itself.
In your case, you are unable to Shift In to Rigel as the Shift Vessel specifically ask for the card name and not the "Player Name" parameter. Granted, all of the current SFR and above-rarity Shift as of B27 can only be used with the player-specific Z/X Overboost and not the generic ones.
Just want to ask about the card effect the contains "Battle Dress x" or "Angel x" where x is a number like Dingir 2/Waker 2. Is it like you need to have the specific number of tribe in Dynamis or something?
FANDOM has decided to retire the HeaderTabs extension from our network. It has been buggy since its implementation and only three wikis are currently using it. Of those three, your wiki is the only one that has implemented it to some degree, specifically in the Template:HeaderTabs template.
We will be retiring it by end of this month. I would suggest looking into Tabber as a replacement.
Is there any other suitable, more customizable replacement for it other than Tabber extension? Because I originally requested the HeaderTabs as the replacement for Tabber because of its customization.
Also, the usage of wiki header by HeaderTabs means that the "tabbed" contents will be separated into its own section in mobile view, whereas Tabber extension simply put all the contents one after another without any separator to differentiate them. The ability to properly separate the "tabbed" contents in mobile view is very important here.
To answer your main question, yes, Tabber is going to be the backbone of your tabbed solution in the wake of HeaderTabs' retirement.
No MediaWiki extension that delivers a tabbed experience on desktop truly "works" on mobile in a tabbed way. Instead, as you've pointed out, the tabs are displayed vertically, one on top of another. The distinction between HeaderTabs and Tabber, on mobile, is mainly that HT gives you an interstitial "header", and therefore clearer separation between the tabs.
There is, however, a way to retrofit headers onto a Tabber instance, which you can find here. Of course, implementation would mean that we'd have to manipulate every page at Special:WhatLinksHere/Template:HeaderTabs. But there are only about 175 pages affected.
Once we found an arrangement you liked on a few test pages, it wouldn't be terribly difficult to make the move by bot. (And I just happen to have a friendly one. :) )
So, I would suggest that in the next few days you:
pick a few test pages that you know are representative of the lot
manually make changes along the lines suggested at that help page
look on your phone to see what the page looks like after being switched to Tabber
Once you've found a look you like on mobile, call me back in and then we can bot the changes for the other ~170 pages. We'll also take a look at the ways the desktop Tabber buttons compare with the HT ones, and get them more similar.
I do aware of the "hidden" header implementation for Tabber, but as you pointed out, I kind of shy away from it because of the amount of effort to do it. Still, the suggestion to port the view of HeaderTabs to Tabber and apply it via bot is a good alternative.
Since we already have a bot here, I will test and port the tabbed view myself in the following week. Please notify me again once the HeaderTabs extension are removed.
I saw your message over the weekend and figured you were probably okay on your own. Still, I just wanted to drop back by and let you know that if you run into any problems, you should feel free to ask for additional help!
As DaNASCAT said in his initial post, it's due to be retired at the end of the month. That means as early as Thursday and as late as next Tuesday.
Just wanted to thank you for your effort and contribution to the Z/x wiki. I (and many other user as well, i'm sure) really appreciate the time and work you put into translating, maintaining and updating the card pool.
You might want to reconsider some of the cards with the "bounce" effect (e.g. "Secret Plan"), since their effect range is limited. Either reduce and/or replace them altogether with stronger cards. Replacing "Mirage Dagger, Bellatrix" is also an option, since her effect is at odds with the draw-shuffle cards in your deck.
In addition, since most cards with Range ability does have slightly lower Power for their Cost, you might want to only focus on several amount of cards rather than going all out with them. By doing so, you will have more room for high Power Z/X or bounce cards for answer in case you get walled by high Power Z/X.
Like said above, some Boot ability will specifically mention its activation place (i.e. most Start Card requires the card to be in Charge). Usually, it will either say "This ability can only be played ... if this card is in [location]" or written after the [Valid] icon for cards with the new text structure.
If the ability does not mention where it could be activated, or written as "[Valid] Square" using the new text structure, then it can only be activated if the said card is in Square.
Like Aeris Ventaile said in his/her last sentence, if an ability that does not specify where it could be activated, it generally means the effect is to be played when this Z/X is in square. Another way you can see this is, abilities only 'exist' when Z/X are in square, unless otherwise specified (where other zones are mentioned as part of the effect text).
Tips on deck building... To be honest, I don't really have one since most general deck building guides for other TCG (card synergies, color & cost balance, etc.) also works here. Not to mention that it will ultimately depends on what deck you are going to build.
Usually, I'll just look for other cards (usually generic) that fit with my deck main theme, or combos and recipes if I need more ideas to expand my deck.
As for Event, it also depends on your deck build and preferences. Most deck runs 0 to 8 Event, sometimes more. They are mostly used for defensive or utility purpose, although there are some deck that centered around Event or absolutely need it to run.
Hmmm... For starter, try to cut the number of Event. 17 is too much, considering that your deck doesn't really focused on Event.
As for the deck's main theme/goal, looks like you already have a definite goal here (Weapon Master, Armed) so your deck is on the right track. You either need cards that can deal with opposing Z/X easily like or generic cards that support the Meister as whole.
If the gallery is empty, just click on the "Gallery" link in the card page (the link should be in red). This will open the editor, where you able to create the page.
For starters, I recommend to take a look at any existing gallery page. Open the page in editor, then simply copy-paste the content to the new page and add/remove or modify the information to suit the new page. Note that most of them are created using the source editor (or wikicode) instead of visual editor so you might have to adjust.
If you find any difficulties, please don't hesitate to contact any admin or discuss it on the forum.