user shops: not sure how needed this one is, the only difference being someone can POST the amount they wish to offer a card for...if this is the case then i would need more slots for data. right now when someone who isnt you views your inventory, they can select some of your cards, and offer you points for them, and you accept/deny. basically this is what would happen in a user shop anyway, so this idea needs some thorough explanation
all the new rules should be feasible to some extent
Note for minimum:
I left this out because i figured why would someone complain if their opponent chose sucky cards? Just an easy win. Also, when you choose reverse, the card cap becomes a level minimum already
different board sizes would require an enormous recode. everything from the rulecheckers to the ai to the saving system, depend on everything being nine slots. now, the rulecheckers and the ai have a set of directions they can read from, but i dont know the extent of changes this would require
same thing with multiple players, and yeah figuring out a winner system would be considered a challenge :-p
There is a way to add new elements, as i decided against a formal method of it before, simply because there was no need to
Code:
1) create your image, in a large format in the middle of a clear gif 105x130. (For examples, look i your images/triad/elements folder)
2) SELECT MAX(element) FROM triad_card
3) Add 1 to this, and make that the new name of your element, remember what it was, and put the image in with the other elements. If you never added elements before, this number would be 9.
4) In include/functions_triad.php find:
'8' => 'Holy'
add after it
, '#' => 'NewElementName'
Noting the comma. # is the number you named the element
5) Create your card as usual, and select the new element for it. The game will take care of the rest :)
Well, I could possibly allow you to specify a source directory, but there is really no way around at SOME point you having to go through each and every image to do something. simply because php cant read what are on images, so you would have to do that yourself. Also the cardid isnt known until the card is actually saved in the database, so it wouldnt know which image belongs to which cardid after the fact. To make it easier for the system to recognize the connection would STILL require you to have previously gone through and say named each image as something indentifyably different :-p