The hardest thing is coming up with the topic which is why I sometimes have the "top 10 cards" because I have no idea what to write about.
Please tell me what kind of things you want to read.
--mtgrares
Subscribe to:
Post Comments (Atom)
I started Forge, which is an open-source, free project that lets you play Magic: The Gathering against the computer. Currently other people are updating Forge and there will be no more posts to this blog.
Posts
13 comments:
Talk about Scars of Mirrodin. Top 10 cards :P
Talk about the types of decks the AI tends to fair better utilizing.
Boring but informative: Talk about Forge handles memory management (and its weaknesses such as when you generate lots of tokens). You never know when some skilled onlooker hops on board to provide some helpful input!
Talk about what cards you're working on, what problems you're having, continue to muse on 2.0 and let us comment leaving people shoot the ideas down or talk them up.
I think you're having trouble coming up with topics because you're afraid of boring us.
Most of the people that are going to be reading your updates are probably programmers, or at least interested in programming, and all obviously in love with MTG. By that I mean that nothing you can say in an update is going to be something that we don't want to read. :D
I second what second Anonymous said...
PS: As for lots of tokens. With a life gaining deck and Storm Herd I've managed to put 1240, 1/1 Pegasus Tokens into play, after that the game got a little slow...
"Talk about the types of decks the AI tends to fair better utilizing."
Creature decks and cards/abilities that don't have a downside. Shock is all good and doesn't have a downside while Wrath of God is great but the AI has a hard time knowing when it should play it. The AI isn't good with strategtic cards/abilities.
I hope that helps.
Tokens aren't really bad but static abilities like Glorious Anthem plus tokens would result in slowdown. The good news is that this situation has been improved but isn't solved.
Thanks for the suggestions.
What I'd really like to read would be a step by step-tutorial on how to add cards.
I would love to contribute and make Forge bigger, but I'm really too dumb for this and I guess others are as well.
Imagine if everyone would be possible to add cards by reading your tutorial, Forge would grow very fast.
I guess that would be a lot of work and I really don't want you to get stressed too lot by Forge.
On the other hand I really am with second Anonymous.
Anyways, I'm going to read what you'll write next monday. See you then. ^^
Here are my suggestions:
- Your most memorable games against the Forge AI.
- How to start programming a magic rules engine.
- Discussions about decks that can be build in Forge.
- Other projects you may working on.
- Programmers stuff in general, like the do's and dont's of programming.
I hope that gives you some inspiration for new subjects.
Articles I'd like to read:
- What are the strong points of forge compared to other similar applications. You often talk about the weaknesses of Forge, and rarely about some of it's cool specificities (you could talk in detail about the quest mode, etc...)
- you could also have some "guests" writing about what they're working on, such as the other devs working on Forge with you now
- I would also love to see a detailed technical article about the structure of Forge. What classes do what, how they interact with other classes, etc...
Thanks for the suggestions wololo. (Wololo works on his own Magic project Wagic.)
I agree with previous posters that there is no subject too technical or boring really. Even us non-semi-coders are interested in the technical aspects. If the specifics are lost on us we can certainly get a grasp on the overarching themes.
I'd like to read about drafting in Forge. How does the AI pick cards and how could the drafting AI get better? (They never play artifacts, enchantments or planeswalkers for some reason, etc)
I saw some pretty clever ideas on the forums about how drafting could be improved, and it was a really interesting read. Could definitely be turned into an article (or a whole bunch of them).
Post a Comment