Template talk:Cardpage - Revision history

Corvantes: /* More categories? */ new section

2013-11-06T04:29:26Z

‎More categories?: new section

Phaselock at 07:16, 9 November 2012

2012-11-09T07:16:18Z

Phaselock at 13:18, 8 November 2012

2012-11-08T13:18:05Z

Phaselock at 13:14, 8 November 2012

2012-11-08T13:14:34Z

Mightymushroom at 00:09, 3 November 2012

2012-11-03T00:09:01Z

Mightymushroom at 00:06, 3 November 2012

2012-11-03T00:06:21Z

Mightymushroom at 23:41, 2 November 2012

2012-11-02T23:41:52Z

Mightymushroom at 23:35, 2 November 2012

2012-11-02T23:35:39Z

Phaselock at 02:14, 31 October 2012

2012-10-31T02:14:31Z

Mightymushroom at 16:00, 30 October 2012

2012-10-30T16:00:56Z

← Older revision		Revision as of 04:29, 6 November 2013
Line 125:		Line 125:

	-PL		-PL
		+
		+	== More categories? ==
		+
		+	It would add a lot to usability if the template would generate more categories. I'd go ahead and do it myself but the template is locked (for a good reason).
		+
		+	The major ones I'd like to have are:
		+	* By quality: [[:Category: Gold Quality Card]] etc.
		+	* By rarity: [[:Category: Common Card]], [[:Category: Uncommon Card]], [[:Category: Rare Card]]
		+	* By attack types: [[:Category: Melee Attack Card]], [[:Category: Magic Attack Card]],
		+	* By damage type: [[:Category: Lightning Attack Card]]
		+	* By attack rider effect: [[:Category: Step Attack Card]], [[:Category: Penetrating Attack Card]], [[:Category: Bash Attack Card]], [[:Category: Chop Attack Card]]
		+	* Game elements: [[:Category: Trait Card]]
		+
		+	Quality, rarity, attack and damage can be added automatically quite easily. Step attacks etc. may require some string filtering.
		+
		+	This would help a lot for deck building and comparing items as well as suggesting new cards and items.
		+
		+	--[[User:Corvantes\|Corvantes]] ([[User talk:Corvantes\|talk]]) 20:29, 5 November 2013 (PST)

@@ Line 118: / Line 118: @@
 #<span style="color:red">Updated Type, damtype and effect type (to review after beta release)</span>
 #<span style="color:red">Updated Play effect. Range, duration, self target, chance and keep are dynamic, delete entries if not required. Ditto for reactions.</span>
-#<span style="color:red">Updated categories in Cards category. (Class category redundant, cf community portal classifications)</span>
+#<span style="color:red">Updated categories in Cards category. (Still considering other proper categories, we might need more than just class/types)</span>
 #<span style="color:red">Updated template help text for contributors, including acceptable card quality and card color entries.</span>
 #<span style="color:red">Updated all cards as per reflected in forum</span>

@@ Line 122: / Line 122: @@
 #<span style="color:red">Updated all cards as per reflected in forum</span>
 #<span style="color:red">Bug fix: flavor text fouling up column widths</span>
-<span style="color:red">''Remarks: Due to dynamic row entries in table, background color looks weird. I might consider other presentation alternatives when free.''</span>
+<span style="color:red">''Remarks: Due to dynamic row entries in table, background color looks weird (cf Bash). I might consider other presentation alternatives when free.''</span>
 -PL

← Older revision		Revision as of 13:14, 8 November 2012
Line 112:		Line 112:
	:*Consider adding list of acceptable colors to 'titlebar' and 'cardcolor' instructions -- will reduce chance of unanticipated response		:*Consider adding list of acceptable colors to 'titlebar' and 'cardcolor' instructions -- will reduce chance of unanticipated response
	:-- mm		:-- mm
		+
		+	<span style="color:red">Changelog:</span>
		+
		+	#<span style="color:red">Updated Color Class (to review after beta release)</span>
		+	#<span style="color:red">Updated Type, damtype and effect type (to review after beta release)</span>
		+	#<span style="color:red">Updated Play effect. Range, duration, self target, chance and keep are dynamic, delete entries if not required. Ditto for reactions.</span>
		+	#<span style="color:red">Updated categories in Cards category. (Class category redundant, cf community portal classifications)</span>
		+	#<span style="color:red">Updated template help text for contributors, including acceptable card quality and card color entries.</span>
		+	#<span style="color:red">Updated all cards as per reflected in forum</span>
		+	#<span style="color:red">Bug fix: flavor text fouling up column widths</span>
		+	<span style="color:red">''Remarks: Due to dynamic row entries in table, background color looks weird. I might consider other presentation alternatives when free.''</span>
		+
		+	-PL

@@ Line 85: / Line 85: @@
 ::'''Quality:''' title bar color
 ::'''Rarity:''' rarity
-::'''Color Class:''' color(s) -- ''"Color Class" to tie what we call class to card colors
+::'''Color Class:''' color(s), outputs Attack etc. -- ''"Color Class" to tie what we call class to card colors
 ::'''Card Type:''' from info box  -- ''I know "Type" isn't official either but it seems the best option currently''
 ::<nowiki><!-- On Play Instructions (light text box) --></nowiki>

@@ Line 79: / Line 79: @@
-:*So I've been thinking it over, and I changed my mind.  I no longer think it's so important to separate instant and duration in the card template. Because there's certainly a difference in terms of game logic, but there is too often not an obvious difference in the instruction text. I think it'll be easier to understand input-wise if it just asks for what's in the boxes. Suggested lines:
+:1. So I've been thinking it over, and I changed my mind.  I no longer think it's so important to separate instant and duration in the card template. Because there's certainly a difference in terms of game logic, but there is too often not an obvious difference in the instruction text. I think it'll be easier to understand input-wise if it just asks for what's in the boxes. Suggested lines:
 ::<nowiki><!-- Card Information --></nowiki>
@@ Line 108: / Line 108: @@
 :How's that look?
-:*Add to To Do list:
+:2. Add to To Do list:
-::Add Categories to template output. I'm thinking just categories by Class, so this can be tucked into the color->class sub-template to assign automatically.
+:*Add Categories to template output. I'm thinking just categories by Class, so this can be tucked into the color->class sub-template to assign automatically.
 :-- mm

← Older revision		Revision as of 23:41, 2 November 2012
Line 107:		Line 107:
	::'''Flavor Text:''' flavor text		::'''Flavor Text:''' flavor text

−	:How's that look? -mm	+	:How's that look?
		+	:*Add to To Do list:
		+	::Add Categories to template output. I'm thinking just categories by Class, so this can be tucked into the color->class sub-template to assign automatically.
		+	:-- mm

← Older revision		Revision as of 23:35, 2 November 2012
Line 77:		Line 77:

	-PL		-PL
		+
		+
		+	:*So I've been thinking it over, and I changed my mind. I no longer think it's so important to separate instant and duration in the card template. Because there's certainly a difference in terms of game logic, but there is too often not an obvious difference in the instruction text. I think it'll be easier to understand input-wise if it just asks for what's in the boxes. Suggested lines:
		+
		+	::<nowiki><!-- Card Information --></nowiki>
		+	::'''Name:''' name
		+	::'''Quality:''' title bar color
		+	::'''Rarity:''' rarity
		+	::'''Color Class:''' color(s) -- ''"Color Class" to tie what we call class to card colors
		+	::'''Card Type:''' from info box -- ''I know "Type" isn't official either but it seems the best option currently''
		+	::<nowiki><!-- On Play Instructions (light text box) --></nowiki>
		+	::'''Play Effect 1:''' when the card Plays -- ''including damage, healing, movement, attachment''
		+	::'''Play1 Range:''' integer (if 0, line is optional)
		+	::'''Play1 Duration:''' integer (or delete line)
		+	::'''Play1 Self Target:''' yes (or delete line)
		+	::'''Play1 Chance:''' integer+ (or delete line)
		+	::'''Play1 Keep:''' yes (or delete line) -- ''{{K\|Keep}} appears to be the new/current word for return to hand''
		+	::'''Play Effect 2:''' -- ''I'm still not convinced this exists, but if you want it, copy all the stuff from Play1''
		+	::...
		+	::<nowiki><!-- Reaction Instructions (dark text box) --></nowiki>
		+	::'''Reaction Effect 1:''' when the card reacts
		+	::'''Reaction1 Range:''' integer (or delete line)
		+	::'''Reaction1 Duration:''' integer (or delete line) -- ''if the Reaction creates an attachment''
		+	::'''Reaction1 Self Target:''' yes (or delete line) -- ''is this necessary? not sure with small sample size''
		+	::'''Reaction1 Chance:''' integer+ (or delete line)
		+	::'''Reaction1 Keep:''' yes (or delete line)
		+	::'''Reaction Effect 2:''' same stuff again
		+	::...
		+	::'''Flavor Text:''' flavor text
		+
		+	:How's that look? -mm

← Older revision		Revision as of 02:14, 31 October 2012
Line 59:		Line 59:
	:* Circling back to your 1: Both "Class" and "Sub-Class" are my words. The most official term I've heard for color is probably "color" and I don't think they've talked about the "Melee, Crushing" part at all. I am waffling between using (Sub-)Class or (Sub-)Type or something else entirely as the preferred terms on the wiki. Suggestions welcome.		:* Circling back to your 1: Both "Class" and "Sub-Class" are my words. The most official term I've heard for color is probably "color" and I don't think they've talked about the "Melee, Crushing" part at all. I am waffling between using (Sub-)Class or (Sub-)Type or something else entirely as the preferred terms on the wiki. Suggestions welcome.
	: -mm		: -mm
		+
		+	<span style="color:red">ok, I think I've gotten your drift. I've summarized and raised a few other issues largely because of some new developments.</span>
		+
		+	#<span style="color:red">The first issue here is from http://www.cardhunter.com/2012/10/card-rarities-2/. To-do list for template is updated right below.</span>
		+	#<span style="color:red">I'll make the change for effect type to subtype. No idea what the devs are calling it either. This is just a 2s cosmetic change. :P Card info becomes a static module per card. Included in to-do list.</span>
		+	#<span style="color:red">You want to put Damage, Range into an On Play dynamic module. Do you want to seperate movement range from spell range ? damage from heal ? I'd reckon that fixed integers go into these entries. And a dynamic text entry for on play effect. How does that sound ?</span>
		+	#<span style="color:red">On Play (instant), Reaction (also instant), and Attachment (duration). ok, understood. 3 sets of dynamic modules...</span>
		+	#<span style="color:red">'As it is, I get errors if I fail to include the four lines each time I have an effect1 or reaction2 or whatever.' Aha, this is what I need...hmm, I need to make some more templates :P</span>
		+	#<span style="color:red">'I believe that a card will not have more than one Play Effect or more than one Attachment' Not too difficult for devs to make an On Play effect be conditional upon the game state. Eg: If 1 enemy is in range, do A. If 1 ally in range, do B.</span>
		+	#<span style="color:red">To-do list:</span>
		+	:*<span style="color:red">Change 'tier' to 'quality'</span>
		+	:*<span style="color:red">Include Rarity (I think this should be in Card Info)</span>
		+	:*<span style="color:red">Change Type to Subtype.</span>
		+	:*<span style="color:red">Make 3 dynamic templates (On Play, Reaction and Attachment)</span>
		+
		+	''PS: won't be doing anything until rosh gets the server protection up, we can bulk up the to-dos until then. :)''
		+
		+	-PL

@@ Line 55: / Line 55: @@
 :* However, I concede that there is a simple perceptive distinction between light and dark text boxes, i.e. Play Effects and Reaction Effects. This is the system we have now. I am willing to be overruled on the necesssity of splitting instant and attachment.
 :* On your 4: Oops, you're right. We definitely want to avoid implying chains where there are none.
-:* On your 6: If I ever edit the template, it's a fair bet that every line will become optional. As it is, I get errors if I fail to include the four lines each time I have an effect1 or reaction2 or whatever. Not all instructions use all four lines.
+:* On your 6: If I ever edit the template, it's a fair bet that every line will become optional. As it is, I get errors if I fail to include the four lines each time I have an effect1 or reaction2 or whatever. Not all instructions use all lines.
 :* Circling back to your 3: As a matter of logic, I believe that a card will not have more than one Play Effect or more than one Attachment. If it did, that would require interrogating the player as to which Play Effect should be used; it's a complication that we have not seen and that I believe the dev team will be leery of employing. No, I have no confirmation that it will never happen in the future. But I just don't see a need now, and future editors can add it in if it arises. Attachments are even less likely to be doubled, because the card sits there explaining its effect and how would you know which explanation is in play?
-:* Circling back to your 1: Both "Class" and "Sub-Class" are my words. The most official term I've heard for color is probably "color" and I don't think they've talked about the "Melee, Crushing" part at all. I am waffling between using (Sub-)Class or (Sub-)Type or something else entirely as the preferred terms on the wiki.
+:* Circling back to your 1: Both "Class" and "Sub-Class" are my words. The most official term I've heard for color is probably "color" and I don't think they've talked about the "Melee, Crushing" part at all. I am waffling between using (Sub-)Class or (Sub-)Type or something else entirely as the preferred terms on the wiki. Suggestions welcome.
 : -mm