New attacker agents are always random agents in the MAL GUI

[sandorstormen]

When creating new attackers in the GUI, remove the attacker type or allow it to be set.

[mrkickling]

We could easily change it to nothing or PassiveAttacker, but it would be nicer to be able to set the policy on an attacker.

[sandorstormen]

Nothing feels better as default

[mrkickling]

The idea was that if you create a scenario and then run it in a simulator, something would happen at least.

So we should:

• Add ability to set the attacker policy when creating an attacker agent in the mal-gui.
• Default to no policy.

[sandorstormen]

The idea was that if you create a scenario and then run it in a simulator, something would happen at least.

Who is going to do this? I use the scenarios for machine learning. I never have an attacker type.

[mrkickling]

The simulator is not only meant for training agents using ML. The idea is that it could also be used to find attack paths using different types of heuristics. But I see your point that defining attacker policy doesn't make much sense for attacker training. It does make sense for defender training though.