Mabinogi World Wiki is brought to you by Coty C., 808idiotz, our other patrons, and contributors like you!!
Want to make the wiki better? Contribute towards getting larger projects done on our Patreon!
Template talk:StyleWeapon
Repair
does anyone else think we should add parser functions to automatically fill in the repair rates when either the npc purchase price or another repair rate is known? --Sozen Cratos Focker 09:19, 5 July 2010 (UTC)
- That wouldn't work because the repair rate charts are inaccurate. There's a different formulas for different types of items btw.--Hengsheng120·TALKCONTRIBS 09:44, 5 July 2010 (UTC)
- I could add a feature where it calculates an approx. repair price - but only if mediawiki supports math.
And I think mediawiki doesn't support mathNvm, I just checked and it does support math. But it would increase the size of the template by a lot (At least 3KB) ~kotarou3 TALKCONTRIBS 09:52, 5 July 2010 (UTC)
Width
omg table is so wide. x.x too much black space around the weapon, see dustin knight sword, please make table 80%? -- ladywinter ~{talk | contribs}~
- Yes, I could make it thinner, but it will start to look ugly. I didn't really want it this wide either :/ ~kotarou3 TALKCONTRIBS 21:00, 20 July 2010 (UTC)
- Maybe make the "Obtained from" a scrollable box when it gets to over a certain width or whatever? That part of the table seems to be what causes the extra stretching. Or, we could start adding line breaks when the droplist gets too crowded. It seems like someone did this on Dagger already. --- Angevon (Talk) 21:22, 10 October 2010 (UTC)
- I hope changing up the rowspan/colspan didnt make it look weird. If it's no good, revert it. --κєνıи (»тαıĸ«) 04:08, 11 October 2010 (UTC)
- Oh wait, we're talking about the width? Oops. :c --κєνıи (»тαıĸ«) 04:12, 11 October 2010 (UTC)
- I hope changing up the rowspan/colspan didnt make it look weird. If it's no good, revert it. --κєνıи (»тαıĸ«) 04:08, 11 October 2010 (UTC)
- Maybe make the "Obtained from" a scrollable box when it gets to over a certain width or whatever? That part of the table seems to be what causes the extra stretching. Or, we could start adding line breaks when the droplist gets too crowded. It seems like someone did this on Dagger already. --- Angevon (Talk) 21:22, 10 October 2010 (UTC)
Unknown Parameters
Is there a reason unknown paramters should be deleted? Why not have it there, just blank? It'll be hard for anyone to add the parameter not knowing the parameter name, and it's highly doubtful anyone'd come to the template just to find out. --- Angevon (Talk) 18:05, 19 July 2010 (UTC)
- Well, some people copy+paste some other template and replace everything with "???", "-", etc for what they don't know. And it also keeps the data more readable ~kotarou3 TALKCONTRIBS 21:00, 20 July 2010 (UTC)
Center or not to center?
The template looks much better if it was centered on the page IMO. What do others think? ~小太郎 TALKCONTRIBS 2011:03:06:03:22 (Sunday)
- would seem weird considering most of the templates aren't centered. --κєνıи (»тαıĸ«) 05:38, 6 March 2011 (UTC)
- Maybe we should start a movment for getting the others to be centered? :D ~小太郎 TALKCONTRIBS 2011:03:06:06:07 (Sunday)
- [View source↑]
- [History↑]
Contents
Thread title | Replies | Last modified |
---|---|---|
summon_set and rag dolls | 0 | 11:47, 2 August 2021 |
Archery Info Update? | 3 | 20:36, 12 June 2016 |
no_bolt_stack needs to be seperated | 2 | 15:49, 23 March 2014 |
Enthralling Performance | 0 | 22:30, 7 October 2013 |
Projectile Types | 0 | 15:42, 8 August 2013 |
Defaults | 3 | 18:33, 6 April 2013 |
Demonic Weapons & Special Upgrades | 2 | 22:20, 31 March 2013 |
Template currently broken | 0 | 09:48, 6 March 2013 |
no_bolt_stack | 1 | 17:58, 18 February 2013 |
Icon background color | 14 | 23:00, 3 September 2012 |
Ego/Spirit | 2 | 15:19, 4 August 2012 |
Minor Typo | 1 | 18:23, 31 July 2012 |
This new template | 7 | 18:34, 24 July 2012 |
Giants and Bows/Xbows | 3 | 18:45, 23 July 2012 |
splash and stamina usage | 3 | 17:27, 11 May 2012 |
Ducat Repairs | 0 | 10:44, 11 October 2011 |
Needs Enchanting and NeedsUpdating | 2 | 17:15, 28 February 2011 |
Now that we have a couple different rag dolls, how should the switch cases for the summon_set parameter work? Currently there are only two "valid" summonable dolls defined in the template, Squirrel and Fennec Fox, and the other pages either have a typo (e.g. Lesser Panda Rag Doll saying that it summons a Fennec Fox), or weapon data just end up in the default case (e.g. Rabbit Rag Doll summons "a ???")... Would it make sense to add another switch case for each of the rag doll types? Or... something else?
A friend of mine noticed recently and brought it to my attention that after the archery renovation they changed the bow system from a "hit" system to a general one. For example before the renovation some bows that were ranked "Slow 2 hit Weapon" has now been reworded as "Slow Ranged Weapon." Seeing that the pages on mabi haven't been updated to that format, not on the bows lists or the individual bow pages, is that something to update?
You should probably stop asking questions on Infodude's user talk page since that's intended to be used for asking him something directly. Please ask your questions on the talk pages for articles related to your questions (e.g. Talk:Dressing Room for questions about the Dressing Room) or the Wiki Home talk page for questions related to many pages at once. I've moved this thread to Template_talk:StyleWeapon for now.
Now to answer your question, we will probably need to edit Template:StyleWeapon in order to update it, but I'm not entirely sure how we should do it. Is there anyone around who's experienced with that template?
It should be easy enough, I think. Just set all the weapons that have range to display "Ranged" instead of "3 Hit" or "2 Hit". And it should also be simple to change the Bows List page's "Speed [Hit]" to "Speed [Stun]" or something.
Hit count apparently determines the stun duration though. Has that changed in any way?
The way the template currently handles no_bolt_stack doesn't apply to Merlin's Shyllien Mana Knuckles. As of right now, if the weapon is a staff but has no_bolt_stack, the template will display that the staff can't be elementally charged, but it can still use intermediate magic. However, the knuckles can be charged with elements, but doesn't require the charges to use int magic.
Some instruments can't be used to play ^. Could a tag be added for this? Please and thank you.
Is it really necessary to say weather a ranged weapon uses arrows or bolts in the "other information" box?
Can we please make the default parameters as unknown rather than a blatant no? (Even in places where it is a yes like most demonic weapons.) It is really misleading to have the default be no.
If the default parameter was "unknown", all "no"s would become "unknown" because the template displays 'yes' if it is explicitly defined as yes, otherwise it is displayed as no.
But when you first suggested the new template, I explicitly said to make sure no was not the default, yet you did leave no the default.
I'm assuming you're referring to this.
The only two sections in the limitations table that require manual input are "Special Upgrade" and "Spirit Weapon". Every other box is automatically done by the itemdb fillout (meaning they will not be unknown; they are known).
Because of how the template works (the list of items that can be egoable/special upgradable is integrated into the template, rather than each weapon's data), replacing "X" by default with "?" would replace ALLLLLLLLLLLLLLLLLL "X"'s for those two sections with "?". For every of those pages, you'd have to them respecify that they cannot be specialupgraded/ego'd (redundant enough as it sounds).
Considering most items that cannot already be ego'd or special upgraded will probably never be ego-able or special upgradable, it's safe to assume all items that are not listed in this template are not egoable or special upgradable.
If, in the future, there comes a time where a currently existing item becomes egoable or special upgradable, it will quite easy to determine. All you'd have to do is look for a new itemdb entry with "Spirit ASDF" or "ASDF R/S". That would be easier and quicker than having to go through every single weapon page and explicitly define the weapon as "not egoable" or "not special upgradable".
...needs fixing, as most demonic weapons can be special upgraded but the template is not showing it properly.
I'm not sure what was recently changed here (or if this is actually deliberate), but all the pages that include this template are broken right now. If you're changing it around, could you do it locally instead of breaking everything?
The staff category parser needs updating to handle the addition of /no_bolt_stack/ with addition of the Hermit Staff.
I changed the background color for the icon to be gray like Template:StyleFood. This way the icons for items that naturally have black (e.g. Cichol Puppet) will be visible. Is everyone okay with this, or do you have a different color to suggest?
I'm not familiar with the css so I didn't want to touch it. Tell me where to change it and I'll do it.
It's pretty much the same as regular coding. All you have to do is replace
table.mabitable tr.image td, table.mabitable td.image, table.imagetable td, table.imagetable th { background-color: #000; }
with
table.mabitable tr.image td, table.mabitable td.image, table.imagetable td, table.imagetable th { background-color: #333; }
(I think.) But that will effect every imagetable on the wiki. No item will have a black background.
The only unpleasant side effect I can think of doing this is that all of those nice previews people has taken in front of the Dunbarton Library doorway will look odd now. :\
After thinking about this, and seeing the current results I think I prefer a completely black background because it makes most icons pop out more. But perhaps apply a switch when you are dealing with an icon that contain black.
I don't like the gray much, either. It looks out of place since the table's borders are also gray. I'm fine with the switch idea.
So, should it be a style override such as ImageStyle=background: #333;
or more like BlackIcon=y
While the latter is shorter, the former is more customizable for the situation.
The wiki page is spirit, in-game it is spirit, so why is ego used instead of spirit in this template?
I know this is an extremely trifling little thing, but...
|53 3=clay
Shouldn't that be "clap"? Noticed it on the Drums of Kindness page and had to do some creative backtracking.
is really something...every weapon page I go it has like...a ton of these operand errors...
Don't worry, I don't want other people to work on it because I have a special xml that I edited to work with. :P
It's a hell of a lot of work to add all the strings and do the cleaning up job, though. I've only gotten through about... I don't know.. 50? Since 4 hours ago? D:
Edit: 3 hours.
I like the idea behind the limitations section of the template, but it makes the template extend past the screen on browser windows smaller than about 1125 pixels wide. Not even mentioning that many people keep their web browser windows smaller than that on purpose, 1024x768 is still a very commonly used screen resolution. Generally, needing to scroll both horizontally and vertically on the same page is considered to be bad web design.
Will splash info and stamina usage be incorporated into this template in the future? (rather, should I keep adding this info on the data template for each weapon?)
At some point, they should be worked in along with stamina per melee attack. Not exactly sure the best way to list them on the table. Ideas?
Maybe keep the stamina part right above the table, since I think people are used to it being displayed there. But for the splash, I don't know either. Some pages have a separate table underneath the weaponbox (e.g. Dagger), so that's a possibility, but it's a bit messy to have 2 tables.
That's what I was thinking to do about Stamina. I may go ahead and add it and use a check for those with the stamina already defined.