next »

[MordyT]

Hi,
Have a customer who wants to run version 1.7 of B3. No issue I thought. Used the "Bleeding Edge" (which I think grabs it straight off of github) and grabbed the latest version. Unzipped and replaced his files... Fired up the bot and it says it is running version 1.6

Is there another link for 1.7?
Game is BFBC2

[Courgette]

you can get it off my github repo, branch "1.7-dev".
Note that this a work in progress and the code changes almost daily

[xlr8or]

Also note that bleeding edge is currently holding code for the upcoming release of B3 version 1.6.0 which is eminent.

Be careful if you want to use that code for Homefront servers, since the repo is holding code which will only work after the homefront server is patched to version 1.0.4x. This version is as of yet not released! We are waiting for the homefront patch to release our B3 v1.6.0 packages.

In other words, current code in our bleeding edge repo is not working for the current homefront version! It will work after the homefront patch is deployed by Kaos.

[MordyT]

@Courgette, Thank you for the link.
@XLR, that is good to know. This user has a BC2 server and needs the latest version so he can run the latest poweradmin.

Thanks for you help.

[MordyT]

Slight question..

B3 runs fine 1.6.0 but not 1.7.0

It appears B3 has new tables in v 1.7.0 then it had in 1.6.0...

Doesn't B3 update the db automatically? Or does it need to be done manually?

[Courgette]

yes, new table in 1.7
the automatic database update is now removed as it is the origin of issues with MySQL from v5.5.

There is no update sql script yet as the 1.7 branch is a work in progress. Executing the following sql query should be all you need to update your db :

Code: sql

CREATE TABLE IF NOT EXISTS ipaliases (
  id int(10) unsigned NOT NULL auto_increment,
  num_used int(10) unsigned NOT NULL default '0',
  ip varchar(16) NOT NULL,
  client_id int(10) unsigned NOT NULL default '0',
  time_add int(10) unsigned NOT NULL default '0',
  time_edit int(10) unsigned NOT NULL default '0',
  PRIMARY KEY  (id),
  UNIQUE KEY ipalias (ip,client_id),
  KEY client_id (client_id)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

[MordyT]

yes, new table in 1.7
the automatic database update is now removed as it is the origin of issues with MySQL from v5.5.

There is no update sql script yet as the 1.7 branch is a work in progress. Executing the following sql query should be all you need to update your db :

Code: sql

CREATE TABLE IF NOT EXISTS ipaliases (
  id int(10) unsigned NOT NULL auto_increment,
  num_used int(10) unsigned NOT NULL default '0',
  ip varchar(16) NOT NULL,
  client_id int(10) unsigned NOT NULL default '0',
  time_add int(10) unsigned NOT NULL default '0',
  time_edit int(10) unsigned NOT NULL default '0',
  PRIMARY KEY  (id),
  UNIQUE KEY ipalias (ip,client_id),
  KEY client_id (client_id)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

Thanks, I will try this. When you say it was the origin of issues, what do you mean?

2 questions:
1) If updating from 1.50 to 1.6.0 when it comes out, will 1.6 update to utf8 as needed now? I assume no... very sad..

2) If enabling xlrstats on future builds, will it create the correct tables? I assume no, but..

I have a guess as to what the issue was and how the update script caused it (the locked tables?) I just want to confirm.

ALSO, is it possible to have a dev version that DOES update it - so when updating I could run that and when done the user can use the regular version?

[Courgette]

issues with MySQL 5.5 -> http://forum.bigbrotherbot.net/xlrstats/xlrstats-not-running-correctly-on-mysql-5-5/msg23589/#msg23589 (there are 2 or 3 topics about this already, I suppose this is because latest ubuntu ships with MySQL 5.5)

1) hum... you'd better update to 1.6 first

2) B3 1.6 comes with a new command line parameter ( --update ) which purpose is to update the database

[Courgette]

I've updated the 1.7a code to include the database update.


In the end, to update to B3 1.7a, follow those steps :

• backup your B3 files and database
• update B3 files with the new ones (from my 1.7-dev branch)
  
• run the update command : b3_run.py --config <your config> --update
• run the bot as usual

[MordyT]

Your awesome. Don't know if anyone every told you that. Awesome.