指导构建 iPhone 卡牌游戏
我曾接触过构建 iPhone 应用程序，但之前从未尝试过构建游戏。我正在尝试构建一款纸牌游戏（不像扑克、二十一点等），更像是快速纸牌，玩家一次会看到一张纸牌。玩家选择卡上的一个选项，该卡将被放回堆栈中并被新卡取代。 我需要一些指导，并且有一些问题：
有示例吗？我研究了 GeekGameBoard，但那更像是 52 张牌的游戏。对于我的游戏，该卡占据了整个屏幕，并被堆栈中的新卡取代。
我可以使用 Gamesalad 或 Cocos2d 更快地构建这样的东西吗？由于我必须有一些动画和游戏逻辑，我想知道这是否能帮助我更快地完成一些常见的事情。
一般来说，卡牌游戏数据交互的最佳实践是什么？玩游戏时使用 CoreData 还是 plists？
I have some exposure building iphone apps but have never tried to build a game before. I am trying to build a card game (not like poker, blackjack etc.) more like quick cards where player will be presented with one card at a time. Player selects an option on the card and that card is put back in stack and is replaced by a new card.
I need some direction going about it and I have some questions:
Is there an example out there? I looked into GeekGameBoard but that is more like the 52 cards game play. For my game, the card occupies the whole screen and is replaced by a new one from the stack.
Can I use Gamesalad or Cocos2d to build something like this faster? Since I would have to have some animation and game logic, I am wondering if this will help me do some common stuff faster.
What is the best practice for data interaction for card based games in general? Use CoreData or plists as the game is played?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
不知道，如果你真的需要一个例子，也许你应该回想一下你需要什么，写下算法和数据结构等等......
这实际上取决于你的想法... CoreAnimation 可以让你在这类游戏中走得更远，但如果你想要一些非常丰富的东西（想想复杂的动画、音乐+声音、特效粒子，诸如此类的东西），你最好使用 Cocos2d。
我认为 CoreData 对于这类东西来说太过分了。如果你真的很熟悉的话，也许吧。我可能会创建一些类来处理这个问题，想想 MVC 模式中的模型。
Don't know, if you really need an example, maybe you should think back on what you need, write down algorithms and data structures, etc...
It really depends on what you have in mind... CoreAnimation can get you quite far for that kind of game, but if you want something really rich (think complex animations, music + sound, particles for special effects, things like that), you'd be better off using Cocos2d.
I would think CoreData is overkill for that kind of stuff. If you're really familiar with it, maybe. I'd probably create some classes to handle that, think Model in a MVC pattern.