Milovana.com

TypingMad wrote: Mon Nov 28, 2022 9:27 pm - Rather than one big library, we could release sets - Senran Kagura set, Redrock set, fetish sets, etc - to keep card numbers manageable and to make customising better

JeriKING wrote: Tue Nov 29, 2022 2:31 pm Lobster I really want to check that version, looks really interesting. Could it be done something like I don't want X set to appear in the deck? Maybe someone is not into monstergirls and wants to disable them for example

BallsBAM wrote: Tue Nov 29, 2022 5:57 pm Sorry I couldn't resist I looked at the code and downloaded everything, it's well done even the dimensions are not disproportionate, from V1 I think it would also be necessary to add the randomly discard keys from the deck to accommodate the discard effects for example of Assassin (50).
Perhaps widening the view of the cards on the field a little even reducing those of the deck and discards a little could be better

Lobster wrote: Tue Nov 29, 2022 6:17 pm

BallsBAM wrote: Tue Nov 29, 2022 5:57 pm Sorry I couldn't resist I looked at the code and downloaded everything, it's well done even the dimensions are not disproportionate, from V1 I think it would also be necessary to add the randomly discard keys from the deck to accommodate the discard effects for example of Assassin (50).
Perhaps widening the view of the cards on the field a little even reducing those of the deck and discards a little could be better

I have a button to discard (or exile) the top card now. Along with rotating and flipping. V1 does have the issue that it's designed specifically for the first images Jeriking shared which were a set size. I've fixed that in V2 so it will scale any image to fit.

I'm still not 100% decided on how to do the field cards. They need to be discard-able (possibly via a return to play to simplify it). Clicking one to make it join the back of the hand could work. Or maybe clicking it just makes it bigger and then buttons appear to move it wherever (need to consider any cards that have been placed behind one too and what to do when there's more than 9 of them). You are right that they either need to be bigger or possible to make bigger (or both). But also, the bigger they are, the less fit on the screen. Initially, I think I had more like 15 spaces but they were even less legible.

For the more than 9, I'm thinking a couple of scroll buttons like the Prev/Next ones there already are. Maybe use that with something to say that the one in the middle of the screen is the selected one and buttons by that to do all the actions...

V2 layout tweaks:

notSafeForDev wrote: Tue Nov 29, 2022 9:19 pm Here's something I have been working on

BallsBAM wrote: Tue Nov 29, 2022 9:41 pm And for the barrier skill, did you think about putting the random from deck button which then goes into the hand and then sends it back to the deck with shuffle?

notSafeForDev wrote: Tue Nov 29, 2022 9:19 pm Neat to see I'm not the only one intrigued enough to create a program for this.

Here's something I have been working on:

MtF.png

It displays:
* Total number of strokes for the drawn card (15)
* Total cards remaining in deck (15)
* Total cards in discard pile (36)
* Cards in hand (3)
* Active cards along with any added strokes for each of them (7)

Hovering over any drawn card scales it up, to make it easier to read.

It uses a json file to define what each card does, for example:

Code: Select all

{
        "name": "bloom",
        "color": "green",
        "strokes": 15,
        "effects": {
            "addStrokes": {
                "turns": 3,
                "value": "(turn - self.lastPlayedTurn) * 5"
            }
        }
    },

Each card can have a set of effects, in this case, the bloom card has the addStrokes effect, which will last for 3 turns and add strokes based on the current turn value and the turn the bloom card was drawn.

It uses javascript eval to calculate values, so pretty much any valid javascript can be used.

I got quite a lot on my plate, so I'm not sure how much more I will be able to work on this, but I thought it would be useful to share for inspiration.

Here's the source code along with a readme:

MtF.zip

Lobster wrote: Tue Nov 29, 2022 10:01 pm
I was planning on doing that but you get functionally the same effect by drawing another card, doing it and then shuffling it back in. The only thing that messes with is anything that puts the card on top or just under the top of the deck but then they'll already be broken by shuffling it back in so it might not matter.
Edit: thinking further about it, it's possibly still worth it because it could put it on top of the "hand" pile instead of at the back....

BallsBAM wrote: Tue Nov 29, 2022 10:05 pm it is certainly interesting, even if I must say that I tried and when I open it in the browser it doesn't let me start anything, I copied the first 60 cards I don't know what the problem is

BallsBAM wrote: Tue Nov 29, 2022 10:10 pm

Lobster wrote: Tue Nov 29, 2022 10:01 pm
I was planning on doing that but you get functionally the same effect by drawing another card, doing it and then shuffling it back in. The only thing that messes with is anything that puts the card on top or just under the top of the deck but then they'll already be broken by shuffling it back in so it might not matter.
Edit: thinking further about it, it's possibly still worth it because it could put it on top of the "hand" pile instead of at the back....

Yes, I thought about it too, more than anything else randomly taking from the deck is different from drawing the next one, maybe for the future, I don't know, anyway is working fine :)

notSafeForDev wrote: Tue Nov 29, 2022 10:15 pm If it's still not working, please open the developer console in the browser and let me know what appears.

Access to script at 'file:///<location>/index.js' from origin 'null' has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: http, data, isolated-app, chrome-extension, chrome, https, chrome-untrusted.

Failed to load resource: net::ERR_FAILED

BallsBAM wrote: Tue Nov 29, 2022 10:29 pm Yes exactly I copied the cards in the decks/starter_set folder
in the decks folder there are only Starter_set.json and the starter_set folder with the 60 cards inside, when I open index.html I only see the backs
in the panel it says:
Cross-origin (cross-origin) request blocked: Origin matching policy does not allow reading remote resource from file:///C:/Users/Desktop/MTG/index.js. Reason: CORS request not http.
The source URI of the module is not allowed in this document: "file:///C:/Users/Desktop/MTG/index.js"

Lobster wrote: Tue Nov 29, 2022 10:34 pm

Code: Select all

Access to script at 'file:///<location>/index.js' from origin 'null' has been blocked by CORS policy: Cross origin requests are only supported for protocol schemes: http, data, isolated-app, chrome-extension, chrome, https, chrome-untrusted.

(<location> is correct) then

Code: Select all

Failed to load resource: net::ERR_FAILED

notSafeForDev wrote: Tue Nov 29, 2022 10:53 pm Right, thanks for the info! I forgot that you would get cors errors from opening the html file directly. To run it, I use VSCode with the Live Server extension.