XNA AI：管理屏幕上的敌人

发布于 2024-10-12 07:25:04 字数 450 浏览 3 评论 0原文

我有两个班级，人类和怪物。

两者都有一个名为 MoveBehavior 的属性

，人类具有 HumanMoveBehavior，怪物具有 MonsterMoveBehavior

我希望 HumanMoveBehavior 远离怪物，而 MonsterMoveBehavior 则向人类移动。

我遇到的问题是我应该将代码移动到哪里？

在人类/怪物类别中？

使用这种方法，我有一个 Move() 方法，它获取游戏中所有实体的列表，使用名为 GetListOfOpponents(List allsprites) 的方法确定它是怪物还是人类，然后运行 GetNearestOpponent(List对手);

但这看起来真的很混乱。

我应该有一个 SpriteController 来决定精灵移动的位置吗？我不确定需要将此代码放在哪里:(

谢谢！

原文

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

缘字诀 2024-10-19 07:25:04

您可以想到一个 AIManager ，它只是说：

foreach(GameObject go in m_myObjects) // m_myObjects is a list of all objects that require updating
{
    go.Update(); // standard GameObject function
}

之后，每个类都应该处理自己的代码片段。所以更新在类本身中起作用。

所以人类说：

// just a class which is a gameObject and also has moving behaviour
// do the same with monster
public class Human : GameObject, IMoveBehaviour
{
    public override Update()
    {
        GoMove();
    }

    public void GoMove()
    {
        // human specific logic here
    }
}

// This interface describes that some movement 
// will happen with the implementing class
public interface IMoveBehaviour
{
    void GoMove();
}

通过使用接口，您可以将特定语言作为类的一部分，并且您不需要还创建一些可以为您处理该问题的类。当然有可能。但在现实生活中，人类/怪物是正在移动的，而不是他携带的某种物体。

更新

对评论的回答。因为有一个 AIManager，甚至一个完整的 GameObjectManager 就可以很好地维护所有 GameObjects，所以你可以询问 AIManager code> 为你不能去的地方。

由于寻路大部分时间是通过使用某些导航网格或指定网格来完成的，因此 GameObjectManager 可以返回包含所有可导航点的特定网格。您当然不应该定义每个怪物的所有位置。因为大多数时候，怪物并不确切知道每个人在哪里（在现实生活中）。因此，知道不该去的地方确实很好，但知道每个人都在哪里，也会给你的人工智能带来太多优势。

因此，考虑返回一个网格，其中包含可以去的点和不可以去的点，而不是将这些东西保留在怪物/人类体内。始终通过思考现实生活中的事物来检查您应该在哪里留下什么。

You could think of a AIManager that just says:

foreach(GameObject go in m_myObjects) // m_myObjects is a list of all objects that require updating
{
    go.Update(); // standard GameObject function
}

After that, each class should take care of its own piece of code. So updating works in the class itself.

So Human says:

// just a class which is a gameObject and also has moving behaviour
// do the same with monster
public class Human : GameObject, IMoveBehaviour
{
    public override Update()
    {
        GoMove();
    }

    public void GoMove()
    {
        // human specific logic here
    }
}

// This interface describes that some movement 
// will happen with the implementing class
public interface IMoveBehaviour
{
    void GoMove();
}

With using an interface, you can make the specific language part of the class and you don't have need to ALSO create some class that will handle that for you. Of course it is possible. But in real life, the human/monster is the one that is moving, not some object he is carrying.

UPDATE

Answer to the comment. Because there is an AIManager, or even a complete GameObjectManager would be nice to maintain all GameObjects, you could ask the AIManager for the placed where you could not go.

Because pathfinding is most of the time done by use of some navigation mesh or a specified grid, the GameObjectManager can return the specific Grid with all navigable points on it. You should for certain not define all positions in every monster. Because most of the time, the monster does not exactly know where everyone is (in real life). So knowing where not to go is indeed good, but knowing where everyone is, will give your AI too much advantage as well.

So think of returning a grid with the points where to go and where not to, instead of maintaining such things inside the monster/human. Always check where you should leave what, by thinking about what would be the thing in real life.

回复收藏 0 原文