Time for a Community Made Game?

continued...
Sun, 2009-10-25 01:30
Art_Freak
Template Developer
Art_Freak's picture

... I had my days

... I had my days confused... that's what a friday off will do to you (I thought today was sunday). I meant whoever is in the lead a week from now (so the morning of Saturday, 10/31/09), will be our project leaders.

Sun, 2009-10-25 02:27
ocb777
ocb777's picture

My Votes

smr1313
Not Me
A Tactical Waffle
Not Me
Art_Freak
Not Me
Idle Muse
Not Me
Jéské Couriano

BY THE WAY: NOT ME. If/as time allows I would happy to consult/advise/etc., but I do not have time to dedicate myself to a project like this. I appreciate the nominations, but I respectfully withdraw.

My fan sets and lots of other stuff I've done: Click Here!

Sun, 2009-10-25 09:37
copapoc
copapoc's picture

smr1313powerrox93art_freak

smr1313
powerrox93
art_freak
idle muse
jéské couriano

alive and kicking relics of alara

Sun, 2009-10-25 14:14
Powerrox93
Powerrox93's picture

To everyone, I'm withdrawing

To everyone, I'm withdrawing of personal reasons from this

Sun, 2009-11-01 05:08
Shiv2503
Shiv2503's picture

well not much has happened

well not much has happened in the last week so I tallied the votes thus far, and the top three are:
smr1313: 5
A Tacticle Waffle: 4
Art_Freak: 4

The runners up(Both ocb777 and Powerrox93 withdrew their names.) are:
Jéské Couriano: 3
Idle Muse: 2
copapoc: 2

Sun, 2009-11-01 14:11
lord_joakim
lord_joakim's picture

Not to piss anybody off, but

Not to piss anybody off, but I'm voting for Art_Freak and Idle Muse.

But don't tally them if it slows this project down. I'd rather have it running.

Sun, 2009-11-01 15:10
A Tactical Waffle
A Tactical Waffle's picture

Why would anybody be pissed

Why would anybody be pissed off. It doesn't even change the results... Idle Muse would be left with 3 (Not high enough to get him into the top 3 and Art_Freak is left with 5, so the top 3 are still me, smr1313, and Art_Freak.

Through enough goblins at any problem and it should go away. At the very least, there'll be fewer goblins.

Sun, 2009-11-01 18:22
Art_Freak
Template Developer
Art_Freak's picture

Well, it looks like we just

Well, it looks like we just need to hear from smr1313 then and we'll have the leaders on board. If he doesn't post by the end of the day I'll try contacting him on pifro (if he's there), or by email.

I'm going to layout what I consider the purpose of the leaders: To keep the project moving forward, to keep good spirits, and to help settle disputes and make key decisions on aspects of the game and style. So everyone is still welcome and encouraged to post their ideas, but the final say on the things people can't agree on fairly unanimously will go to the leaders so that the project can keep moving forward.

So let's settle on the game and it's rules before we design a template for it. From the look of it my template/set design game was a popular one. My first question then is should the game focus on template design or set design? My vote would go towards set design as I think that fairly represents what any member of the MSE2 community is and can be a part of (template design and scripting isn't for everyone afterall. Stick out your tongue)

As a starting point for the rules I'll just quote my original post here and we can build off of that:

Quote:
Why don't we do a game based on creating a template or set since it's to represent the MSE community. The win cons would be 1) A completed template/set or 2) Decking (the opponent has run out of ideas). The card types would be: If template: script, set field, card field, style, and symbol; If set: concept, creator, design, art, and time.

Basically you'd start the game with a deck and 10 "community interest points". Each card played would cost points but also provided more points based on it's effect (easier to play = fewer points, harder to play = more points). Cards could also be played that affect your opponent's interest pool so that as your project gains momentum, their project loses it.

Mon, 2009-11-02 02:55
A Tactical Waffle
A Tactical Waffle's picture

Ya, I wonder where smr1313

Ya, I wonder where smr1313 is. He hasn't posted at all...

I think we should to template design for a few reasons: Although less people know how to script, it still is a major part of the community and the make a set idea might make it revolve to much around an already existing card game.

Through enough goblins at any problem and it should go away. At the very least, there'll be fewer goblins.

Mon, 2009-11-02 08:09
ocb777
ocb777's picture

A note from moi

If you make a game based on templating... throw in real coding and terms, those of us who are code ignorant might learn something and become more useful to the community! A happy smile

My fan sets and lots of other stuff I've done: Click Here!

Tue, 2009-11-03 03:09
Art_Freak
Template Developer
Art_Freak's picture

I PM'd smr1313 at the pifro

I PM'd smr1313 at the pifro boards. If he doesn't respond here or there then I'll try to email him.

Well, we've got 2 for templating and 1 for set building. I'd like to keep this project moving, but I'd also like to hear more than three opinions. This game is going to represent these boards and its users, and you don't have to devote yourself to the project to give an opinion on where you'd like to see it go. So please, let's hear some more feedback! Big smile

Tue, 2009-11-03 04:05
Jéské Couriano
Jéské Couriano's picture

ocb77) Or not. I can barely

ocb77) Or not. I can barely tweak templates to alter fonts properly; adding actual code is just gonna make me feel stupid, even if it's just added as flavor text.

I also create custom D&D material!

Sets:
SSB (predesign)
Jargon File (design)
Echoes Block [Echoes of Past and Present, Anthrologies, Trinity's Heartsease] (design)
Mother (design)

Tue, 2009-11-03 04:23
windandfire
windandfire's picture

I second the opinion that

I second the opinion that this should be based off making custom sets, rather than templates. For one, take a look at the templater:set designer ratio here. You'll be losing out on a large chunk of your audience if we can't understand the terminology. Consider how many of Unglued and Unhinged's jokes a non-magic player would understand for instance.

A side effect of the above means you'll have more people able to catch errors and critique the actual game if you shift your focus away from templating.

The end result might be closely tied to Magic, but that's not necessarily a bad thing. While mse is used for other card games, it is my understanding that, due to the chosen name, it is first and foremost a tool for developing Magic sets.

"I will do science to it." - Kimiko “Thunderbolt” Ross
"I can wire anything directly into anything - I'm the professor!" - Professor Hubert J. Farnsworth
"Our tanks can't hold aggro of that magnitude!

Tue, 2009-11-03 04:49
Shiv2503
Shiv2503's picture

I'm going to have to vote

I'm going to have to vote for template making. I feel that a game based on template making would have alot more to offer then making sets. Although if anyone would enplane what sorts of possible game play mechanics.
also @ Jéské Couriano and windandfire I don't think if we did a templating based game it would need anything talking about individual functions, just coding as a broader group.

Tue, 2009-11-03 05:45
Jéské Couriano
Jéské Couriano's picture

Shiv2503) What I'm saying is

Shiv2503) What I'm saying is that we shouldn't be adding coding instructions or code itself to the cards for the benefit of the muggles here (and I wager there are plenty of them; I'm closer to script kiddie myself but still can't wrap my head around the more complex stuff).

Yes, I am leaning towards set building if only because it's the only category where I'd know what the frag I'm doing.

I also create custom D&D material!

Sets:
SSB (predesign)
Jargon File (design)
Echoes Block [Echoes of Past and Present, Anthrologies, Trinity's Heartsease] (design)
Mother (design)

Tue, 2009-11-03 06:19
Shiv2503
Shiv2503's picture

The thing I'm worried about

The thing I'm worried about is what game play a set building game would have, Not saying it's a bad idea, I just need some general concepts on how the actual manics would work.

Tue, 2009-11-03 06:24
Jéské Couriano
Jéské Couriano's picture

I would think it a

I would think it a bankout-style game (c.f. Neopets and Heresy), where each point meant that your set was more balanced and/or popular, and the objective to reach a certain number of points.

For example, Card additions are card phenotypes that are commonly added to sets (such as counter/negation cards, beatsticks, etc.), Rules addendums are alterations to the rules (which can add to or subtract from a player's banked amount), Publicity means to try to reach new players (maybe starting with a small payment of banked points to secure a continual effect?), etc.

Note the above is just an idea.

I also create custom D&D material!

Sets:
SSB (predesign)
Jargon File (design)
Echoes Block [Echoes of Past and Present, Anthrologies, Trinity's Heartsease] (design)
Mother (design)

Tue, 2009-11-03 06:44
Shiv2503
Shiv2503's picture

For "Just an idea" it sounds

For "Just an idea" it sounds pretty good.Stick out your tongue

Tue, 2009-11-03 06:51
Jéské Couriano
Jéské Couriano's picture

I assure you it is just an

I assure you it is just an idea, I was pulling it outta my a** as I was typing it up.

Though now that I actually think about it it does sound pretty good.

I also create custom D&D material!

Sets:
SSB (predesign)
Jargon File (design)
Echoes Block [Echoes of Past and Present, Anthrologies, Trinity's Heartsease] (design)
Mother (design)

Tue, 2009-11-03 20:33
Neko_Asakami
Neko_Asakami's picture

I like Jéské's idea. A

I like Jéské's idea. A lot. However, I don't like the idea of not having any coding. I think that having coding represent changes you can make to your set (new frames, extra colors) or cards (new fonts, foil overlays) that aren't part of the regular "Set file" could be a good thing. (Think of Code kind of like enchantments in Magic) This represents the fact that 98% of code requests are the same things over and over, and are usually just set tweaks.

Tue, 2009-11-03 20:45
Jéské Couriano
Jéské Couriano's picture

Neko_Asakami) Again, I'm

Neko_Asakami) Again, I'm opposed to including code snippets or coding tips in the cards (cards representing coding changes I'm OK with).

ALL) Please, for the love of all that is decent, actually read my objection before you comment on it, okay?

I also create custom D&D material!

Sets:
SSB (predesign)
Jargon File (design)
Echoes Block [Echoes of Past and Present, Anthrologies, Trinity's Heartsease] (design)
Mother (design)

Wed, 2009-11-04 00:20
Neko_Asakami
Neko_Asakami's picture

Jéské, I understood what

Jéské, I understood what you were saying, I just wasn't clear in my response. ^_^ I was offering it as an idea that, while light on actual code, could allow "coding" to have a strong mechanical presense in the game. I think that to completely remove the idea of coding from a game based on our forums would be as bad as removing all cards relating to artwork. Simply put, it's a large part of what this forum is, even if you're not involved in that part.

Realistically, using coding terms in the game for anything other than keywords or flavor text is a bad idea, just due to complexity and lack of widespread knowledge. That I agree on. However, saying that no code whatsoever should be used is limiting to mechanics, keywords, and flavor text. Yes, you might not like it, or even understand it, but how often do you hate a quote on a Magic card and your friend absolutely loves it? How often do you look at a card and think "That is pure crap" and end up sitting down across from someone who has built a deck around that card? Our game, like Magic, should try to appeal to as wide an audience as possible and that will mean not being able to please everyone with every card.

Edit: On a very much related note, we have coders, artists, and set designers on the team, but do we have someone dedicated to flavor? Someone working on the creative aspect of the game, not just the mechanical?

Wed, 2009-11-04 00:44
Art_Freak
Template Developer
Art_Freak's picture

Great to see some serious

Great to see some serious feedback on this, and it seems we have a close divide among the opinions given. We have 2 for coding being included (Shiv & Neko), and 2 against it (Jeske & windandfire). Myself, I was leaning towards a strictly set making game because the vast majority of the users of this forum don't do any templating. However, I completely agree with Neko's point about coding used in the game representing changes you'd make to your set to make it more interesting than your opponent's. Think of that this way using MTG and it's R&D playing our yet unmade game as the example: Player A has built Saviors of Kamigawa and Player B is building Ravnica. Player B plays the "Add Hybrids" card and suddenly their set pulls ahead in interest and they take the game.

While adding hybrids to any set seems like second nature to most MTG players and it could be argued as just an included aspect of the game, it is actually a very, very complicated piece of scripting that is only featured in the MTG game files. No other game currently available for MSE2 has it, and to include an "Add Hybrids" card in a game about set making assumes that the game is for making MTG sets if it is not included as a template/coding aspect (which then would make it applicable to any game.)

I'm going to have to keep my vote with set making as the focus, but I am also really for the inclusion of coding based cards.

Wed, 2009-11-04 01:07
Jéské Couriano
Jéské Couriano's picture

Art_Freak) A-fragging-gain?!

Art_Freak) A-fragging-gain?! How many times do I have to say it? I'm against ACTUAL CODE on the cards. I don't object to cards about coding options.

I'm getting tired of being misrepresented.

I also create custom D&D material!

Sets:
SSB (predesign)
Jargon File (design)
Echoes Block [Echoes of Past and Present, Anthrologies, Trinity's Heartsease] (design)
Mother (design)

Wed, 2009-11-04 01:26
Idle Muse
Template Developer
Idle Muse's picture

I love how despite never

I love how despite never posting on the forums (aside from to start and then abandon threads), smr1313 has been voted onto the commitee for this game. And despite only posting inane comments in this thread, all I'd need to do to put myself onto the committee is vote for myself. Unfortunately I just don't have the time to do anything but post inane comments, so I won't A happy smile

Formerly known as Lordpenguin.
Download DraftWithMSE to draft custom MSE sets!

Wed, 2009-11-04 02:38
Art_Freak
Template Developer
Art_Freak's picture

@Idle: I appreciate your

@Idle: I appreciate your inane comments, lol.

@Jeske: You're entitled to your opinion, but don't scream it like yours is the only one that counts here. I believe you yelled at Menasor for something similar not long ago.

EDIT: It is important to note that you are talking about something completely different than what I am Jeske. You seem to be saying that none of the "if.. then.. else" coding statements and the like should be on the cards. I'm just saying something that represents it should be in the game, like a themed card. Take my example card for argument's sake "Add Hybrids". It would be something like:

Quote:
Add Hybrids
Cost: 4
Type: Template Element
Effect: When you play ~, add 4 points to your interest pool. At the beginning of your turn, add 1 point to your interest pool.

Not...
Spoiler:
Quote:
Add Hybrids
Cost: 4
Type: Template Element
Effect: Your set has:
# Scripts for blending images
# Included by a style file in its init script


########################################################################
# Filenames and other defaults
########################################################################

mask_hybrid_with_land	:= { false }
mask_multi_land_with_color	:= { false }
template		:= { input + "{type}.jpg" }
land_template		:= { (if input == "a" then "c" else input) + "l{type}.jpg" }
# For what value should thumbnails of hybrids be made?
hybrid_previews         := "hybrid"
# Are there templates for colored lands, land_template(...)?
colored_lands           := true

########################################################################
# Combining multiple colors (hybrids)
########################################################################

card_hybrid_2 := {
	linear_blend(
		image1: template(colors[0])
		image2: template(colors[1])
		x1: 0.4,  y1: 0
		x2: 0.6,  y2: 0
	)
}

overlay_hybrid := [
	1: { template(colors[0]) }
	2: { combine_blend(
		image1: template(colors[0]),
		image2: template(colors[1]),
		combine: "symmetric overlay"
	   )}
]

# vertical version of a horizontal hybrid
vertical_card_hybrid := {
	do_linear_blend := linear_blend
	linear_blend := { do_linear_blend(x1: 0, x2: 0, y1: x1, y2: x2) }
	card_hybrid.horizontal[color_count]()
}

horizontal_card_hybrid := [
	1: { template(colors[0]) }
	2: card_hybrid_2
	3: {linear_blend(
		image1: template(colors[0])
		x1: 0.22,  y1: 0
		x2: 0.4,   y2: 0
		image2: linear_blend(
		  image1: template(colors[1])
		  x1: 0.6,   y1: 0
		  x2: 0.78,  y2: 0
		  image2: template(colors[2])
	   ))}
	4: {linear_blend(
		# blend = 0.16
		image1: template(colors[0])
		x1: 0.15,  y1: 0
		x2: 0.31,  y2: 0
		image2: linear_blend(
		  image1: template(colors[1])
		  x1: 0.42,  y1: 0
		  x2: 0.58,  y2: 0
		  image2: linear_blend(
		    image1: template(colors[2])
		    x1: 0.69, y1: 0
		    x2: 0.85, y2: 0
		    image2: template(colors[3])
	   )))}
	5: {linear_blend(
		image1: template(colors[0])
		x1: 2.0 / 15,  y1: 0
		x2: 4.0 / 15,  y2: 0
		image2: linear_blend(
		  image1: template(colors[1])
		  x1: 5.0 / 15,  y1: 0
		  x2: 7.0 / 15,  y2: 0
		  image2: linear_blend(
		    image1: template(colors[2])
		    x1:  8.0 / 15,  y1: 0
		    x2: 10.0 / 15,  y2: 0
		    image2: linear_blend(
		      image1: template(colors[3])
		      x1: 11.0 / 15,  y1: 0
		      x2: 13.0 / 15,  y2: 0
		      image2: template(colors[4])
	   ))))}
	6: {linear_blend(
		image1: template(colors[0])
		x1: 1.5 / 15,  y1: 0
		x2: 3.1 / 15,  y2: 0
		image2: linear_blend(
		  image1: template(colors[1])
		  x1: 4.1 / 15,  y1: 0
		  x2: 5.7 / 15,  y2: 0
		  image2: linear_blend(
		    image1: template(colors[2])
		    x1: 6.7 / 15,  y1: 0
		    x2: 8.3 / 15,  y2: 0
		    image2: linear_blend(
		      image1: template(colors[3])
		      x1: 9.3 / 15,  y1: 0
		      x2: 10.9 / 15,  y2: 0
		      image2: linear_blend(
		        image1: template(colors[4])
		        x1: 11.9 / 15, y1: 0
		        x2: 13.5 / 15, y2: 0
		        image2: template(colors[5])
	   )))))}
	7: {linear_blend(
		image1: template(colors[0])
		x1: 1.3 / 15,  y1: 0
		x2: 2.7 / 15,  y2: 0
		image2: linear_blend(
		  image1: template(colors[1])
		  x1: 3.5 / 15,  y1: 0
		  x2: 4.9 / 15,  y2: 0
		  image2: linear_blend(
		    image1: template(colors[2])
		    x1: 5.7 / 15,  y1: 0
		    x2: 7.1 / 15,  y2: 0
		    image2: linear_blend(
		      image1: template(colors[3])
		      x1: 7.9 / 15,  y1: 0
		      x2: 9.3 / 15,  y2: 0
		      image2: linear_blend(
		        image1: template(colors[4])
		        x1: 10.1 / 15, y1: 0
		        x2: 11.5 / 15, y2: 0
		        image2: linear_blend(
		          image1: template(colors[5])
		          x1: 12.3 / 15, y1: 0
		          x2: 13.7 / 15, y2: 0
		          image2: template(colors[6])
	   ))))))}
]

card_hybrid := [
	radial: [
		0: { template("c") }
		1: { template(colors[0]) }
		2: card_hybrid_2
		3: {linear_blend(
			image1: card_hybrid_2(colors: colors[0] + colors[1]),
			image2: template(colors[2]),
			x1: 0,  y1: 0.55
			x2: 0,  y2: 0.77
		   )}
		4: {linear_blend(
			image1: card_hybrid_2(colors: colors[0] + colors[1])
			image2: card_hybrid_2(colors: colors[3] + colors[2])
			x1: 0,  y1: 0.4
			x2: 0,  y2: 0.62
		   )}
		5: {linear_blend(
			image1: linear_blend(
				image1: card_hybrid_2(colors: colors[0] + colors[1]),
				image2: card_hybrid_2(colors: colors[4] + colors[2]),
				x1: 0,  y1: 0.19
				x2: 0,  y2: 0.35
			),
			image2: template(colors[3]),
			x1: 0,  y1: 0.777
			x2: 0,  y2: 0.937
		   )}
		6: {linear_blend(
			image1: linear_blend(
				image1: card_hybrid_2(colors: colors[0] + colors[1]),
				image2: card_hybrid_2(colors: colors[5] + colors[2]),
				x1: 0,  y1: 0.19
				x2: 0,  y2: 0.35
			),
			image2: card_hybrid_2(colors: colors[4] + colors[3]),
			x1: 0,  y1: 0.777
			x2: 0,  y2: 0.937
		   )}
		7: {linear_blend(
			image1: linear_blend(
				image1: linear_blend(
					image1: card_hybrid_2(colors: colors[0] + colors[1]),
					image2: card_hybrid_2(colors: colors[6] + colors[3]),
					x1: 0,  y1: 0.34
					x2: 0,  y2: 0.50
				),
				image2: card_hybrid_2(colors: colors[5] + colors[3]),
				x1: 0,  y1: 0.877
				x2: 0,  y2: 0.937
			),
			image2: template(colors[4]),
			x1: 0,  y1: 1.140
			x2: 0,  y2: 1.300
		   )}
	]
	horizontal: horizontal_card_hybrid
	vertical: [
		1: { template(colors[0]) }
		2: { linear_blend(
			image1: template(colors[0])
			image2: template(colors[1])
			x1: 0,  y1: 0.4
			x2: 0,  y2: 0.6
		   )}
		3: vertical_card_hybrid
		4: vertical_card_hybrid
		5: vertical_card_hybrid
		6: vertical_card_hybrid
		7: vertical_card_hybrid
	]
	overlay: overlay_hybrid
]


########################################################################
# P/T box
########################################################################
# These are easier

horizontal_pt_hybrid := [
	1: { template(colors[0]) }
	2: { template(colors[1]) }
	3: { linear_blend(
		image1: template(colors[1])
		image2: template(colors[2])
		x1: -0.51, y1: 0
		x2:  0.26, y2: 0
	   )}
	4: { linear_blend(
		image1: template(colors[2])
		image2: template(colors[3])
		x1: -0.1,  y1: 0
		x2:  0.6,  y2: 0
	   )}
	5: { linear_blend(
		image1: template(colors[3])
		image2: template(colors[4])
		x1: 0.08,  y1: 0
		x2: 0.65,  y2: 0
	   )}
	6: { linear_blend(
		image1: template(colors[4])
		image2: template(colors[5])
		x1: 0.07, y1: 0
		x2: 0.7, y2: 0
	   )}
	7: {linear_blend(
		image1: linear_blend(
			image1: template(colors[4]),
			image2: template(colors[5]),
			x1: -0.2,  y1: 0
			x2: 0.2,  y2: 0
		),
		image2: template(colors[6]),
		x1: 0.5,  y1: 0
		x2: 0.7,  y2: 0
	   )}
]

pt_hybrid := [
	radial: [
		0: { template("c")       }
		1: { template(colors[0]) }
		2: { template(colors[1]) }
		3: { template(colors[2]) }
		4: { template(colors[2]) }
		5: { linear_blend(
			image1: template(colors[2])
			image2: template(colors[3])
			x1: 0, y1: -1.5
			x2: 0, y2: 0.7
		   )}
		6: { linear_blend(
			image1: template(colors[2])
			image2: template(colors[3])
			x1: 0, y1: -1.5
			x2: 0, y2: 0.7
		   )}
		7: { template(colors[4]) }
	]
	horizontal: horizontal_pt_hybrid
	vertical: [
		1: { template(colors[0]) }
		2: { template(colors[1]) }
		3: { template(colors[2]) }
		4: { template(colors[3]) }
		5: { template(colors[4]) }
		6: { template(colors[5]) }
		7: { template(colors[6]) }
	]
	overlay: overlay_hybrid
]

########################################################################
# P/T boxes of flip cards
########################################################################

flip_pt_hybrid := [
	radial: [
		0: { template("c")       }
		1: { template(colors[0]) }
		2: { template(colors[1]) }
		3: { template(colors[1]) }
		4: { template(colors[1]) }
		5: { linear_blend(
			image1: template(colors[1])
			image2: template(colors[2])
			x1: 0, y1: -1
			x2: 0, y2: 1.8
		   )}
		6: { linear_blend(
			image1: template(colors[1])
			image2: template(colors[2])
			x1: 0, y1: -1
			x2: 0, y2: 1.8
		   )}
		7: { template(colors[4]) }
	]
	horizontal: horizontal_pt_hybrid
	vertical: [
		1: { template(colors[0]) }
		2: { template(colors[0]) }
		3: { linear_blend(
			image1: template(colors[0])
			image2: template(colors[1])
			x1: 0, y1: 0
			x2: 0, y2: 2
		   )}
		4: { linear_blend(
			image1: template(colors[0])
			image2: template(colors[1])
			x1: 0, y1: -1.5
			x2: 0, y2: 1
		   )}
		5: { linear_blend(
			image1: template(colors[0])
			image2: template(colors[1])
			x1: 0, y1: -1.1
			x2: 0, y2: 0.2
		   )}
		6: { template(colors[1]) } # Probably not right
		7: { template(colors[2]) }
	]
	overlay: overlay_hybrid
]

flip_pt_hybrid2 := [
	radial: [
		0: { template("c")       }
		1: { template(colors[0]) }
		2: { template(colors[0]) }
		3: { linear_blend(
			image1: template(colors[0])
			image2: template(colors[2])
			x1: 0, y1: -1
			x2: 0, y2: 1.1
		   )}
		4: { template(colors[3]) }
		5: { template(colors[4]) }
		6: { template(colors[5]) }
		7: { template(colors[5]) }
	]
	horizontal: [
		1: { template(colors[0]) }
		2: { template(colors[0]) }
		3: { template(colors[0]) }
		4: { linear_blend(
			image1: template(colors[0])
			image2: template(colors[1])
			x1: 0.4,  y1: 0
			x2: 1.5,  y2: 0
		   )}
		5: { linear_blend(
			image1: template(colors[0])
			image2: template(colors[1])
			x1: 0.08,  y1: 0
			x2: 0.65,  y2: 0
		   )}
		6: { template(colors[5]) } #TODO
		7: { template(colors[6]) } #TODO
	]
	vertical: [
		1: { template(colors[0]) }
		2: { template(colors[1]) }
		3: { linear_blend(
			image1: template(colors[1])
			image2: template(colors[2])
			x1: 0, y1: -1
			x2: 0, y2: 1.5
		   )}
		4: { linear_blend(
			image1: template(colors[2])
			image2: template(colors[3])
			x1: 0, y1: 0.5
			x2: 0, y2: 3
		   )}
		5: { template(colors[3]) }
		6: { template(colors[5]) } # Probably not right
		7: { template(colors[6]) }
	]
	overlay: overlay_hybrid
]

########################################################################
# Textbox and typeline for FPM templates and Futureshifts
########################################################################

textbox_hybrid := [
	radial: [
		0: { template("c")       }
		1: { template(colors[0]) }
		2: card_hybrid_2
		3: { template(colors[2]) }
		4: { card_hybrid_2(colors: colors[3] + colors[2]) }
		5: { template(colors[3]) }
		6: { card_hybrid_2(colors: colors[4] + colors[3]) }
		7: { template(colors[4]) }
	]
	horizontal: horizontal_card_hybrid
	vertical:  [
		0: { template("c")       }
		1: { template(colors[0]) }
		2: { template(colors[1]) }
		3: { template(colors[2]) } # TODO
		4: { template(colors[3]) }
		5: { template(colors[4]) }
		6: { template(colors[5]) }
		7: { template(colors[6]) }
	]
	overlay: overlay_hybrid
]

typeline_hybrid := textbox_hybrid

########################################################################
# Putting it all together.
########################################################################

# Determine the card background based on the card_color multiple choice options
color_background := {
	
	# for thumbnails
	if input == "hybrid" then
		input := "white,blue,red,{hybrid_previews},horizontal"
	else if input == "overlay" then
		input := "blue,red,{hybrid_previews},overlay"
	else if input == "radial" or input == "horizontal" or input == "vertical" then
		input := "white,blue,red,{hybrid_previews}," + input
	else if input == "reversed" then
		input := "white,blue,red,{hybrid_previews},horizontal,reversed"
	
	# What type of 'hybrid'?
	land     := chosen(choice:"land")
	multi    := chosen(choice:"multicolor")
	hybrid   := chosen(choice:"hybrid")
	artifact := chosen(choice:"artifact")
	if land and colored_lands then template := land_template # use land template instead?
	
	# The selected colors
	colors := sort_text( order: "(wubrg)"
	                   , (if chosen(choice:"white") then "w")
	                   + (if chosen(choice:"blue")  then "u")
	                   + (if chosen(choice:"black") then "b")
	                   + (if chosen(choice:"red")   then "r")
	                   + (if chosen(choice:"green") then "g"))
	if multi and (hybrid or colors == "") then (
		colors := colors + "m"
		multi := false
	)
	if artifact and (hybrid or colors == "") then (
		colors := colors + "a"
		artifact := false
	)
	if chosen(choice:"reversed") then colors := reverse(colors)
	color_count := number_of_items(in: colors)
	if colors == "" then colors == "c"
	
	# 'shape' / type of hybrid
	shape := if      chosen(choice:"horizontal") then "horizontal"
	         else if chosen(choice:"vertical")   then "vertical"
	         else if chosen(choice:"overlay")    then "overlay"
	         else                                     "radial"
	
	# Determine background (allows styles to hook something else here)
	color_combination()
}

color_combination := {
	# The base hybrid, without the outer frame blended over it
	base := base_hybrid[shape][color_count]()
	
	# Put a frame around it?
	if land and not colored_lands then
		masked_blend(
			mask:  "multicolor_blend_{type}.png",
			dark:  land_template("c"),
			light: base,
		)
	else if land and multi and mask_multi_land_with_color() then
		masked_blend(
			mask:  "hybrid_blend_{type}.png",
			dark:  base,
			light:  land_template("m"),
		)
	else if multi and artifact then
		masked_blend(
			mask: "artifact_blend_{type}.png",
			dark: template("a"),
			light: masked_blend(
				mask: "multicolor_blend_{type}.png",
				dark: template("m"),
				light: base
			)
		)
	else if multi then 
		masked_blend(
			mask:  "multicolor_blend_{type}.png",
			dark:  template("m"),
			light: base,
		)
	else if artifact then 
		masked_blend(
			mask:  "artifact_blend_{type}.png",
			dark:  template("a"),
			light: base,
		)
	else if color_count > 1 and mask_hybrid_with_land() then
		masked_blend(
			mask:  "hybrid_blend_{type}.png",
			dark:  land_template("c"),
			light: base,
		)
	else base
}

########################################################################
# Specific types
########################################################################

card_background  := { color_background(type:"card",     base_hybrid:card_hybrid) }
card_ptbox       := { color_background(type:"pt",       base_hybrid<img src="/smile/tongue.gif" title="Stick out your tongue" alt="Stick out your tongue" />t_hybrid) }
flip_ptbox       := { color_background(type:"pt",       base_hybrid:flip_pt_hybrid) }
flip_ptbox2      := { color_background(type:"pt2",      base_hybrid:flip_pt_hybrid2) }
card_textbox     := { color_background(type:"textbox",  base_hybrid:textbox_hybrid) }
card_typeline    := { color_background(type:"typeline", base_hybrid:typeline_hybrid) }

########################################################################
# Font colors
########################################################################

# For which colors is the font white?
font_colors_white := { input == "b" or input == "l" }

font_color_positions := [
	radial:     [0,0,0,2,3,3,4,4]
	horizontal: [0,0,0,0,0,0,0,0]
	vertical:   [0,0,1,2,3,4,5,6]
	overlay:    [0,0,0,0,0,0,0,0]
]

# Determine whether light or dark fonts should be used
font_white := {
	hybrid   := chosen(choice:"hybrid")
	artifact := chosen(choice:"artifact")
	colors := sort_text( order: "(wubrg)"
		           , (if chosen(choice:"white") then "w")
		           + (if chosen(choice:"blue")  then "u")
		           + (if chosen(choice:"black") then "b")
		           + (if chosen(choice:"red")   then "r")
		           + (if chosen(choice:"green") then "g"))
		           + (if artifact               then "a")
	font_colors_white(
		if chosen(choice:"land") then "l"
		else if input == "artifact, multicolor" then "a"
		else if chosen(choice:"multicolor")     then "m"
		else if artifact and not hybrid         then "a"
		else if colors == ""                    then "c"
		else colors[
			font_color_positions[
				if      chosen(choice:"horizontal") then "horizontal"
				else if chosen(choice:"vertical")   then "vertical"
				else if chosen(choice:"overlay")    then "overlay"
				else                                     "radial"
			][number_of_items(in: colors)]
		]
	)
}

font_color := { if font_white() then rgb(255,255,255) else rgb(0,0,0) }

That by the way is the script that makes all hybrids possible...

Wed, 2009-11-04 02:49
Shiv2503
Shiv2503's picture

Although to be fair there

Although to be fair there are other things in there too.

Wed, 2009-11-04 03:01
Art_Freak
Template Developer
Art_Freak's picture

@Shiv: I don't follow your

@Shiv: I don't think I follow what you're saying.
Edit: NM. I think I know what you're referring to. The other things in there are other blend scripts, and they are minimal compared to what's there for hybrids. I didn't feel like picking out the little parts for the sake of an example.

Edit 2: Although it really isn't relevant, I'd hate for anyone to think I was bolstering a faulty argument, here's the hybrid script sans the "other things".

Spoiler:
# Scripts for blending images
# Included by a style file in its init script


########################################################################
# Filenames and other defaults
########################################################################

mask_hybrid_with_land	:= { false }
mask_multi_land_with_color	:= { false }
template		:= { input + "{type}.jpg" }
land_template		:= { (if input == "a" then "c" else input) + "l{type}.jpg" }
# For what value should thumbnails of hybrids be made?
hybrid_previews         := "hybrid"
# Are there templates for colored lands, land_template(...)?
colored_lands           := true

########################################################################
# Combining multiple colors (hybrids)
########################################################################

card_hybrid_2 := {
	linear_blend(
		image1: template(colors[0])
		image2: template(colors[1])
		x1: 0.4,  y1: 0
		x2: 0.6,  y2: 0
	)
}

overlay_hybrid := [
	1: { template(colors[0]) }
	2: { combine_blend(
		image1: template(colors[0]),
		image2: template(colors[1]),
		combine: "symmetric overlay"
	   )}
]

# vertical version of a horizontal hybrid
vertical_card_hybrid := {
	do_linear_blend := linear_blend
	linear_blend := { do_linear_blend(x1: 0, x2: 0, y1: x1, y2: x2) }
	card_hybrid.horizontal[color_count]()
}

horizontal_card_hybrid := [
	1: { template(colors[0]) }
	2: card_hybrid_2
	3: {linear_blend(
		image1: template(colors[0])
		x1: 0.22,  y1: 0
		x2: 0.4,   y2: 0
		image2: linear_blend(
		  image1: template(colors[1])
		  x1: 0.6,   y1: 0
		  x2: 0.78,  y2: 0
		  image2: template(colors[2])
	   ))}
	4: {linear_blend(
		# blend = 0.16
		image1: template(colors[0])
		x1: 0.15,  y1: 0
		x2: 0.31,  y2: 0
		image2: linear_blend(
		  image1: template(colors[1])
		  x1: 0.42,  y1: 0
		  x2: 0.58,  y2: 0
		  image2: linear_blend(
		    image1: template(colors[2])
		    x1: 0.69, y1: 0
		    x2: 0.85, y2: 0
		    image2: template(colors[3])
	   )))}
	5: {linear_blend(
		image1: template(colors[0])
		x1: 2.0 / 15,  y1: 0
		x2: 4.0 / 15,  y2: 0
		image2: linear_blend(
		  image1: template(colors[1])
		  x1: 5.0 / 15,  y1: 0
		  x2: 7.0 / 15,  y2: 0
		  image2: linear_blend(
		    image1: template(colors[2])
		    x1:  8.0 / 15,  y1: 0
		    x2: 10.0 / 15,  y2: 0
		    image2: linear_blend(
		      image1: template(colors[3])
		      x1: 11.0 / 15,  y1: 0
		      x2: 13.0 / 15,  y2: 0
		      image2: template(colors[4])
	   ))))}
	6: {linear_blend(
		image1: template(colors[0])
		x1: 1.5 / 15,  y1: 0
		x2: 3.1 / 15,  y2: 0
		image2: linear_blend(
		  image1: template(colors[1])
		  x1: 4.1 / 15,  y1: 0
		  x2: 5.7 / 15,  y2: 0
		  image2: linear_blend(
		    image1: template(colors[2])
		    x1: 6.7 / 15,  y1: 0
		    x2: 8.3 / 15,  y2: 0
		    image2: linear_blend(
		      image1: template(colors[3])
		      x1: 9.3 / 15,  y1: 0
		      x2: 10.9 / 15,  y2: 0
		      image2: linear_blend(
		        image1: template(colors[4])
		        x1: 11.9 / 15, y1: 0
		        x2: 13.5 / 15, y2: 0
		        image2: template(colors[5])
	   )))))}
	7: {linear_blend(
		image1: template(colors[0])
		x1: 1.3 / 15,  y1: 0
		x2: 2.7 / 15,  y2: 0
		image2: linear_blend(
		  image1: template(colors[1])
		  x1: 3.5 / 15,  y1: 0
		  x2: 4.9 / 15,  y2: 0
		  image2: linear_blend(
		    image1: template(colors[2])
		    x1: 5.7 / 15,  y1: 0
		    x2: 7.1 / 15,  y2: 0
		    image2: linear_blend(
		      image1: template(colors[3])
		      x1: 7.9 / 15,  y1: 0
		      x2: 9.3 / 15,  y2: 0
		      image2: linear_blend(
		        image1: template(colors[4])
		        x1: 10.1 / 15, y1: 0
		        x2: 11.5 / 15, y2: 0
		        image2: linear_blend(
		          image1: template(colors[5])
		          x1: 12.3 / 15, y1: 0
		          x2: 13.7 / 15, y2: 0
		          image2: template(colors[6])
	   ))))))}
]

card_hybrid := [
	radial: [
		0: { template("c") }
		1: { template(colors[0]) }
		2: card_hybrid_2
		3: {linear_blend(
			image1: card_hybrid_2(colors: colors[0] + colors[1]),
			image2: template(colors[2]),
			x1: 0,  y1: 0.55
			x2: 0,  y2: 0.77
		   )}
		4: {linear_blend(
			image1: card_hybrid_2(colors: colors[0] + colors[1])
			image2: card_hybrid_2(colors: colors[3] + colors[2])
			x1: 0,  y1: 0.4
			x2: 0,  y2: 0.62
		   )}
		5: {linear_blend(
			image1: linear_blend(
				image1: card_hybrid_2(colors: colors[0] + colors[1]),
				image2: card_hybrid_2(colors: colors[4] + colors[2]),
				x1: 0,  y1: 0.19
				x2: 0,  y2: 0.35
			),
			image2: template(colors[3]),
			x1: 0,  y1: 0.777
			x2: 0,  y2: 0.937
		   )}
		6: {linear_blend(
			image1: linear_blend(
				image1: card_hybrid_2(colors: colors[0] + colors[1]),
				image2: card_hybrid_2(colors: colors[5] + colors[2]),
				x1: 0,  y1: 0.19
				x2: 0,  y2: 0.35
			),
			image2: card_hybrid_2(colors: colors[4] + colors[3]),
			x1: 0,  y1: 0.777
			x2: 0,  y2: 0.937
		   )}
		7: {linear_blend(
			image1: linear_blend(
				image1: linear_blend(
					image1: card_hybrid_2(colors: colors[0] + colors[1]),
					image2: card_hybrid_2(colors: colors[6] + colors[3]),
					x1: 0,  y1: 0.34
					x2: 0,  y2: 0.50
				),
				image2: card_hybrid_2(colors: colors[5] + colors[3]),
				x1: 0,  y1: 0.877
				x2: 0,  y2: 0.937
			),
			image2: template(colors[4]),
			x1: 0,  y1: 1.140
			x2: 0,  y2: 1.300
		   )}
	]
	horizontal: horizontal_card_hybrid
	vertical: [
		1: { template(colors[0]) }
		2: { linear_blend(
			image1: template(colors[0])
			image2: template(colors[1])
			x1: 0,  y1: 0.4
			x2: 0,  y2: 0.6
		   )}
		3: vertical_card_hybrid
		4: vertical_card_hybrid
		5: vertical_card_hybrid
		6: vertical_card_hybrid
		7: vertical_card_hybrid
	]
	overlay: overlay_hybrid
]


########################################################################
# P/T box
########################################################################
# These are easier

horizontal_pt_hybrid := [
	1: { template(colors[0]) }
	2: { template(colors[1]) }
	3: { linear_blend(
		image1: template(colors[1])
		image2: template(colors[2])
		x1: -0.51, y1: 0
		x2:  0.26, y2: 0
	   )}
	4: { linear_blend(
		image1: template(colors[2])
		image2: template(colors[3])
		x1: -0.1,  y1: 0
		x2:  0.6,  y2: 0
	   )}
	5: { linear_blend(
		image1: template(colors[3])
		image2: template(colors[4])
		x1: 0.08,  y1: 0
		x2: 0.65,  y2: 0
	   )}
	6: { linear_blend(
		image1: template(colors[4])
		image2: template(colors[5])
		x1: 0.07, y1: 0
		x2: 0.7, y2: 0
	   )}
	7: {linear_blend(
		image1: linear_blend(
			image1: template(colors[4]),
			image2: template(colors[5]),
			x1: -0.2,  y1: 0
			x2: 0.2,  y2: 0
		),
		image2: template(colors[6]),
		x1: 0.5,  y1: 0
		x2: 0.7,  y2: 0
	   )}
]

pt_hybrid := [
	radial: [
		0: { template("c")       }
		1: { template(colors[0]) }
		2: { template(colors[1]) }
		3: { template(colors[2]) }
		4: { template(colors[2]) }
		5: { linear_blend(
			image1: template(colors[2])
			image2: template(colors[3])
			x1: 0, y1: -1.5
			x2: 0, y2: 0.7
		   )}
		6: { linear_blend(
			image1: template(colors[2])
			image2: template(colors[3])
			x1: 0, y1: -1.5
			x2: 0, y2: 0.7
		   )}
		7: { template(colors[4]) }
	]
	horizontal: horizontal_pt_hybrid
	vertical: [
		1: { template(colors[0]) }
		2: { template(colors[1]) }
		3: { template(colors[2]) }
		4: { template(colors[3]) }
		5: { template(colors[4]) }
		6: { template(colors[5]) }
		7: { template(colors[6]) }
	]
	overlay: overlay_hybrid
]

########################################################################
# P/T boxes of flip cards
########################################################################

flip_pt_hybrid := [
	radial: [
		0: { template("c")       }
		1: { template(colors[0]) }
		2: { template(colors[1]) }
		3: { template(colors[1]) }
		4: { template(colors[1]) }
		5: { linear_blend(
			image1: template(colors[1])
			image2: template(colors[2])
			x1: 0, y1: -1
			x2: 0, y2: 1.8
		   )}
		6: { linear_blend(
			image1: template(colors[1])
			image2: template(colors[2])
			x1: 0, y1: -1
			x2: 0, y2: 1.8
		   )}
		7: { template(colors[4]) }
	]
	horizontal: horizontal_pt_hybrid
	vertical: [
		1: { template(colors[0]) }
		2: { template(colors[0]) }
		3: { linear_blend(
			image1: template(colors[0])
			image2: template(colors[1])
			x1: 0, y1: 0
			x2: 0, y2: 2
		   )}
		4: { linear_blend(
			image1: template(colors[0])
			image2: template(colors[1])
			x1: 0, y1: -1.5
			x2: 0, y2: 1
		   )}
		5: { linear_blend(
			image1: template(colors[0])
			image2: template(colors[1])
			x1: 0, y1: -1.1
			x2: 0, y2: 0.2
		   )}
		6: { template(colors[1]) } # Probably not right
		7: { template(colors[2]) }
	]
	overlay: overlay_hybrid
]

flip_pt_hybrid2 := [
	radial: [
		0: { template("c")       }
		1: { template(colors[0]) }
		2: { template(colors[0]) }
		3: { linear_blend(
			image1: template(colors[0])
			image2: template(colors[2])
			x1: 0, y1: -1
			x2: 0, y2: 1.1
		   )}
		4: { template(colors[3]) }
		5: { template(colors[4]) }
		6: { template(colors[5]) }
		7: { template(colors[5]) }
	]
	horizontal: [
		1: { template(colors[0]) }
		2: { template(colors[0]) }
		3: { template(colors[0]) }
		4: { linear_blend(
			image1: template(colors[0])
			image2: template(colors[1])
			x1: 0.4,  y1: 0
			x2: 1.5,  y2: 0
		   )}
		5: { linear_blend(
			image1: template(colors[0])
			image2: template(colors[1])
			x1: 0.08,  y1: 0
			x2: 0.65,  y2: 0
		   )}
		6: { template(colors[5]) } #TODO
		7: { template(colors[6]) } #TODO
	]
	vertical: [
		1: { template(colors[0]) }
		2: { template(colors[1]) }
		3: { linear_blend(
			image1: template(colors[1])
			image2: template(colors[2])
			x1: 0, y1: -1
			x2: 0, y2: 1.5
		   )}
		4: { linear_blend(
			image1: template(colors[2])
			image2: template(colors[3])
			x1: 0, y1: 0.5
			x2: 0, y2: 3
		   )}
		5: { template(colors[3]) }
		6: { template(colors[5]) } # Probably not right
		7: { template(colors[6]) }
	]
	overlay: overlay_hybrid
]

########################################################################
# Textbox and typeline for FPM templates and Futureshifts
########################################################################

textbox_hybrid := [
	radial: [
		0: { template("c")       }
		1: { template(colors[0]) }
		2: card_hybrid_2
		3: { template(colors[2]) }
		4: { card_hybrid_2(colors: colors[3] + colors[2]) }
		5: { template(colors[3]) }
		6: { card_hybrid_2(colors: colors[4] + colors[3]) }
		7: { template(colors[4]) }
	]
	horizontal: horizontal_card_hybrid
	vertical:  [
		0: { template("c")       }
		1: { template(colors[0]) }
		2: { template(colors[1]) }
		3: { template(colors[2]) } # TODO
		4: { template(colors[3]) }
		5: { template(colors[4]) }
		6: { template(colors[5]) }
		7: { template(colors[6]) }
	]
	overlay: overlay_hybrid
]

typeline_hybrid := textbox_hybrid

########################################################################
# Putting it all together.
########################################################################

# Determine the card background based on the card_color multiple choice options
color_background := {
	
	# for thumbnails
	if input == "hybrid" then
		input := "white,blue,red,{hybrid_previews},horizontal"
	else if input == "overlay" then
		input := "blue,red,{hybrid_previews},overlay"
	else if input == "radial" or input == "horizontal" or input == "vertical" then
		input := "white,blue,red,{hybrid_previews}," + input
	else if input == "reversed" then
		input := "white,blue,red,{hybrid_previews},horizontal,reversed"
	
	# What type of 'hybrid'?
	land     := chosen(choice:"land")
	multi    := chosen(choice:"multicolor")
	hybrid   := chosen(choice:"hybrid")
	artifact := chosen(choice:"artifact")
	if land and colored_lands then template := land_template # use land template instead?
	
	# The selected colors
	colors := sort_text( order: "(wubrg)"
	                   , (if chosen(choice:"white") then "w")
	                   + (if chosen(choice:"blue")  then "u")
	                   + (if chosen(choice:"black") then "b")
	                   + (if chosen(choice:"red")   then "r")
	                   + (if chosen(choice:"green") then "g"))
	if multi and (hybrid or colors == "") then (
		colors := colors + "m"
		multi := false
	)
	if artifact and (hybrid or colors == "") then (
		colors := colors + "a"
		artifact := false
	)
	if chosen(choice:"reversed") then colors := reverse(colors)
	color_count := number_of_items(in: colors)
	if colors == "" then colors == "c"
	
	# 'shape' / type of hybrid
	shape := if      chosen(choice:"horizontal") then "horizontal"
	         else if chosen(choice:"vertical")   then "vertical"
	         else if chosen(choice:"overlay")    then "overlay"
	         else                                     "radial"
	
	# Determine background (allows styles to hook something else here)
	color_combination()
}

color_combination := {
	# The base hybrid, without the outer frame blended over it
	base := base_hybrid[shape][color_count]()
	
	# Put a frame around it?
	if land and not colored_lands then
		masked_blend(
			mask:  "multicolor_blend_{type}.png",
			dark:  land_template("c"),
			light: base,
		)
	else if land and multi and mask_multi_land_with_color() then
		masked_blend(
			mask:  "hybrid_blend_{type}.png",
			dark:  base,
			light:  land_template("m"),
		)
	else if multi and artifact then
		masked_blend(
			mask: "artifact_blend_{type}.png",
			dark: template("a"),
			light: masked_blend(
				mask: "multicolor_blend_{type}.png",
				dark: template("m"),
				light: base
			)
		)
	else if multi then 
		masked_blend(
			mask:  "multicolor_blend_{type}.png",
			dark:  template("m"),
			light: base,
		)
	else if artifact then 
		masked_blend(
			mask:  "artifact_blend_{type}.png",
			dark:  template("a"),
			light: base,
		)
	else if color_count > 1 and mask_hybrid_with_land() then
		masked_blend(
			mask:  "hybrid_blend_{type}.png",
			dark:  land_template("c"),
			light: base,
		)
	else base
}

########################################################################
# Specific types
########################################################################

card_background  := { color_background(type:"card",     base_hybrid:card_hybrid) }
card_ptbox       := { color_background(type:"pt",       base_hybrid<img src="/smile/tongue.gif" title="Stick out your tongue" alt="Stick out your tongue" />t_hybrid) }
flip_ptbox       := { color_background(type:"pt",       base_hybrid:flip_pt_hybrid) }
flip_ptbox2      := { color_background(type:"pt2",      base_hybrid:flip_pt_hybrid2) }
card_textbox     := { color_background(type:"textbox",  base_hybrid:textbox_hybrid) }
card_typeline    := { color_background(type:"typeline", base_hybrid:typeline_hybrid) }

Wed, 2009-11-04 03:27
Shiv2503
Shiv2503's picture

Yeah I know that it doesn't

Yeah I know that it doesn't really matter but I'd hate for someone for some reason to try and figure out how to do hybrids and assume that all that was in there was hybrids (yes I know that that would probably not happen and if it did they would have no idea what the heck it all meant.)

Also Just for anybody wondering that spoiler right above me contains 73 lines of code and 1026 characters.

Wed, 2009-11-04 03:31
Art_Freak
Template Developer
Art_Freak's picture

Shiv2503 wrote:Also Just for

Shiv2503 wrote:
Also Just for anybody wondering that spoiler right above me contains 73 lines of code and 1026 characters.

LOL, just a couple more lines than would fit on the average card!

This is what I'm getting at though, the intention is not to have entire or really even partial scripts on cards. The cards should only pay homage to or represent a script or other template element.

Wed, 2009-11-04 03:42
ocb777
ocb777's picture

*sigh*

And were right back (basically) to where we were before the elections.

Bickering and self fluffing.

I may have added to it with my comment about coding, if so I appologize.

Lets all shut up, let A_F, ATW and SMR get their p and qs in order and let them LEAD the project, instead of being led by it (wich from what I can see is the current case.)

Let them figure out whats going on and then ask US for input. and I stand by that if the time in here arguing and griping was spent on templates we'd have every ccg templated by week's end. Big smile

-------------------------------
Edit: this includes my griping about the griping which took dozens of keystrokes that could have been spent on my mad updated wow template.

My fan sets and lots of other stuff I've done: Click Here!

Wed, 2009-11-04 03:58
Art_Freak
Template Developer
Art_Freak's picture

Yeah... in regards to that,

Yeah... in regards to that, I still haven't had any luck getting ahold of smr1313. My email to him just came back as a failure to deliver, so unless he comes in on his own, then Idle Muse might have him pegged. Also, the next leader in line since Idle bowed out is Jeske if he's willing.

Also, I did ask for everyone's opinion, and they've been giving it which has led to debate (which is good.) so I don't really consider that being led by the project...

What we have so far:
Game about templating: 2 votes
Game about set making: 3 votes

There's mixed opinions about the inclusion of code, but overall it's pretty clear that in some element it will be at the very least referenced (you may not see "if then else" statements on your cards, but you will see cards like "Add Hybrids" or "Add Styling Options").

Ideas for gameplay:

Art_Freak wrote:
The win cons would be 1) A completed template/set or 2) Decking (the opponent has run out of ideas). The card types would be: If template: script, set field, card field, style, and symbol; If set: concept, creator, design, art, and time.
Basically you'd start the game with a deck and 10 "community interest points". Each card played would cost points but also provided more points based on it's effect (easier to play = fewer points, harder to play = more points). Cards could also be played that affect your opponent's interest pool so that as your project gains momentum, their project loses it.

Jeske wrote:
For example, Card additions are card phenotypes that are commonly added to sets (such as counter/negation cards, beatsticks, etc.), Rules addendums are alterations to the rules (which can add to or subtract from a player's banked amount), Publicity means to try to reach new players (maybe starting with a small payment of banked points to secure a continual effect?), etc.

Consolidation of the above:
Win cons: 1) A completed template/set or 2) Decking (the opponent has run out of ideas).
Card types: Card Additions, Rules Addendums, Publicity, Concept, Creator, Design, Art, and Time (ALL of these can be removed/replaced, they've just been thrown out there)
Method of play: Interest Pool that acts as life and mana and is affected by cards played by both players.

What we need now:
We need to flesh out the rules so that we know what has to appear on cards so that templating and play testing can begin. We need a solid set of card types, a solid amount of starting interest points, turn structure, deck size, and any other elements of interest. So far the cards look like they'd have 4-6 fields (Name, Cost, Type, Rules Text, Flavor Text?, & Art?)

Wed, 2009-11-04 04:21
windandfire
windandfire's picture

I can't help but start to

I can't help but start to think that we could include equal ammounts of both templating and set design in the game. I was mainly worried about how much knowledge the user would be expected to know if we went with the templating route, but seeing the "hybrid cards" example, I think we could do something like the following. Imagine you're running a deck of this game that pays homage to the time spiral block design. Here's a card you might use:

Homage - <Cost>
Concept
At the start of your turn, you may have your interest pool become equal to the number of Concept and Art cards in your used-ideas (graveyard) pile.
Words of the wise: Don't overlook the old fans.

Somewhere along the line, your opponent may pull something tricky such as:

Tribal - <Cost>
Theme
When you play Tribal, add 5 interest points to your interest pool. Whenever another card named Tribal is played, it's controler loses 10 interest points.
Imagine Lorwyn right after Onslaught... Not a pretty sight.

... and he take the lead. But right as he's about to win, you play your backup plan:

Futureshift Frames - <Cost>
Template
You gain 5 interest points. If Futureshift Frames is the only nonbasic Template, you gain 10 interest points instead.
They didn't see that coming.

I think if we bring together the templating and set designs, we'll have a much more realistic mimicry of how Wizards goes at it. And it'll make for a much more dynamic game where you can balance both themes much like creatures vs spells in Magic. Besides, I don't think we have enough people developing templates for their own sets. Maybe this can inspire to that end.

So you can change my vote to "both" (or .5 and .5 if you'd prefer), Art_Freak.

For future looking into, we'd definatly need something players can grow and attack other than the interest pool. Maybe some "Angry Fans" cards or "Powerlevel Restrictions: Vintage" ones.

"I will do science to it." - Kimiko “Thunderbolt” Ross
"I can wire anything directly into anything - I'm the professor!" - Professor Hubert J. Farnsworth
"Our tanks can't hold aggro of that magnitude!

Wed, 2009-11-04 06:47
Jéské Couriano
Jéské Couriano's picture

When the vote was held, I

When the vote was held, I was certainly up for it. However, recent circumstances mean that I can't take it on. Sorry.

I also create custom D&D material!

Sets:
SSB (predesign)
Jargon File (design)
Echoes Block [Echoes of Past and Present, Anthrologies, Trinity's Heartsease] (design)
Mother (design)

Wed, 2009-11-04 20:59
Art_Freak
Template Developer
Art_Freak's picture

@windandfire: I really like

@windandfire: I really like what you've shown, and I think it really shows off a great gameplay scenario. With your new stance on things that gives coding being represented a clear majority, so I think we should move on and consider that issue settled.

@copapoc: With Jeske bowing out you're the last runner up. If you're willing just say so, if not it's ok.

@ALL: Giving this some thought today it ocurred to me that it's likely cards will affect an opponent's interest pool often enough that it would make sense to create a secondary field that acts as a negative/bonus to the opponent's pool rather than having each card say something like "Each opponent loses X interest points." Visually I think each card would have two numbers either side by side like a PT box on MTG cards or in separate fields like on Vanguard cards.

Wed, 2009-11-04 21:35
copapoc
copapoc's picture

hy ! of course i am ^^ i

hy ! of course i am ^^
i just was like verry sick and just followed the tread as it goes along. i repliedd to some others but tha was just beacuse of the facts that those replies usualy where like 5-6 rules or copy+paste stuff
had the "sweinenflue". still suffering but alright !

now my replies on evrything (now that i am willing to type ^^)

- i say do setmaking. importing the templating is alright by me, as long as i doesn't overrule the set desing. that's the what the forum does too!

- i stand behind coding (srry jéske) but as long as it is "understandable" meaning, the rest , the non-templater understand wath you are telling and we can "learn" templating by the game. this being mostly in flavor ofcourse ^^

- omph ! all of the above was already solved XD

- but if your "intrest pool works as your life ... then no intrest is game over ? couse i can see someon playing that fancy "hybrid"-card above, then using his 4 intrest points , ending without. is he dead or not ? cause the next turn he wil ge intrest agian, so his set wasn't dead ... it was "put on a hold", if you get where i'm going ?

- to the list give above i would love to add some ( Card Additions, Rules Addendums, Publicity, Concept, Creator, Design, Art, and Time ) + comments ? they sometimes make or brake a set (especialy those of monkechewytoy Stick out your tongue) + moderators ? (they can eliminate cards without crediting ?) + the "game's" we have around here ? like the "you fix the card"-thread. it oftens inspires me to make a sertain card ... or more

to en this (by my doing) packed message i say "i will contribute in the future, leader art_freak, a tactical waffle (and smr1313?) (ps: art_freak, your avatar scared the sh*t outa me , i watched i up close for the first time *shivers*, but no offense ^^)

alive and kicking relics of alara

Wed, 2009-11-04 21:56
A Tactical Waffle
A Tactical Waffle's picture

hmm... Possibly your "life"

hmm... Possibly your "life" wouldn't be the interest points, but something else....

I will have to give some thought on this.

Through enough goblins at any problem and it should go away. At the very least, there'll be fewer goblins.

Wed, 2009-11-04 22:23
Art_Freak
Template Developer
Art_Freak's picture

@copapoc: That's true. It

@copapoc: That's true. It would be a very brief game if you started with 10 interest, played two 4 cost cards and had an opponent on their first turn force you to lose 2 interest. Maybe the only real wincon in a set creation game should be completing a set? If this is the case, a deck could be very small and feature only 1 copy of each card, making even a very low card count deck (20 for argument's sake) possible and when you deck out, just shuffle and replace. *Note: Not every card in a deck would have to be used to win, we just still need a minimum number of cards in a deck.

Also, if the only win con is finishing a set then we could have actual "Set" cards that featured stipulations as to what the requirements for completing them would be and would be used like a Vanguard card would in MTG. These cards could also feature what your starting interest is and any static effect that will affect you. I'll use the following as an example:

Quote:
NAME: Ravnica
STARTING INT: 10
TYPE: Set - Magic: The Gathering
RULES: At the beginning of each turn, add 1 interest point to your interest pool for each Concept card you control with "Guild" in its name.
You win if you control "Hybrid Cards", "Multicolor Cards", "Storyline: Ravnica".

While I'm brainstorming, I'd like to suggest the card types be:
Set (A Vanguard-like card that outlines starting interest points, win cons, etc.)
Concept (This would include storylines, characters, locations, etc.)
Rules Addendum (This would be keywords, new game elements such as hybrid mana costs, a new subtype such as Arcane or Trap, etc.)
Designer (This would represent forum members and their potential feedback on a set or something they would bring to the table.)
Design Element (This would include things like hybrid cards, watermarks, artwork, versions, etc.)

Just trying to narrow the card types and what they should cover. How does it sound?

Wed, 2009-11-04 22:27
Jéské Couriano
Jéské Couriano's picture

Quote:hmm... Possibly your

Quote:
hmm... Possibly your "life" wouldn't be the interest points, but something else....

I think a game like this would be better as a banking/countup game, not a countdown game.

EDIT) Art_Freak) Sounds like an idea.

I also create custom D&D material!

Sets:
SSB (predesign)
Jargon File (design)
Echoes Block [Echoes of Past and Present, Anthrologies, Trinity's Heartsease] (design)
Mother (design)

Thu, 2009-11-05 00:16
windandfire
windandfire's picture

Art_freak, I really like

Art_freak, I really like that idea. I just learned to play a stand alone card game called "Brains" (I think, it's zombie based) where the win conditions are actually cards that define what you need to win, and playing a new one overrides the previous ones. Something along those lines, only probably separate for each player.

"I will do science to it." - Kimiko “Thunderbolt” Ross
"I can wire anything directly into anything - I'm the professor!" - Professor Hubert J. Farnsworth
"Our tanks can't hold aggro of that magnitude!

Thu, 2009-11-05 05:21
Shiv2503
Shiv2503's picture

Another game like that is

Another game like that is Fluxx.

Thu, 2009-11-05 05:49
windandfire
windandfire's picture

Actually, that was it. I

Actually, that was it. I forgot the name had very little to do with zombies.

"I will do science to it." - Kimiko “Thunderbolt” Ross
"I can wire anything directly into anything - I'm the professor!" - Professor Hubert J. Farnsworth
"Our tanks can't hold aggro of that magnitude!

Thu, 2009-11-05 11:56
copapoc
copapoc's picture

maybe play with a single

maybe play with a single deck ?
like having the 2 players draw cards from the same deck ?

alive and kicking relics of alara

Thu, 2009-11-05 22:25
Jéské Couriano
Jéské Couriano's picture

I don't think we should be

I don't think we should be trying to ape any existing card game *too* much, else it becomes a variant of that game.

I also create custom D&D material!

Sets:
SSB (predesign)
Jargon File (design)
Echoes Block [Echoes of Past and Present, Anthrologies, Trinity's Heartsease] (design)
Mother (design)

Thu, 2009-11-05 23:04
A Tactical Waffle
A Tactical Waffle's picture

Quote:Posted by

Quote:
Posted by Art_Freak:
@copapoc: That's true. It would be a very brief game if you started with 10 interest, played two 4 cost cards and had an opponent on their first turn force you to lose 2 interest. Maybe the only real wincon in a set creation game should be completing a set? If this is the case, a deck could be very small and feature only 1 copy of each card, making even a very low card count deck (20 for argument's sake) possible and when you deck out, just shuffle and replace. *Note: Not every card in a deck would have to be used to win, we just still need a minimum number of cards in a deck.

Also, if the only win con is finishing a set then we could have actual "Set" cards that featured stipulations as to what the requirements for completing them would be and would be used like a Vanguard card would in MTG. These cards could also feature what your starting interest is and any static effect that will affect you. I'll use the following as an example:

Quote:
NAME: Ravnica
STARTING INT: 10
TYPE: Set - Magic: The Gathering
RULES: At the beginning of each turn, add 1 interest point to your interest pool for each Concept card you control with "Guild" in its name.
You win if you control "Hybrid Cards", "Multicolor Cards", "Storyline: Ravnica".

While I'm brainstorming, I'd like to suggest the card types be:
Set (A Vanguard-like card that outlines starting interest points, win cons, etc.)
Concept (This would include storylines, characters, locations, etc.)
Rules Addendum (This would be keywords, new game elements such as hybrid mana costs, a new subtype such as Arcane or Trap, etc.)
Designer (This would represent forum members and their potential feedback on a set or something they would bring to the table.)
Design Element (This would include things like hybrid cards, watermarks, artwork, versions, etc.)

Just trying to narrow the card types and what they should cover. How does it sound?


I like it! I also feel like I haven't participated enough when I am one of the leaders.

How about each player chooses a set before the game starts, and that set that each player has will change some of the rules. We could make these cards based off of any set, existing mtg sets or even sets made using MSE, like "Taint" Something like this:

Quote:
NAME: Taint
TYPE: Set - MSE
RULES: At the end of your turn, add 2 interest points to your interest pool for each card you control that has "Poison" in it's name or Rules text.

Well, I don't really like the card I just made, but you get the point.

Through enough goblins at any problem and it should go away. At the very least, there'll be fewer goblins.

Thu, 2009-11-05 23:30
Jéské Couriano
Jéské Couriano's picture

If that's the case, we could

If that's the case, we could also add cards that force players to change their set on the fly or symbolizes complications, like so.

Quote:
NAME: Too Soon
TYPE: Design Element
RULES: One player replaces his Set card with another one he owns.

I also create custom D&D material!

Sets:
SSB (predesign)
Jargon File (design)
Echoes Block [Echoes of Past and Present, Anthrologies, Trinity's Heartsease] (design)
Mother (design)

Fri, 2009-11-06 20:11
AlexKOJ
AlexKOJ's picture

I really like the "set

I really like the "set building" idea. I had an idea like this, but it had to do with creating a story, where you needed to play cards that represented the different parts of a story: exposition, rising action, climax, falling action, and resolution. Each part of the story had certain effects and a specific requirement for you to fulfill before being able to proceed to the next part of the story. There'd also be plot twists to switch up how a player's story was going, characters (protagonists and antagonists) for the story to help you progress through your story or get in the way of your opponent's story, and cards or abilities that allowed you to skip a part of the storyline just like some stories do. I never really got this idea to go anywhere, by I thought it was pretty nifty, and just thought I'd share it because the set building idea is pretty similar to this and brought it back to my attention. I'm not saying to use it as the premise for the community game; I'm just letting you guys know what's going on in my head. I also had a variant of my game called "Trilogy Run" where after the first story was finished, your main characters and any cards attached to them and status changes they had would carry over and you'd start a new story, and after that story was finished, do it again. Sort of a marathon game type, though since I never got this thing off the ground with any cards made for it at all, I never knew how that would pan out time-wise.

Sat, 2009-11-07 19:13
copapoc
copapoc's picture

maybe change this into :

maybe change this into :

Too Soon
desing - element
one player puts his current set card at the bottom of the setdeck and put's the top one in it's place
a set deck woull look kinda like an planedeck and would consist of twice the number of players.

evry player would bring their 2 favorite cards, sleev them in their sleeves, and they would be shuffled. you do can see wich player thier from, but not wich card it is.you give evry player one and put the rest appart

alive and kicking relics of alara

Sat, 2009-11-07 20:52
A Tactical Waffle
A Tactical Waffle's picture

Just a random comment, we

Just a random comment, we should not call your interest amount the interest pool. It sounds way to much like mana pool.

@ Copapoc: No, I think I like the original idea more.

Through enough goblins at any problem and it should go away. At the very least, there'll be fewer goblins.

Sat, 2009-11-07 21:42
Art_Freak
Template Developer
Art_Freak's picture

@Jeske & copapoc: Personally

@Jeske & copapoc: Personally I'm against anything that would change a player's set card. It's a great idea to be able to do so until you consider that a player could own sets for different games, in which case a deck built around MTG would not be able to complete a VS set. It also doesn't work if the set cards are the determining factor of how to win the game. It won't do you much good to build a deck to build Ravnica, needing the hybrid, multicolor, and watermark cards if your opponent forces your set into being Saviors of Kamigawa. Now what do you do without a card for flips? If we do make it so that sets can be switched, then we have to establish an staple win con for all decks, which doesn't seem practical with each unique set having it's own criteria.

@ATW: I see your point. Some alternatives I can think of off the top of my head: Collective Interest & Interest Cache. I personally don't like how either sounds as much as I do interest pool. Any suggestions for what else we could call it?