A downloadable tool

Get this tool and 4 more for $40.00 USD
View bundle
Buy Now$10.00 USD or more

This is an extension for the duelist cards (RPG Maker MV/MZ) plugin.

Features:

  • Randomized card pack setup.
  • Scene BGM setup.
  • Custom card motion sequences when pack generated.
  • Post creation view scene.

Compared to the base plugin, this extension is relatively easy to setup.

Please pay attention to the note in the help section with regards to screen animations.

MV users may use the following script call to call pre-made packs:


The parameter sets the background images to be used in the pack viewer.

There isn't anything more that needs to be done here. Let's move on to the plugin command setup:

  • Pack configuration: Setup the card creator. This will randomly select from available cards based on your settings. Setting up multiple packs will cause them to be randomly selected.
  • Backgrounds: Set custom background for the scene.
  • BGM: The audio BGM file to play during scene.

Note (MV Users): Backgrounds is set via the "Create Pack Backgrounds" parameter in the plugin parameters and BGM is set via the "Default BGM" parameter in the plugin parameters.

  • Type: The type of card search to do. In the image above, rating is selected as the type and as such, it will select cards based on the "Rating Cards" parameter.
  • Number: The number of cards to create.
  • Filter: Can opt to remove card types (monster, ability or field) from the card pack creation.

Fixed cards are a list of cards (by name) that can be created. The cards created are randomly selected from this list and selection rate can be influenced by frequency of name occurrence in list.

Rating cards is the max rating of card that can appear in the booster pack. 

Weight cards is the max weight of card that can appear in the booster pack.

Element cards are the valid elements of the cards that can be added to the pack.

After setting up these parameters. That's basically it. No further setup is required.

If you want to add some custom card motion sequences, we need to go a bit further:

For all cards created, the sequences will be checked from the first to the last in the sequence list.

To get the simple out of the way...:

  • Card X/Y refer to the initial card position on the screen for the sequence.
  • Card Alpha is the starting transparency of the card. 0 represents full transparency whilst 1 represents full opacity.

Rating, weight, type and elements represent the conditions required for the sequence to activate for the card. For elements, if the list is empty, any element is considered valid.

Actions are what we need to be really concerned about:

  • Type: The type of action the card does on screen.

Once a type is selected, the related configuration will be used for that action. For example, in the image above, animation is selected as the type. This means that the animation configuration will be used.

  • Location Configuration: Move the card on screen in X/Y coordinates.

X/Y is the target screen position for the card to arrive at whilst duration is the length of time required to do so.

  • Rotation Configuration: Rotate the card (Value is read in radians).

Magnitude is the size of rotation to apply. A full circle is read as Math.PI * 2.

Type may be 'set' or 'constant' in which set only applies the rotation once and constant applies it continuously over the "Duration".

  • Animation Configuration: Play an animation from the RPG Maker database.

Animation is the database ID of the animation (Available as a selection menu). X and Y are used to set the screen position of the animation if it is not a screen centered type.

If it is a screen centered type, leave it at 0.

  • Transparency Configuration: Change the transparency of the card.

For alpha values, 0 represents full transparency whilst 1 represents full opacity. Duration is the time taken to arrive at that target alpha.

Finally, there is the "Wait Duration" parameter which is how long the action lasts before moving onto the next. This setting is independent of the durations set in the various configurations.

Purchase

Get this tool and 4 more for $40.00 USD
View bundle
Buy Now$10.00 USD or more

In order to download this tool you must purchase it at or above the minimum price of $10 USD. You will get access to the following files:

BACKUP.js 42 kB
Synrec_Duelist_Pack.js 69 kB

Development log

Comments

Log in with itch.io to leave a comment.

When ever I get a card pack and it trys to show all the cards I got at the end, I get this Error

TypeError: Cannot read property 'selectionCard' of undefined

    at WindowDuelist_DuelCardData.drawMonsterATK (Synrec_Duelist.js:8527)

    at WindowDuelist_DuelCardData.drawMonsterData (Synrec_Duelist.js:8493)

    at WindowDuelist_DuelCardData.redrawData (Synrec_Duelist.js:8414)

    at WindowDuelist_DuelCardData.setCard (Synrec_Duelist.js:8404)

    at Synrec_Duelist_Pack.js:1837

    at Array.forEach (<anonymous>)

    at Window_CardViewList.updateData (Synrec_Duelist_Pack.js:1836)

    at Window_CardViewList.update (Synrec_Duelist_Pack.js:1817)

    at WindowLayer.update (rmmz_core.js:4231)

    at Scene_PackView.Scene_Base.updateChildren (rmmz_scenes.js:129)

SceneManager.catchNormalError @ rmmz_managers.js:2032

SceneManager.catchException @ rmmz_managers.js:2020

SceneManager.update @ rmmz_managers.js:1941

Graphics._onTick @ rmmz_core.js:811

TickerListener.emit @ pixi.js:9093

Ticker.update @ pixi.js:9548

Ticker._tick @ pixi.js:9298

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301

requestAnimationFrame (async)

Ticker._tick @ pixi.js:9301


The plugin was put in the latest demo.

(1 edit)

What is the version of the core duelist cards plugin you are running?

EDIT: Nevermind found it on my end. This will be patched next core plugin update.

Also, the game pauses after I make a move, is this supposed to happen?

pauses how?

Basically, whenever I click on a card when I can't play any more cards it pauses, and I have to click the thing that looks like the power symbol (the thing you click on when you want to access the power option like sleep and turn off) on a computer to progress.

When you can't play any more cards the game pauses...? Is there something that's expected to happen?

Is there no gamepad support in the future plans?

If this is the case, then I can completely cancel the optimization of the game controller operation logic.

There are regrets (no matter who it is), but I’m also grateful that my workload has been reduced.

Thanks for bringing it to my attention. I'll see what can be done for future updates.