@bazola Make sure you have mvn linked to the cmd prompt, open up command prompt (actually Git bash I always have open) and run it in the correct folder
okay, that is what I have been doing but I haven't had to do it in a long time. usually build with dependencies would pick everything up that i needed. but it won't pick up these mockito files
ugh no i take that back... closing and reopening netbeans fixed things without mvn install.. but when I checked it, it was still showing errors, so I flipped back to this window and typed what I just said, and then when I looked at it again the errors went away..
right now the lobby stops you from having more than one game at once (and the code is not set up so that you could have two games at once without some changes)
@SimonAndréForsberg I agree, and maybe we don't want to let users have more than one game, just wanted to see how you all felt on the topic
with regards to scrapping, I hate the idea of needing an explicit scrap button on the cards all the time, but I hate the idea of needing a confirmation pop up for pretty much every action even more. For example, if you can attack with a creature, but you would rather scrap it, you would have to tap the card, and a window would pop up that says Scrap or Attack? and then after you click attack, you would have to click a target. that seems clunky to me
So I think I will go with an explicit button for scrapping all the time
@skiwi I have been working on the resizable window problem a little bit. What I haven't figured out yet is how to dynamically resize things inside the window. I do have them appropriately anchored
I've seen some hints at how to do it in the documentation but I haven't been able to put it all together yet (anchor panes resizing their children, that is)
> The setup of a game needs to change slightly. It needs to be possible to create a game using a specific random seed. This is also related to #30 and #44
> This is required for making tests fail less. Currently a test may fail because a specific card that is going to be tested is not in the deck (it's 0.1% chance of this happening)
Well I'm hoping to modify the set of cards today. Is there an easy way to determine some sort of probability ratio for the distribution of certain cards (common) as opposed to others (less common)? Or is it completely random right now?
@Phrancis in the code you see there is a for loop now, for (int card = 0; card < CARDS_OF_EACH_TYPE; card++) {
instead of having only one such loop, you can have several different loops. loop x times for some cards to create them, y times for other cards to create them
@SimonAndréForsberg I'm trying to locate the code section we discussed yesterday on github (only have browser access here) can you point me in the right direction please?
It would make more sense if perhaps the scrap value == mana cost?
or maybe scrap value == creature health?
I think that actually would make the most sense... a B0T with higher health/constitution would necessarily have better/more useful parts... make sense?
@Phrancis I don't think it should necessarily be scrap value == mana cost or scrap value == creature health. perhaps scrap value == creature health / 2 would be a good guideline though, but I think that individual setting is the best.
Also @Phrancis would it be possible to create some "goals" of the game? I would want to do automated balance-checks, but I figure a difficult time to figure out what should be checked against
@Phrancis And I still think that the +2/+2 enchantment is too expensive. I think 3 scrap would be enough for that. Although I'd recommend changing the other existing +3/+0 or +0/+3. Although this depends a bit on how the attack system will change.
@skiwi At least I intend to support them in the game code. Whether or not @Phrancis and the game designers wants to add them to their game, I do not know.
I haven't given that much thought into spell cards. I'm trying to get the other designers to play the game first - hopefully today - and see what direction we should go
@Phrancis If Bios should not be scrappable, that configuration will probably leave quite a lot of scrap-shortage. Perhaps change the number of each enchantment cards players get?
I was thinking of just adding more bot variations. Also I'm guessing if one identical line was present twice, it would generate double the amount of that card? Hypothetically
