mirror of https://github.com/mod-playerbots/mod-playerbots synced 2025-11-29 15:58:20 +08:00

Files

Bobblybook 312c661311 Preferred mount selection for bots

Added a new table to store user-specified mount ids.
Can specify flying and ground mounts for a character which will prioritise that mount. If multiple entries, a random entry will be selected from that list.

Currently no way to add entries other than manual DB editing, but can be developed into a whisper command pretty easily.

This should gracefully fail (if no entries exist for the character, or the db table does not exist) and fallback to the default random selection as usual.

2024-10-19 22:40:26 +11:00

characters

Minor correction in logging text and removed in_use from the playerbots_names table and added an additional index for the fallback

2024-08-21 19:34:26 +00:00

playerbots

Preferred mount selection for bots

2024-10-19 22:40:26 +11:00

world

Fix corrupt item cache crashes, bot whispers, trade crashes

2022-03-22 11:04:21 -06:00

README.md

Initial commit - mod-playerbots

2021-12-30 17:13:09 +01:00

README.md

NEW MODULE - SQL BEST PRACTICES

Create a new table

Example:

CREATE TABLE IF NOT EXISTS `table`(
  `id` int(11) unsigned NOT NULL,
  `column` smallint(6) unsigned,
  `active` BOOLEAN DEFAULT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

Boolean datatype in mysql: Use TinyInt(1) or Boolean (this is the same thing)

bit(1) can also work, but it may require a syntax like b'(0) and b'(1) when inserting (not sure).

If there are multiple booleans in the same table, bit(1) is better, otherwise it's the same result.

Rules

Use InnoDB as engine for dynamic tables (most likely in the auth and characters databases).
Use MyISAM for read-only tables (in world database), but if you're not sure, just use innoDB.
Use utf8 as charset.

Resources

https://www.w3schools.com/sql/sql_datatypes.asp