Raised This Month: $29 Target: $400
 7% 

[TFC] FoxBot coding help


Post New Thread Reply   
 
Thread Tools Display Modes
Author Message
RoboCop
AlliedModders Donor
Join Date: Dec 2010
Location: Dundee, Scotland
Old 07-04-2018 , 15:40   [TFC] FoxBot coding help
Reply With Quote #1

Hello I know this site didn't host nor had FoxBot coders here, but me and my TFC buddies are in need for some bot coding hellp.

What it is I've had to fix some of Zybby's leftover bugs from FoxBot 0.77 and left the project in 2010. I do have some contact with RedFox and Dr Evil but they wish not to get involved with FoxBot anymore.

So far I did manage to fix some errors thanks to Safety1st and Arkshine as well as my testers recently. I've reached to version 0.791 but there are some huge flaws: syntax errors for Assault maps and the bot_job_think.cpp (not included until 0.76 came). However it appears that FoxBot 0.75 had no major bugs until the huge step was taken for advanced features but wasn't properly tested nor fixed.

I had a look on the foxbot.log and it gave me some syntax errors for warpath and dustbowl from 0.791. I don't know if the .far FoxBot area files are corrupt but I suspect it could be a problem with the engine itself:-

PHP Code:
Syntax errorunrecognised command

on_start
 
{
  
blue_notavailable_point1
  blue_available_point2
  blue_notavailable_point3
  blue_notavailable_point4
  blue_notavailable_point5
  red_notavailable_point1
  red_notavailable_point2
  red_notavailable_point3
  red_available_point4
  red_notavailable_point5
 
}

on_msg(#cz_bcap2)
 
{
  
blue_notavailable_point1
  blue_notavailable_point2
  blue_available_point3
  blue_notavailable_point4
  blue_notavailable_point5
  if_red_point1
   
{
    
red_notavailable_point1
    red_available_point2
    red_notavailable_point3
    red_notavailable_point4
    red_notavailable_point5
   
}
 }

on_msg(#cz_bcap3)
 
{
  
blue_notavailable_point1
  blue_notavailable_point2
  blue_notavailable_point3
  blue_available_point4
  blue_notavailable_point5
  if_red_point2
   
{
    
red_notavailable_point1
    red_notavailable_point2
    red_available_point3
    red_notavailable_point4
    red_notavailable_point5
   
}
 }

on_msg(#cz_bcap4)
 
{
  
blue_notavailable_point1
  blue_notavailable_point2
  blue_notavailable_point3
  blue_notavailable_point4
  blue_available_point5
  if_red_point3
   
{
    
red_notavailable_point1
    red_notavailable_point2
    red_notavailable_point3
    red_available_point4
    red_notavailable_point5
   
}
 }

on_msg(#cz_rcap2)
 
{
  
red_available_point1
  red_notavailable_point2
  red_notavailable_point3
  red_notavailable_point4
  red_notavailable_point5
  if_blue_point3
   
{
    
blue_notavailable_point1
    blue_available_point2
    blue_notavailable_point3
    blue_notavailable_point4
    blue_notavailable_point5
   
}
 }

on_msg(#cz_rcap3)
 
{
  
red_notavailable_point1
  red_available_point2
  red_notavailable_point3
  red_notavailable_point4
  red_notavailable_point5
  if_blue_point4
   
{
    
blue_notavailable_point1
    blue_notavailable_point2
    blue_available_point3
    blue_notavailable_point4
    blue_notavailable_point5
   
}
 }

on_msg(#cz_rcap4)
 
{
  
red_notavailable_point1
  red_notavailable_point2
  red_available_point3
  red_notavailable_point4
  red_notavailable_point5
  if_blue_point5
   
{
    
blue_notavailable_point1
    blue_notavailable_point2
    blue_notavailable_point3
    blue_available_point4
    blue_notavailable_point5
   
}
 }

on_msg(#warpath_blue_wins) 
 
{
  
blue_notavailable_point1
  blue_available_point2
  blue_notavailable_point3
  blue_notavailable_point4
  blue_notavailable_point5
  red_notavailable_point1
  red_notavailable_point2
  red_notavailable_point3
  red_available_point4
  red_notavailable_point5
 
}

on_msg(#warpath_red_wins) 
 
{
  
blue_notavailable_point1
  blue_available_point2
  blue_notavailable_point3
  blue_notavailable_point4
  blue_notavailable_point5
  red_notavailable_point1
  red_notavailable_point2
  red_notavailable_point3
  red_available_point4
  red_notavailable_point5
 
}

Syntax errorunrecognised command

on_start
 
{
  
blue_attack
  red_defend
  blue_available_only_point1
  red_available_only_point1
 
}

on_msg(#dustbowl_blue_secures_one)
 
{
  
blue_available_only_point2
  red_available_only_point2
 
}

on_msg(#dustbowl_blue_secures_two)
 
{
  
blue_available_only_point3
  blue_available_point8
  red_available_only_point3
 
}

on_msg(#dustbowl_blue_caps)
 
{
  
blue_available_only_point1
  red_available_only_point1
 
}

on_msg(#dustbowl_red_defends)
 
{
  
blue_available_only_point1
  red_available_only_point1
 

Now even so that FoxBot 0.75 performs better on most of the TFC maps, but they are not compatible with waypoints made for 0.76 or better. Any help or useful suggestions will be great.

FoxBot 0.75 src code:-
https://apg-clan.org/vbdownloads.php...ownloadid=1113

Latest FoxBot 0.791-beta src code:-
https://github.com/APGRoboCop/foxbot
__________________
vBulletin Webmaster Since 2001
RoboCop is offline
Send a message via Skype™ to RoboCop
RoboCop
AlliedModders Donor
Join Date: Dec 2010
Location: Dundee, Scotland
Old 07-16-2018 , 17:44   Re: [TFC] FoxBot coding help
Reply With Quote #2

Update: it appears Linux got a problem due to tchar.h in dll.cpp as that isn't used for Linux. I did try some solution like this, but doesn't appear to have resolved that issue. Any idea's what is causing the bots to not obey properly?

Code:
#ifdef _UNICODE //Fix by Globoss - [APG]RoboCop[CL]
typedef wchar_t TCHAR;
#else
typedef char TCHAR;
#endif
__________________
vBulletin Webmaster Since 2001
RoboCop is offline
Send a message via Skype™ to RoboCop
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -4. The time now is 16:09.


Powered by vBulletin®
Copyright ©2000 - 2021, vBulletin Solutions, Inc.
Theme made by Freecode