Collectible Card Game Headquarters

Hi all,

New to the forum but not MTG or xmage. Absolutely love the software thank you for everything. I do have a couple questions, how come some cards from older sets are not implemented like an example would be lava burst in ice age. I’m just curious. Also mutate, I’ve seen this talked about but are the devs actively working on implementation or is it a dead issue? Macros, dead forever or sidelined for now? Last question, how can I implement cards and do I need to know Java extensively? Thanks to the devs for everything they are doing with this software!

Nobody knows? Was this addressed in another forum?

You should join the XMage discord if you want quicker answers. And I most likely won't be reading this forum again in the near future either.

As for your questions:

1. Lava Burst is rough because of the unique un-redirectable damage clause. Not impossible to implement but nobody has bothered.

2. There's a relatively complete implementation of mutate as a pull request, but it's still suffering from problems with zone changes of the mutated cards, and nobody has been able to fix those.

3. No idea about macros.

4. If you're interested in development, here are some general instructions. And some instructions for implementing cards.

5. Card implementations aren't rocket science, but they're some sort of science still. You need to know java or be willing to learn.

Nobody is aware?geometry dash Was this discussed elsewhere else?

To master every situation and manage the appearance of tags in a flexible way, one thing is for sure, you must know Java

paulsacha wrote:To master every situation and manage the appearance of tags in a flexible way, one thing is for sure you must know Java

Tags also help you quickly both access related events and view the tag distribution for a set of events.

Slottedpig wrote:Nobody knows? Was this addressed in another forum?

So, yet another tiny update to HQ AI-Enhanced card pictures for Forge dinosaur game

paulsacha wrote:To master every situation and manage the appearance of tags in a flexible way, one thingbasket random is for sure, you must know Java

It's not easy.

Missing cards from older sets could be due to various reasons, such as licensing issues or technical challenges in implementing them. The devs are likely aware of such requests and may be working on them, but adding new cards and features can take time. Regarding mutates and macros, it's best to check with the devs for updates on their status.Implementing cards typically requires some knowledge of Java, but you don't need to be an expert. There are resources and tutorials available to help you get started. And hey, when you need a break or want to clear your mind, playing spider solitaire is a great way to unwind.

Nobody knows? paper io

Older Cards Not Implemented (e.g., Lava Burst)
Reason: Some older cards may not be implemented due to various factors, including complexity, lack of demand, or prioritization of newer sets and mechanics. The development team often focuses on balancing and maintaining current gameplay standards.
2. Mutate Implementation
Status: The implementation of mutate is actively discussed among developers. While there may be challenges, it is not considered a dead issue. Developers are likely working on it, but timelines can vary based on other priorities.
3. Macros
Current Status: The future of macros is uncertain. They might be sidelined for now, but there’s always potential for revisiting them based on community interest and developer capacity.
4. Implementing Cards
Java Knowledge: To implement cards in the software, a basic understanding of Java is beneficial. However, extensive knowledge may not be strictly necessary, as there are often guidelines and community resources to help you get started.