Programming using Selection StructureWe start to control $($with control structures$)$ the execution flow of our programs FROM Sequence $-$ executing every statement one after the other $----->$ TO making a decision and choosing $($or selecting$)$ a block of code $\{\}$ to execute and$/$or excluding block$($s$)$ of code from executing.Let's update our Game from last week: EmperialBattleBots.java and create EmperialBattleBotsSelection.javaAs Empires around the globe have consolidated lands and loot through battles and conquests, subjugating principalities and livestock, expanding armories, and hording jewels and treasure, the number of mercenary employers $($Empires$)$ has decreased. The competition for mercenary enlistment has resulted in Imperial conventionalities such that $\%$ loot offered to Mercenaries follows as such:Salaries $0-500-->$ upto$*20\%$ loot optionSalaries $501-1000-->$ upto$*25\%$ loot optionSalaries $1001-2000-->$ upto$*50\%$ loot option Salaries $2001-3000-->$ upto$*75\%$ loot optionSalaries over $3000-->$ upto$*100\%$ loot option$*$upto $\%$ means the max $\%$ a mercenary can negotiate with the Empire they battle for.Level $2$ Game changes:Level $2$ game, base Salary is no longer a NAMED CONSTANT, so be sure it is no longer in ALL CAPSLevel $2$ game, loot percentage has been somewhat taken over by the Empires$[13$ points$]$ Submit ImperialBattleBotsSelection.javaThis weeks Updates to our Game ProgramSalary is input $($variable$)$ value and no longer a constant valueDerive Loot $\%$ percentage available to negotiate based on the initial Salary RangeInput loot $\%$ in range of $0-$ max$\_$percent