[WIP] Artificial Intelligence Personalities

[myk]

aiPlayer.getAi().getProperty(AIProps.AI_MULLIGAN_THRESHOLD)

+1. this keeps things clean and accessible only from where it makes sense.

[Agetian]

@ Max Mtg, myk: Agreed. Will improve according to suggestions. Thanks!
EDIT: Done.

- Agetian

[myk]

Hey Agetian, I tested the merge from trunk to AIPersonalities, and there aren't any special conflicts with your branch. The same upgrade procedure as trunk applies, though. Would you like me to check in the merge? If you're in the middle of developing something, it would be better if you got that checked in before trunk is merged to the branch.

[Agetian]

@ myk: Yep I had no problems merging with the latest trunk after you've reintegrated your branch. Thanks for the offer to help! I think everything is good so far!

A question for everyone: I've hit another "busy at work" period of time in my life, hopefully not a long one, but potentially I won't be able to develop too actively for a week or two - that being said, the API itself for the AI personalities is fully in place and it's working correctly as far as all my tests have shown. It doesn't do much yet (there's only one property - the mulligan threshold - and no actual stock profiles yet) but the API is usable and can be used by anyone to add new properties (I certainly have lots of ideas and will jump in with them as soon as only possible, but it may have to wait for a while). That being said, what do you think - would you like me to reintegrate the branch into trunk then and then just continue developing there (because for the most part, it's just new properties from here on out, plus linking to the quest metadata if necessary) or continue working in my own branch for the time being and just keep merging until I get a chance to get back to it? I'll do as you say, I think both scenarios are possible.

- Agetian

[myk]

I think letting a branch go unused for a while is a good way to lose the work in it. If merge conflicts build up, it will hamper your ability to get back into its development. Since the "experimental" phase of the branch has passed and you have it tested, I'd vote for merging it now and expanding it later.

[Sloth]

A question for everyone: ... what do you think - would you like me to reintegrate the branch into trunk...

Yes, please merge.

[Chris H.]

I too think that merging the branch back into the trunk would be a good idea.

[Agetian]

OK, since there were only votes for the reintegration, I've reintegrated the AIPersonalities branch into trunk.
So far:

The primary API for AI personalities is now in place. AI properties are implemented in forge.game.ai.AiProps and are retrieved via a call to one of AiController.getProperty, AiController.getIntProperty, or AiController.getBooleanProperty depending on the type of property. The basic getProperty returns data of type String, getIntProperty returns an int and getBooleanProperty returns a boolean. The AI controller can be retrieved via a getAi() call on the AI player object, so that a certain property AI_MY_PROPERTY can first be implemented in an enum in AiProps (the default value is specified as a string):

Code: Select all

AI_MULLIGAN_THRESHOLD("5"),
AI_MY_PROPERTY("false")


and then retrieved via a call to (assuming that "aiPlayer" is the AI player object, and taking into consideration that it's meant to be a boolean property):

Code: Select all

boolean myAiProp = aiPlayer.getAi().getBooleanProperty(AiProps.AI_MY_PROPERTY);


Each property can be assigned on a per-profile basis in res/ai/*.ai profile files. A profile can be selected in the game properties. Two random profile options exist and can be selected - the default one selects a random profile for each AI player the moment the match starts (but the profile stays the same during the entire match for all duels). The second option, called "Random Profile (Duel)", makes the game choose random profiles for all AI players for each duel in a match, making your opponents completely unpredictable.

For an example implementation of a working AI property (of type int), see AI_MULLIGAN_THRESHOLD implemented in AiProps and retrieved in ComputerUtil.

Currently there is one property only, but more are on the way - I'll get back to coding them as soon as I resolve this business project I have on my hands (and I'll try to code a bit even during these days, too). Everyone is also free to expand as necessary. Specific AI profiles for specific quest opponents will be implemented at a later date.

P.S. If someone knows how to delete a branch on the SVN, please do it, it's safe to remove branches/AIPersonalities.

- Agetian

[myk]

branch removed. Thanks for getting this framework started!