Volunteers needed for 3 major coding projects!

[TimerClock14]

For the card ideas database:

I have had a basic code going for this using Google Apps Script as the client, so if anyone is interested and knows how to do it, I'd be happy to show you my code. A web-based application would serve much better, however, as GAS-powered applications cannot be supported in the iframe HTML tag.

Send me PM to contact me.

Thank you in advance to all who help!

[UTAlan]

I would gladly integrate my quantum-index.com site into the Resources section of the forum. I threw it up on its own domain just because that's the logical thing to do when I develop a website, but I'm not stubborn about that! Also, what is up there now was just the result of about an hour or so worth of work. I've already started making changes that account for quanta from different marks (and therefore pendulums) and abnormal cards that throw off QI (Devourer, Fractal, etc).

[Scaredgirl]

This topic has been officially resurrected!

[tdog0001]

Both (or all 3 depending on if you include QI calc. with deck wizard) would be a cinch, IMO. Even the hardest/most repetitive parts can be done easily.

For card database:

1.Create a new database + new table with the following cells (key: Full name(DB cell name)

• Name(name)
• Cost(cost)
• Element(element)
• Art link/file name(href/art)
• Active Ability(actabil)
• Passive Ability(pasabil)
• Attack(atk)
• Health(hp)
• Deck Code(code)

2.  Manually add each card via an .sql script or through a DB GUI like phpMyAdmin or something to that effect.

3.  Build base search engine, taking the query, sanitizing it (to prevent injections), and bringing back any results for the specified name matching.

4.  Add additional options to exclude anything not matching the selections.

5.  Make results page, structuring it to not look like crap (With a table, or something better).

6. Make everything pretty with SSI.php and some CSS.

7. Make beta release.

8. Fix bugs that slipped through design phase.

9. Make final release.

Eh, I'm not the best designer around, but I'm very proficient in PHP and playing around with SMF(which was the impetus of learning PHP for me, unsurprisingly :p). With a person or two helping out(if I was to do this), this could be done in a few days(well, aside from 7-9).

For deck wizard, it's really hard on making formulas for computation more than anything. I'll give a whack at making a game plan for it:

1. Once user has submitted script, it explodes it by a ' ' and then searches database for the cards based on card code.

2. It then stores all the info into array(probably something along the lines of  $deck [card code][name/element/cost/etc].

3. Then it loops through everything in the array and gets the info necessary for the formula (This may require adding some stuff to the card database like a 'generator' value to differentiate quanta producers and things like that) and does whatever necessary for that (ie add the total quanta consumption/generation, sorted by element).

4. Finally it performs calculations and gathers results.

5. Create result page.

6. Make it pretty.

7-9. See above.

Eh, for the deck wizard it was simplified a bit too much and I know it's going to be relatively hard, but not anything brain-blowing with a small dev crew. Maybe you should hire a dev crew and get them to start working on this.

Just my on the subject.

fakeedit: oh right this is a volunteer thread. I'll volunteer if needed. Contact me via PM if you want me.

[Camoninja]

I can do some Java and I'd like to do this, even if my version(s) aren't right, just for the experience. I'd have to fit it in with school though, that might be busy. If there is no hurry on this and Java is OK I'll be able to do it eventually.

[UTAlan]

Card Database
Idea: To have all the card images listed based on different criteria that users can change. This way users are not required to go though all the cards to find what they are looking for, which becomes increasingly more important as we get more and more cards.

How it works:
1. Page has ALL the cards listed in alphabetical order as full size images.
2. On top of the page there are several checkbozes and dropdown menus that control how the cards are shown. When the user checks/unchecks those boxes or selects something from the drop-down menu, the card list updates automatically based on these selections. You can change the following settings:
- element (you can choose more than one)
- unupped, upped or both.
- type of card
- rarity
- cost
etc.
3. You can sort your results based on the following criteria:
- card name
- card cost
etc.

Example:
I start off with all the cards in front of me. I want to build a deck that uses the "Growth" ability. I check the ability box "Growth". The card list gets updated to show all the cards that have the "Growth" ability. All other cards are hidden.

http://elements.alanbeam.net/cards.php (http://elements.alanbeam.net/cards.php)

More filters coming shortly, but it's after 2:30am and I have work in the morning, so this will have to do for now. Feedback is welcome.

[Planplan]

The 3 project are more or less linked.
A good and full database is needed to generate good decks, QI need the card database (and maybe some more infos) to compute data, and the deck wizard, as mentioned, need the QI for optimal quanta as well as the database.

[Scaredgirl]

Thanks for everyone who offered to help. As always, we kind of have Coder Wars going on here.

Both (or all 3 depending on if you include QI calc. with deck wizard) would be a cinch, IMO. Even the hardest/most repetitive parts can be done easily.

For card database:

1.Create a new database + new table with the following cells (key: Full name(DB cell name)

• Name(name)
• Cost(cost)
• Element(element)
• Art link/file name(href/art)
• Active Ability(actabil)
• Passive Ability(pasabil)
• Attack(atk)
• Health(hp)
• Deck Code(code)

2.  Manually add each card via an .sql script or through a DB GUI like phpMyAdmin or something to that effect.

3.  Build base search engine, taking the query, sanitizing it (to prevent injections), and bringing back any results for the specified name matching.

4.  Add additional options to exclude anything not matching the selections.

5.  Make results page, structuring it to not look like crap (With a table, or something better).

6. Make everything pretty with SSI.php and some CSS.

7. Make beta release.

8. Fix bugs that slipped through design phase.

9. Make final release.

Eh, I'm not the best designer around, but I'm very proficient in PHP and playing around with SMF(which was the impetus of learning PHP for me, unsurprisingly :p). With a person or two helping out(if I was to do this), this could be done in a few days(well, aside from 7-9).

For deck wizard, it's really hard on making formulas for computation more than anything. I'll give a whack at making a game plan for it:

1. Once user has submitted script, it explodes it by a ' ' and then searches database for the cards based on card code.

2. It then stores all the info into array(probably something along the lines of  $deck [card code][name/element/cost/etc].

3. Then it loops through everything in the array and gets the info necessary for the formula (This may require adding some stuff to the card database like a 'generator' value to differentiate quanta producers and things like that) and does whatever necessary for that (ie add the total quanta consumption/generation, sorted by element).

4. Finally it performs calculations and gathers results.

5. Create result page.

6. Make it pretty.

7-9. See above.

Eh, for the deck wizard it was simplified a bit too much and I know it's going to be relatively hard, but not anything brain-blowing with a small dev crew. Maybe you should hire a dev crew and get them to start working on this.

Just my on the subject.

fakeedit: oh right this is a volunteer thread. I'll volunteer if needed. Contact me via PM if you want me.

This is just a wild guess but I'm guessing this is not the first time you've done something like that. It's great that you offered to help but I think the next guy kind of ninja'd you on that..

Card Database
Idea: To have all the card images listed based on different criteria that users can change. This way users are not required to go though all the cards to find what they are looking for, which becomes increasingly more important as we get more and more cards.

How it works:
1. Page has ALL the cards listed in alphabetical order as full size images.
2. On top of the page there are several checkbozes and dropdown menus that control how the cards are shown. When the user checks/unchecks those boxes or selects something from the drop-down menu, the card list updates automatically based on these selections. You can change the following settings:
- element (you can choose more than one)
- unupped, upped or both.
- type of card
- rarity
- cost
etc.
3. You can sort your results based on the following criteria:
- card name
- card cost
etc.

Example:
I start off with all the cards in front of me. I want to build a deck that uses the "Growth" ability. I check the ability box "Growth". The card list gets updated to show all the cards that have the "Growth" ability. All other cards are hidden.

http://elements.alanbeam.net/cards.php (http://elements.alanbeam.net/cards.php)

More filters coming shortly, but it's after 2:30am and I have work in the morning, so this will have to do for now. Feedback is welcome.

Wow, that's awesome. It's almost identical to what I had in mind. I'll give some feedback. I understand that since it's unfinished, you probably would have done some of these suggestions yourself, but I'll go ahead and give my feedback anyways.

I love the simple and clean layout. Looks very professional.

It might be a good idea to include elemental icons next to element names. You could even try it with icons only, although the text part might help some users. Elements checkboxes could be evenly spaced (spacing not determined by the number of letters) and maybe in two rows to limit horizontal space?

"Upgraded" could be a radiobox because you don't need to choose more than one of those options. I would also rename "all" to "both", have that "both" be default option, and finally move the "both" on the right so it says "yes no both".

"RESET" button next to "GO" button.

One big suggestion I have is make the card images work as links for Wiki card articles. Wiki card articles (most of them written by Kuroaitou) use the card name for url like this: http://elementscommunity.org/wiki/cards-water/arctic-squid-arctic-octopus/ . I'm pretty sure that instead of having to manually add those links, you could dynamically build the url using card element, unupped name and upped name. But if something like that is too much work, then never mind.


That was all I could come up with. None of it is really crucial so take it or leave it.

As always, great work. +rep

[The_Mormegil]

More feedback for you, UTAlan (as SG said, we'll point out useless tiny details that you most likely already know, but whatever, your job is awesome and great).

1) Card code in a box under the image? Since this is not really a deckbuilder, and you might need the code only for the specific card,it might be better that way. Also, if you know how to do that, I think having the boxes auto-select-and-copy the code would be very nice (I saw it in some sites, I don't know if it's impossible or what).
2) Checkbox for showing only names or small images or whatever - faster loading if you don't want the images.
3) Search engine for card name
4) Seach engine for card text (both are nice but not really required as we have a small cardpool, for now)
5) Filter by card type (weapon, permanent, creature etc.)
6) If filter "creature" is on, filter by minimum or maximum attack and hp
7) Put most of the above in an "Advanced Search" spoiler because it's bothersome and mostly useless many times.
8) Order By could have a "By Type" function. Also, a "By Attack", "By Hp", "By Card Cost".

Also, +rep.

[TimerClock14]

Card Database
Idea: To have all the card images listed based on different criteria that users can change. This way users are not required to go though all the cards to find what they are looking for, which becomes increasingly more important as we get more and more cards.

How it works:
1. Page has ALL the cards listed in alphabetical order as full size images.
2. On top of the page there are several checkbozes and dropdown menus that control how the cards are shown. When the user checks/unchecks those boxes or selects something from the drop-down menu, the card list updates automatically based on these selections. You can change the following settings:
- element (you can choose more than one)
- unupped, upped or both.
- type of card
- rarity
- cost
etc.
3. You can sort your results based on the following criteria:
- card name
- card cost
etc.

Example:
I start off with all the cards in front of me. I want to build a deck that uses the "Growth" ability. I check the ability box "Growth". The card list gets updated to show all the cards that have the "Growth" ability. All other cards are hidden.

http://elements.alanbeam.net/cards.php (http://elements.alanbeam.net/cards.php)

More filters coming shortly, but it's after 2:30am and I have work in the morning, so this will have to do for now. Feedback is welcome.

While I'm assuming you're going to put this in, you forgot to have the "Card Ideas" part. But the mechanics of this is very smooth. Much better than anything I had made. +rep

[UTAlan]

It might be a good idea to include elemental icons next to element names. You could even try it with icons only, although the text part might help some users. Elements checkboxes could be evenly spaced (spacing not determined by the number of letters) and maybe in two rows to limit horizontal space?

"Upgraded" could be a radiobox because you don't need to choose more than one of those options. I would also rename "all" to "both", have that "both" be default option, and finally move the "both" on the right so it says "yes no both".

"RESET" button next to "GO" button.

One big suggestion I have is make the card images work as links for Wiki card articles. Wiki card articles (most of them written by Kuroaitou) use the card name for url like this: http://elementscommunity.org/wiki/cards-water/arctic-squid-arctic-octopus/ . I'm pretty sure that instead of having to manually add those links, you could dynamically build the url using card element, unupped name and upped name. But if something like that is too much work, then never mind.

I have made all these changes, sans the Wiki links. I'm currently working on building a relationship between upped and unupped cards so I can dynamically determine the correct link for any given card. Mormegil - I'll get to your suggestions soon. Thanks for the feedback (and rep)!