-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Otter randomly giving stats not recorded #32
Comments
For me, it gives +1 attack +1 defense to a random member in the team before buying:
after buying:
This is because sapai hasn't been updated. Is this the issue or is the effect not recorded at all? |
For training this is perfectly fine. The problem has to do with deployment with the actual game. We just have to catch which animal the otter gave the stats point. The issue was the stats giving, not the amount of attack/health. It is probably +1/+1. I dont recall. But I will update to the latest version of SAP tomorrow. Cant update to the latest sapai until sapai-gym is made compatible with it. |
oh I understand, the random pet the otter gave stats to in the actual game and in sapai is different. |
Yes, this is absolutely not trivial. There are also other pets that have similiar complex behaviour. I think for now, I would not spend a lot of time on that. Now I think is the time to improve the reward system and RL algorithm, as I believe the deployment method is working fine enough. It would also be great to support freezing of objects, but currently We would also need to handle that in the machine vision system somehow. For instance the template matching method might fail if an animal is frozen. More tuning to be made.
I like that idea. Seems a lot more seemless. If you are interested, you can also contribute to the machine vision system. Up to you what you prefer working on :) |
Yes, I am interested in contributing to the machine vision system. I will start once I finish what I am working on currently. |
Looking forward to it :) I will have more time this weekend to contribute. I guess I will start playing around with the reward system, but would be great if we were multiple people testing ideas here, as it really is not trivial. |
@GoldExplosion Oh!! That's great!! And as you said, this can easily be added through template matching. But the machine vision system seems to know quite well which animals are in the item shop. It knowns the initial state and tracks all actions where it updates the team. I believe the team and team order should be available in the engine, at all times, or was there something else you were thinking about? |
you are right @andreped. The team should be available in the engine at all times. But if suppose you have to restart the engine in the middle of the game then you have to restart the game also because the engine doesn't the current team and steps taken to get there. We also cannot make switch between manual and AI. We can overcome this by using computer vision system to detect the team and other state information(wins, rounds, gold and health). On a different note, another use is that we can now get teams that we play against. With this we make a database of teams the AI has played against, potential leveraging it for future training. |
Yes, then I agree. For now, I have not taken that scenario into account, but that could easily be done, as you mentioned. However, we would have to update the current team and statuses to the engine. Should be possible. However, improving the reward system is more urgent. I have no time this week to work on this project, but should have more time next week. It is nice to build up a database, sure. However, it would be great if we didn't need "real games" to make a good AI ;) Right now, the AI does not seem to be that intelligent - I blame the reward system being too simple. |
ok got it. Take your time.
I see. makes sense. |
During deployment, when buying the otter, it will give +2 attack +1 defence to a random member in the team. This is not recorded in the team.
The text was updated successfully, but these errors were encountered: