News:

A forum for users of LackeyCCG

Main Menu

Recent posts

#1
I've been unable to discover additional available criteria. Notably, there doesn't appear to be a functioning ISLESSTHAN, and I haven't even been able to get ISGREATERTHAN to work.

There are two main ways I know of to handle cases like this, where multiple card slots in the pack each have options. One would be to add a card data column named something like CardSlot. All your uncommons would list "3"; all your rares would list "3 4"; and all your ultras would list "4"; that way you could specify a crit like "CardSlot CONTAINS 3" and be guaranteed to get either an uncommon or a rare.

One limitation of this is that you can't alter the probabilities. If your set has, say, 80 uncommons and 20 rares, you'll always have an 80% chance of getting an uncommon for slot 3.

The other way to handle this is to use what Lackey calls Chances, each of which has a certain percentage of appearing, and includes whatever cards it should provide. The complicating factor is that Lackey only understands chances on the level of the entire pack, not for individual card slots. So in your case, the pack would have four total chances:
  • (2 commons and) 1 uncommon, 1 rare
  • (2 commons and) 1 uncommon, 1 ultra
  • (2 commons and) 2 rares
  • (2 commons and) 1 rare, 1 ultra

This way you could specify whatever probabilities you want for each of the for options (assuming you make them add up to 100%).

Calculating from the probabilities you want for each slot to the probabilities you ultimately need to specify at the top level can get onerous, especially if you've got multiple slots with multiple options. If you've ever tinkered with Python, you might find this tool I made useful:

https://lackeyccg.com/forum/index.php?topic=12713

I could probably stand to make an updated, improved version of that, now that I look at it...
#2
@BADxWOLF, sorry for the late reply. I'm not sure why Edge of Eternities would be doing that, I'll have to look into it.

Some packs are "missing" because not all sets care available in draft boosters. Commander sets (aside from Commander Masters) usually come from Wizards of the Coast as preconstructed decks; as far as I know, there's no such thing as a Bloomburrow Commander booster pack.

(That said, I still haven't updated more recent sets with the new layout of draft boosters... they keep making the options more complicated.)
#3
Plugins & Plugin Creation Forum / Re: Crash Log location?
Last post by Alastair - September 16, 2025, 10:37:28 PM
Look at how Magic does it if you want to see multiple folders inside the parent directory.
#4
Plugins & Plugin Creation Forum / Re: Crash Log location?
Last post by ThatGuy - September 16, 2025, 07:50:37 PM
Oh, I thought I followed the CardUrlFiles: section correctly.
I didn't want to use a General Url for a single folder. I like the idea of being able to control the destination and filename for each image.
#5
Plugins & Plugin Creation Forum / Re: Crash Log location?
Last post by Alastair - September 16, 2025, 05:43:48 PM
For starters "CardImageURLs1.txt" is not a valid URL for CardGeneralURLs: which expects an actual URL of where the images files are located at.
#6
Plugins & Plugin Creation Forum / Re: Crash Log location?
Last post by ThatGuy - September 16, 2025, 03:49:51 PM
Ok, I'm stumped. I had everything working on my local copy.
All the Images, and carddata text displayed. The Pack definitions gave the right amount of correct cards.
It all looked good, So I added checksums to the update list and moved everything online. cleared the plugins folder and did a fresh download...

It worked, until it tried to get the Cards, then lackey crashed.
Opening Lackey again, I could see all the cards but none of the images were loading.
I hit the manually download missing images button, and that worked! It grabbed all the files.

Also, adding packs, if I Choose a pack, it works fine. But Choose and View now crashes Lackey and it didn't before.?!

The updatelist.txt is located here, If you could offer any insight I am sure I just missed something small. Please & Thank you.
#7
Plugins & Plugin Creation Forum / Re: Crash Log location?
Last post by Alastair - September 14, 2025, 07:37:53 PM
It does generate a debug log for some actions where there's known possible issues. For a blanket crash though, no.
#8
Plugins & Plugin Creation Forum / Re: Crash Log location?
Last post by ThatGuy - September 14, 2025, 06:14:09 AM
I fixed the crash. Forgot the <plugin> tag

Still, an error log would be nice.
#9
Plugins & Plugin Creation Forum / Crash Log location?
Last post by ThatGuy - September 14, 2025, 04:43:23 AM
Does Lackey generate a crash log?
When I try to load my plugin Lackey crashes and I am not sure why.
#10
General Discussion Forum / New LackeyCCG Release 1.1.5 (S...
Last post by Alastair - September 12, 2025, 07:20:09 AM
The new version of LackeyCCG, 1.1.5 (September 12 2025), is now available for both Windows and Mac. The game server has already been enabled to allow connections from the new client. This is a forced update due to changes in the networking code, older versions will not be able to connect.

https://www.lackeyccg.com/downloads.html

Fixes and Changes
----------------------------------------------------------------------------------------
Fixed it so that ` and | are no longer blocked from text input and still function as shortcuts when not in a text input state.

Fixed double ratio swap: Ratios were getting swapped when they shouldn't in the function that draws moving cards.

Name Change Fix: Players can now change their name while connected to the game server.

Save/Load Game fix: There were some race conditions with saving and loading game states that resulted in players losing zones or parts of zones. Fixed what I could find of those and added debugging info to help track down other instances.

Visibility for super zones: Adding more careful checking on visibility for super zones

Column Sort Logic: Sorting is now aware of the type of data in columns and does it first numerically and then alphabetically.

DLog Update: DLog() now includes a timestamp in what it writes to the debug log.