We can't do this because technically, the colored sections of the land frames aren't the same as the corresponding areas on a colored land card. Compare a green card and a Forest again.

Now, I've done something similar to grant things like colored lands for flip style, but it should be avoided when possible since it is not correct. And even if it were correct, making the change program wide would wreck some custom styles, such as the popular FPM frames.

I've already fixed this for 0.3.8.

I support Pichoro in this matter, but I do think that at some point in the future, the blends scripts need to be redone, to make it clearer and cleaner how they work. When I say 'redone', I don't mean necessarily starting from scratch, but I think they need to be looked at and kinda reworked knowing that all of these different combinations are necessary. I can visualise a system whereby the definition of frame, piping, and texbox colours are separated and made distinct, meaning that the ultimate call to the blend would have three parameters, each a collection of colours, for each rendered part.

Well, I've made no secret of my dislike for doing this unless absolutely necessary. I see what you typed there, and think something like "Fize Size: Going Up!" and making the change to sooo many templates, some of which are already using crappy frames images to begin with... *shudder*

Well the idea is that it will actually *reduce* file size, since you'd probably be reducing the size of the blends script file, by streamlining the code. To be honest though, text files aren't the issue with file size, images are. And depending on implementation, masks may not need changing, or if they do, there wouldn't need to be more than there are currently.

At any rate, we're talking about optimisation fixes in the future; the current system _works_ fine as it is, its just quite messy, and not very intuitive for new designers.

I don't know that I would call the current system "unintuitive". Most of it is quite intuitive; there are a few odd spots I'm not fond of, like the "Murmuring Bosk" effect. But really, I think that's about it. The rest seems to work well to me.

Whats the maximum number of nest if then statements and could you increase it?
*Currently I can only do 3*

I don't know the maximum number of if-then statements, but you might be able to get more by using subscripts instead of trying to make it a single script.

Could you pm on the file library some examples?? because I'm not sure what you mean if that's not too much trouble.

Feature request: Change the size of the text on a card.

Ask Wizards, October 15: http://www.wizards.com/Magic/Magazine/Article.aspx?x=mtg/daily/askwizards/1008

They do it to make their cards look better, basically, so if it wouldn't be too much of a pain in the ass to do, I'd love to be able to do the same.

This is really hard to implement. Somebody tried it before, a while back, with a text size choice field, but essentially, this is one of the areas where MSE is always gonna fall down; real MtG cards are typeset by professionals, and MSE is not a typesetting program, its a card creation program.

Okay, that's cool. Can't have it all, nice as it would be.

There's more important stuff to work on than that anyway.

Actually, discovering that the text size used by M:tG cards is chosen from a set of options is interesting. It would theoretically be possible to try to replace the automatic font sizer with a manual one that can size the fonts in small increments. We know the maximum (cards like Cancel with no flavor text and rules in the middle) and the minimum (Soul's Grace), so we can try to do it.

It would require some program changes, though, but I'm just saying it's possible.

A (hopefully) simple request: The ability to script the size of an image field inserted into the Set Info or Styles tabs.
You can read the whole discussion here: http://magicseteditor.sourceforge.net/node/1976

Shadowmoor and Eventide sort the hybrid cards by their color, then name. I know Shards of Alara doesn't do this, but I'd like a feature that allows sorting of the gold cards similar to the hybrid cards (WU, WB, UB, UR, BR, BG, RG, RW, GW, GU).

I'll be blunt; I don't want to. The sort script is already a mess just to cover all the real combinations.

Agreed. It's nice in theory to be able to do everything, but lets be realistic - one timers like the sorting you're suggesting aren't worth it for all the scripting they would need and how unlikely it is people would actually use it. The only thing that sorting would really be needed for is if you're trying to proxy that set, which is not what MSE2 is for.

I've noticed that if you take a wide symbol and give it multiple points of symmetry, it does not resize on the card but instead cuts part of the symbol off. I'm assuming this was not intended.

I believe this has been already noted in the bugs thread. Nice symbol though.

Indeed; error noted, and already fixed it seems.

Request... I think. You'll see what I mean.
I would like it if we were able to script a switch into symbol fonts. I was working on the YGO templates and adding a new card type that requires a different version of the * symbol. I tried scripting the following to make it so that no new symbol code would be needed and that the appropriate * symbol would appear based on card type.

Here are examples featuring the regular * and the anti-* respectively:

And what I tried to script:

symbol:
	code: *
	image: { if card.card_type=="dark synchro summon" then "dstar.png" else "star.png" }
	image font size: 20

It worked, both images would appear, just not how they were supposed to. This is where I come to a fork in the road whether this should be a bug or a request. You see, I can't recall any if this then that scripts being used in a symbol-font before, so I'm guessing its not so much a bug as something that just hasn't been thought of or worked out.

What was happening is I would type in the * for the level and a * would appear, but it didn't switch like it was supposed to. I had two cards in the test set, one a "normal monster" which uses the * symbol and one a "dark synchro summon" which uses the anti-* symbol. When I hit reload data while viewing the normal one, the * symbol appeared on all the cards. When I hit reload data while viewing the dark synchro one, the anti-* symbol appeared on all the cards.

What I gather from this is that the program can locate both files and the script functions, but the script isn't limited to a single card and instead references all the cards in the set. I can understand this as symbol fonts generally are the same throughout the set, and don't vary internally based on the individual card. In my case, I just ended up using ^ as a new symbol trigger for the anti-* symbol, but ideally I would like to be able to use the * symbol for both so that when the frame switches, so does the *.

Scripts in symbol fonts do exist (for instance, the magic tap symbol), though not exactly in the way you are showing here.

Indeed, this functionality should be possible already. Try this instead:

symbol:
	code: *
	image: dstar.png
	enabled: {card.card_type=="dark synchro monster"}
	image font size: 20
symbol:
	code: *
	image: star.png
	image font size: 20

Notice that the one with the "enabled" is first; it needs to be that way, as the one without is the default. Also note that only one has an enabled; the one without is a "catch-all" for all other cases.

Update: I've tested this now, and it works.

Thanks for the input guys! And thanks a million for the example, it makes it a lot more clear now. I guess I tried to go at it from too much of a game/style file scripting approach.

I know that 0.3.7 1/2 is out already but I couldn't find the most recent one. But I have a couple of things I would like different. Could you change the Text for the name of YGO cards. Everything else is PERFECT in YGO! And how 'bout in Magic, when you type 0/C, instead of making it the Hybrid (or guild) mana, how about making it the half mana like the one's in Unhinged? So insted of (0/W), it's [W)

Because there's already |C for half mana.

Indeed; |W is not the same as 0/W for a reason. In fact, I could imagine a card actually using the 0/W symbol and being balanced.

Sample Card [0/B]
Sorcery (C)
As an additional cost to play ~, pay 3 life.
If you paid B to play ~, target player discards a card.
Draw a card.

So, no, the 0/C functionality will be staying.

As for Yu-Gi-Oh, its going through changes currently. Look here: http://magicseteditor.sourceforge.net/node/1987

Street Wraith says your sample card could probably get away with being only 2 life.

Okay, yeah, fine. But the card isn't meant for critiquing, its meant as a sample to show that the 0/C is a valid mechanic and should remain accessible in MSE. Please, no further card critique here. Don't make me remove comments, please.

I know, I was teasing you. I know how much you hate random example cards being critiqued completely out of context

Odd request here that hopefully wouldn't be too hard to add. Can we get an "Export to Forums" options that exports to a .txt file formatted like so:

[card name] [mana cost, with the correct forum formatting so the symbols come up like they should]
[type] [rarity, in letters (C, U, R, MR, S)
[card text, again with symbol formatting like the cost]
[p/t, if any]
[ft, with italics brackets for the forums]

This would make community projects easier for those involved so we don't have to work in MSE, copy to text, then have the project leader copy back to MSE?

LP has created an export template that's similar to that. Have a look: http://mtg.pifro.com/viewtopic.php?f=8&t=483

My export tempalte does all that (admittedly formatted for these forums, but italics and stuff should be transferrable to other forums easily.)

Aside from one thing; converting mana symbols to forum shortcut mana symbol images would be hard, since it varies a lot between forums, and its quite a complex bit of coding. So at the moment, it just outputs the text for symbols, like 2WUUB or whatever.

well I figured we just configure it for this forum, since that is where most posts will go (at least for me)

Thanks for the link though, didn't know that existed.

Something else to keep in mind is that its really better not to do cost formatting using form images when you're submitting cards for a group project. It would be much better to just type the cost out, as WUBRG than to type since the program doesn't recognize the latter.

Well, personally i'm wary of copypasting anyway since I've got some odd control-character related bugs in the past. What i do hate is when people type it out like 2. There are symbols too, guys! Its just best to be consistent.

Wait, I do have a useful suggestion; A 'new card from clipboard' funtion, that takes text formatted in the form:

Name manacost
types - subtypes (rarity)
rules
rules
p/t
flavour

from the clipboard
and pastes it into a new card.

That sounds pretty complicated to me. Maybe those who actually know how to implement these types of things have a better idea, but given the propensity for weird little bugs, I wouldn't be surprised if such a feature took

Brain Gorgers 3B
Creature - Zombie (common)
When you play Brain Gorgers, any player may sacrifice a creature. If a player does, counter Brain Gorgers.
Madness 1B
4/2
In spite of their hunger, they're slow eaters.

and turned it into

Brain
3B Creature - Zombie (C)

It would get the rules text, though.

I should note, too, that the Gatherer at least lists the power and toughness between the creature type and the rules text, not between the rules text and the flavor text. Then again, they list the rarity before the card name, too. Eh.

This is going to seem like an odd request...

Is there a way to make a card that's hybrid artifact, sort as it's color(s).

For example, in Planar Collapse, my next set, there is the following.

Frostfall
-
Snow Sorcery
Frostfall is white.
Destroy all creatures, they can't be regenerated.
Suspend 5
Repeat 13
Rare

In order to further the flavor, I've created homebrew snow frames. I usually hybrid the color, and the artifact frame (white in the case of the old frame, and blue for planeshifts). However, when the cards sort, it doesn't recognize it as a white card, but as a hybrid (?!?!), despite the rules text being clear that it is white, and nothing else. If that could be dealt with, it would be appreciated.

I'm not sure if I can do anything to help you or not, Jrzman. Could you clarify; are you using a custom frame image for snow, or are you using the hybrids to generate the effect of one?

If you're using hybrids at all, the reason you're getting what seems like an error in the sorting is that the order cards sort is determined by cost (first) and frame color (second). Rules text is not used to determine color, as cards that say "~ is white." have a white frame.

If you're using a custom frame image, I'm willing to integrate it into my Magic New w/ Extra Colors template if you wish; once I do that I can alter the sorting to do whatever. In fact, even if you don't consider this an acceptable solution, would you be willing to post the custom frame image (if you have one)? I've wanted to put snow into that template for a long time, but can't find a suitable frame.

I'm using the hybrids to generate the effect. It makes the card frame seem more crystalline, and reinforces that it is a snow spell.

I really don't have a lot of image editing experience, thus I created a homebrew frame using the frames internally within the program.

Then I'm afraid I can't do much for you. In the eyes of the program, such a card is a hybrid. Sorry.

White and blue overlay hybrid makes a lovely snow frame

If you need a frame for snow in magic-extended, pich, I can mix up the blue and white to make a snow frame in an editing program.

I know the card text and flavor text has an automatic smart quotation marks feature (“ ” vs. " "), as well as a smart apostrophe (’ vs. '). Is it possible to have this feature added to the card name and card type fields as well? I am a bit OCD about this kind of thing, and copying and pasting an apostrophe into names gets kind of annoying.

Its certainly possible, all it would take is a line "script: curly_quotes", but whether or not it is necessary in the card type box is debatable. Card names I can see having quotes in, in rare occasions.

a simple request to also update the YGO templates to add in the Dark Synchro frames *with correct placement and coloration of letters and stars on them as well; and the fixing of the justify issue on the last line of a YGO card text

Most of your request is already completed, Nahts. Have a look here: http://magicseteditor.sourceforge.net/node/1987

To my knowledge, the Justification is the only thing not done; that would require a change to the program. Would you mind showing some example cards that really feature the justification you're speaking of? I'd like to see how it works on real cards.

Sorry for the double post, but I have a new request for a program wide change. I'd like to be able to use semi-transparent colors with symbol variations. Specifically, this would be with the goal of cleaning up the set symbol watermark feature by stopping border pieces from appearing; on real card with set symbols used as logos, only the fill portion of the watermark is used.

I've got two (hopefully small...) ideas:

Being able to edit values (at least text or choice) in the card list, not only on the card itself, would speed up template development a lot.

Making card field's editable: scriptable boolean instead of boolean. (I suppose this can be tricky for some obscure technical reason... perhaps, if a card's editable is scripted, you should treat it as editable in all respects, but disable the actual input component on the card...). This would I wouldn't have to move unneeded fields like 5000 pixels to the left, so that they don't get in the way

Liosan

sorry for the late reply Pichoro, but here's the justification difference:

Real card

---

MSE card with Justified turned on

---

MSE card with Justified turned off

---

sounds minuscule; but there are "perfectionists" out there :/ (like me >_>)

Yes, I see. It would be nice to have an option to add on to justify, to not justify short lines. Similar to how we have "left middle shrink-overflow", we could maybe have something like "middle justify left-short" meaning to justify everything except short lines, which would be left aligned. I don't really know about the feasibility of such an option (that's up to Twan), but its an idea.

Usually justifying is only done on lines ending in a soft line break, i.e. when the text wraps around because of the size of the text box. Right now, MSE justifies all lines as you show in your example. I think this can be considered a bug, and I will get to work on fixing it.