palota

I changed goal_combatmovement and committed it to SVN.

AABB region triggers can't be oriented or rotated. They are always aligned to axis. I think it would be easier to use Sphere region trigger which has a center and radius. Trigger regions can't be modified. If you need it, I could add a new function to update region's position. The best approach would be to change goal_combatmovement.gm to automatically disable it near some goals (RIDE, SWITCH, GRENADE...).

Allies have M7. Why do you need it ? Which map is it ? Bots should choose their weapons automatically.

I've fixed another problem and committed it to SVN.

ClassCount is internal property and it should never be used in map scripts. If there are goals for satchel, you should change MinClassCount. Server.MinClassCount[TEAM.AXIS][CLASS.COVERTOPS] += 1; If there are not enough BUILD goals, you should also decrease MinClassCount for engineer. Server.MinClassCount[TEAM.AXIS][CLASS.ENGINEER] = 1;

I've fixed the problem and committed it to SVN. I use this short command to print values: Commands["p"] = function(_params) { ExecCommand("script_run print(" + _params[0] + ")"); }; \bot p Map.liftStatus

What is the error ? Image warbell_12346.jpg does not exist.

Routes to CAPPOINT must start at FLAG goal position. You have to create ROUTE_kegs goal and set its radius large enough to include both "FLAG_axis_gold1" and "FLAG_axis_gold2".

Bots hold JUMP button because there is inwater flag on waypoint UID 110. You have to add a new waypoint between UID 109 and UID 110 (you can use command waypoint_split).

Logs are disabled by default since Omni-bot 0.9. To enable logs you have to set cvar omnibot_logsize. Value is maximal file size in KB.

@ Mateos Route to "DEFEND_Flag_.*" in battery is useless because these goals are immediately disabled after allies capture the flag. All Axis bots run to the CHECKPOINT goal. I tried to manually enable "DEFEND_Flag_.*" and disable CHECKPOINT and then routes with weights work as expected. Some bots go downstairs and some bots go upstairs. @ vargatom Please attach all your waypoint files and share link to your map.

Waypoint flag elevator is wrong.

native12 is making the waypoints of dam_revengev2 and already got the elevator working. He will commit it to SVN after he would finish the waypoints.

Goals for both teams are enabled by Util.EnableGoal. Weapon properties are used mainly for heavy weapons like panzerfaust and flamethrower. That's why they have higher priority so that soldiers prefer their specific goals. If you don't like default priorities, you can change them by SetGoalPriority. Command /bot goal_setproperty weapon weapon_name is used to add a weapon to the list of permitted weapons. Command /bot goal_setproperty weapon clear is used to delete all weapons.

No, it's different file. The RELOAD goal is implemented in omnibot_et.dll. But this problem with medic has already been fixed in version 0.92. Omni-bot 0.83 does not work. Revived bots cannot hit enemies. I tested it now. I stood just in front of a soldier with mobile MG42. I saw him shooting hundreds of bullets, but he did not hurt me. I've recently updated goal_respawn.gm so that engineers can be revived. I think it's a good strategy to keep engineers alive so that they can build and destroy objectives while others are covering them. I've also enabled it for bots that have heavy or sniper weapons.