-
Happy Cataclysm gaming! The long-awaited 4.3.4 Cataclysm Repack V19.0 is now live - and downloadable from our brand-new Emucoach App.
Download it now -
Mists of Pandaria is calling! Heya - did you know that the newest 5.4.8 MoP Repack - version 7.0 - is now live?
Download now
Changelog MoP Premium 7 Version Repack - CHANGELOG LIST | Mists of Pandaria Release | Emucoach
- Thread starter ExO
- Start date
ExO
Admin
- 5,362
- 2014
- 1,982
Hrmm, when does it happen?
- 37
- 2019
- 7
- Location
- france
Hello, thank you for your work, does this mean we can finally manage the equipment for the playerbots in the arena? 
(- After a few feedback queries around this, we have implemented worldserver.conf option to disable Playerbot commands (PlayerBots.RestrictCommandsSecurityLevel) for players. This way it's up to you as a server owner, whether the Players should be allowed to use the Playerbots commands (GMs can still use it if you set it in the config)
- Implemented Playerbot Item level configuration (beta):
You can now fine-tune how strong playerbots are directly from worldserver.conf via gear scaling.
Control the item level of gear bots equip using a global multiplier (PlayerBots.GearScale) and optional per-level-bracket multipliers (e.g. PlayerBots.GearScale.90, PlayerBots.GearScale.80to85, etc.). These stack together, so setting global GearScale = 0.8 and GearScale.90 = 0.9 means level 90 bots get gear at 72% of their normal item level.
You can also cap the maximum gear quality bots can wear with PlayerBots.GearMaxQuality (e.g. set to 3 to limit bots to Rare/Blue gear).
Note: This feature is still in beta and feedback is much welcomed. Extreme gear scale values (especially very low ones) may result in bots having empty equipment slots if no matching items exist at the calculated item level. We recommend making small adjustments and observing the results.)
(- After a few feedback queries around this, we have implemented worldserver.conf option to disable Playerbot commands (PlayerBots.RestrictCommandsSecurityLevel) for players. This way it's up to you as a server owner, whether the Players should be allowed to use the Playerbots commands (GMs can still use it if you set it in the config)
- Implemented Playerbot Item level configuration (beta):
You can now fine-tune how strong playerbots are directly from worldserver.conf via gear scaling.
Control the item level of gear bots equip using a global multiplier (PlayerBots.GearScale) and optional per-level-bracket multipliers (e.g. PlayerBots.GearScale.90, PlayerBots.GearScale.80to85, etc.). These stack together, so setting global GearScale = 0.8 and GearScale.90 = 0.9 means level 90 bots get gear at 72% of their normal item level.
You can also cap the maximum gear quality bots can wear with PlayerBots.GearMaxQuality (e.g. set to 3 to limit bots to Rare/Blue gear).
Note: This feature is still in beta and feedback is much welcomed. Extreme gear scale values (especially very low ones) may result in bots having empty equipment slots if no matching items exist at the calculated item level. We recommend making small adjustments and observing the results.)
gothrock
MoP Premium
- 1
- 2025
- 0
Would be awesome to be able to que for other bgs like SoA and IoC!
The Proving grounds would also be a nice addition. Since it gives titles as well.
Bots will just stop and stand alone in bgs at times. In WSG, they will go under the map at the flag location and are pretty much untargettable. This means they will hold the flag indefinitely sometimes not allowing any more flags carried.
As far as arena, for some reason I've never been able to que for dalaran sewers.
The Proving grounds would also be a nice addition. Since it gives titles as well.
Bots will just stop and stand alone in bgs at times. In WSG, they will go under the map at the flag location and are pretty much untargettable. This means they will hold the flag indefinitely sometimes not allowing any more flags carried.
As far as arena, for some reason I've never been able to que for dalaran sewers.
- 18
- 2021
- 4
When that happens in WSG you can target the member that has the flag and ".die" command them so they drop it, with gm privilege's. ".summon" also works to reset them but you need to be in gm mode to use that, .die is quicker and can be used outside gm mode
ExO
Admin
- 5,362
- 2014
- 1,982
Did you change your account to your MySQL server?
ExO
Admin
- 5,362
- 2014
- 1,982
Are you sure the password was changed properly? Did you try to test by connecting manually via a DB editor to root (username) and ascent (password)? (To verify that the password was properly changed)
Yes. I changed the password back to ascent via HeidiSQL. Closed HeidiSQL. Started HeidiSQL and logged in with root and ascent. Which worked fine and so I proceeded to run the upgrade. However, I got the same error and message. Is changing the password in SQL enough though? This information is also in the *.conf files, as well as, in the launcher app. Do any of these need to be changed too before running the upgrade?
ExO
Admin
- 5,362
- 2014
- 1,982
Is it running on port 3306 and the user is connectable via localhost?
Yessir! In the meantime I have changed all the places where this password is kept and ran the update again. The message did not appear and it went on to migrate the database stuff. However, at some point the update failed again. I tried to start the server, but that now errors too. When I rerun the update, it fails with that same error message.
Attachments
Last edited:
ExO
Admin
- 5,362
- 2014
- 1,982
Do you have Discord? If so, add me on .utilize and I can have a personal look
