Messages

Ah, yeah there is that. Scripts only work on the table, for better or for worse.

Hmm... perhaps an initialization script on relevant cards?

Code Select Expand

/cn"I have errata"

will make a small blue N on the card (on the table, not in the viewer pane), and hovering over it will show the note. With some searching and replacing, you could even make the note be the full errata text if you want.

Caveat: Lackey apparently doesn't stop reading in the note if there's another script directly afterward. So this works:

Code Select Expand

/ch;/cn"I have errata"

But this doesn't:

Code Select Expand

/cn"I have errata";/ch

This only applies if they're separated merely by semicolons. Separately tagged scripts are fine:

Code Select Expand

<s><a>y</a><l>Initialize</l><f>/ch;/cn"I have errata"</f></s> <s><l>Reveal top card</l><f>/vp1at1</f>

Scripting guide: https://www.lackeyccg.com/forum/index.php?topic=2134.0
Older scripting guide, which is outdated in general, but is still a useful reference for its commands, which work when preceded by /c: https://www.lackeyccg.com/forum/index.php?topic=1801.0

I don't know of a setting to do that selectively and automatically. Have you tried holding the `/~ key (in in the top left, just below escape) while mousing over cards? That should display the full card data next to the cursor.

Well if you decide to experiment with this any more, and you haven't fixed this part already, here's the card info file with all the image fields fixed. (I haven't verified every single one makes a valid URL, but every one I've tried does.)

http://magicplugin.normalitycomics.com/stuff/overpower-setinfo.txt

(Rename to "setinfo.txt" and replace the existing file.)

PNGs are supposed to work, even though they're not the default, but it's possible that has something to do with it. I have little experience with them in Lackey, as the Magic plugin is actually entirely JPGs.

It's aggravatingly mysterious. I used a program called Wireshark to watch the packets Lackey sends, just to be sure. It requests the exact same URL that works in a browser (or for downloading from the command line), but for some reason it doesn't download the image. I can't explain it.

Looks like it's trying to download most of its images from the Overpower website, including the cardback image, which is required for the plugin to load. It also looks like that website has changed how their URLs are formatted; the dashes are now slashes ("ally-17.png" -> "ally/17.png"). And the cardback image is still there, but it's a PNG instead of JPG.

I put the cardback image in place, then did a search-and-replace in my local copy of the card data. The URLs now seem to point to perfectly fine image files, but Lackey's still not downloading them correctly. If I go to those same exact URLs in a web browser, download the file, and save it in the plugin folder, it works. Not sure why yet, will probably do some more fiddling.

That could work! One thing to keep in mind is that if you create them as nontoken cards, both versions will be available in the deck editor. Adding "Token" to the beginning of the type line on cards that you only intend to spawn keeps them from cluttering up the master card list.

[YOUR]

Ah, okay, I see what you're asking now. Unfortunately, as far as I'm aware, this is a limitation of Lackey; there's ISYOURFACEDOWNVISIBLE, but no similar option for cards that aren't yours.

There are two workarounds I can think of. Neither is ideal, but depending on how your game works, one of them might be sufficient. (I don't know anything about how Exceed functions.)

The simplest is for players to just flip and reflip cards when they need to read them. This requires no additional work on your end, of course, though it could be confusing for players to see each other doing this just to check things, when the card isn't supposed to be "actually" flipping.

The second option would be to create tokens of the backside, either instead of or in addition to the "actual" backside. As an example, in Magic, even double-sided cards need to be turned "face-down" sometimes; that is, show a standard back rather than the "flipped over" version. So I give all cards the standard back, and cards that have a special backside have a script to spawn a token of it.

Depending on your needs, you could do both. If the card has both sides defined, and is currently face-up on the table, then anyone who mouses over it can see both sides in the viewer. Then if, as a game action, someone wants to flip the card over on the table, what they could do instead is right-click it and select the script to spawn the token, then place that token next to or overlapping the actual card. Then you could still tell at a glance which state it's in on the table, and everyone can still see both sides. (They could mouse over the token to see the back, and mouse over the original to see either the front or the back.) If you need to flip the card face-up again, simply drag the token to any non-table zone and it will cease to exist.

What do you mean "the opponent can't see either"? What does the opponent see in the card viewer pane when they mouse over the card on the table, just a blank space?

Some screenshots might be helpful in explaining both what you want to happen, and what is happening.

For comparison, the version I previously shared requires all pack structures be defined in Python. The default layout for a Magic pack (including the crit definitions, which can be reused) looks like this:

Code Select Expand

mythic = Crit('Rarity', 'IS', 'M')
rare = Crit('Rarity', 'IS', 'R')
uncommon = Crit('Rarity', 'IS', 'U')
common = Crit('Rarity', 'IS', 'C')

default = (
  BranchPoint(
      Branch(Kind(1, mythic), prob=13),
      Branch(Kind(1, rare), prob=87),
    ),
    Kind(3, uncommon),
    Kind(10, common),
)

These days I write my pack structures in YAML, a simpler format. It's not a programming language; it's made for listing data or settings. So the above gets streamlined to:

Code Select Expand

mythic: [ Rarity, IS, M ]
rare: [ Rarity, IS, R ]
uncommon: [ Rarity, IS, U ]
common: [ Rarity, IS, C ]
---
default:
  - 13: [ 1, mythic ]
    87: [ 1, rare ]
  - [ 3, uncommon ]
  - [ 10, common ]

In either case, the Python code handles reading that, generating the pack-wide chances that Lackey expects, and outputting it as XML:

Code Select Expand

<chance>
  <prob>13</prob>
  <kind>
    <qty>1</qty>
    <crit><field>Rarity</field><eval>IS</eval><data>M</data></crit>
  </kind>
  <kind>
    <qty>3</qty>
    <crit><field>Rarity</field><eval>IS</eval><data>U</data></crit>
  </kind>
  <kind>
    <qty>10</qty>
    <crit><field>Rarity</field><eval>IS</eval><data>C</data></crit>
  </kind>
</chance>
<chance>
  <prob>87</prob>
  <kind>
    <qty>1</qty>
    <crit><field>Rarity</field><eval>IS</eval><data>R</data></crit>
  </kind>
  <kind>
    <qty>3</qty>
    <crit><field>Rarity</field><eval>IS</eval><data>U</data></crit>
  </kind>
  <kind>
    <qty>10</qty>
    <crit><field>Rarity</field><eval>IS</eval><data>C</data></crit>
  </kind>
</chance>

Let me know if you'd find this updated version handy, and I can look into extricating it into a shareable form.

This may or may not be way more complicated than is helpful or warranted in your situation, but I made a tool that can help with generating chances when your pack structure gets more complex: https://www.lackeyccg.com/forum/index.php?topic=12713

I have actually improved and streamlined it a good bit since, but in a way that unfortunately is pretty tightly coupled with the rest of my Magic-plugin-generating code. No one's ever expressed interested before, so I haven't worried about it too much. But if it could be helpful to you, I could see about packaging my newer version up into a tidier and more shareable form. In its newer form, especially, it should require very little knowledge of programming in Python.

Heck yeah! Godspeed, and feel free to ask more questions if something stumps you.

You're in good company here! In over my head but stubbornly willing to learn is exactly how I started out when I took on responsibility for the Magic plugin. (Not that this should be anywhere near THAT big an undertaking...)

Did you put pack definitions in your packdefinitions.xml file? If you left it blank, or your formatting is incorrect, that could be causing an issue.

It might be helpful, in troubleshooting, to copy one of the pack definition files from the Magic plugin (or any other plugin with currently working packs). None of the packs will probably be able to actually load cards, since they'll be referring to set names that probably don't exist in your plugin, but the pack selector should at least show up and display the available pack titles.

I installed those two plugins, just now, to test. I get the same results. (My existing MTG installation still works fine.) Not sure yet what the actual issue is, but at least we can be pretty certain it's a problem with the plugins, not some local system issue or Lackey setting.

Edit: I think I see the issue. These plugins use what looks to be an earlier format for pack definitions, before Trevor settled on his "1.0" XML syntax. I dug around to see if any other plugins I have installed use the same pack format; LOTR does, and it displays the same buggy behavior.

If you're feeling industrious, you could probably follow that guide and update the pack definitions to the newer syntax. (Liberal use of search-and-replace would no doubt come in handy.) I don't know if either of those plugins is still maintained, but if so, you could also contact the maintainers about this.