Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Primalist and Mage Support identification #1

Open
Bamux opened this issue Oct 22, 2017 · 2 comments
Open

Primalist and Mage Support identification #1

Bamux opened this issue Oct 22, 2017 · 2 comments

Comments

@Bamux
Copy link

Bamux commented Oct 22, 2017

I found a solution for the correct recognition of the Primalist and Mage support.

First I deleted Lifegiving Veil from the abilityrole table and added Corrosive Spores. The problem with Lifegiving Veil is that you can already get it with 8 points and Archont (Support) as well as Arbiter (Tank) use this ability and not be recognized correctly as Tank or Support.

For the Primalist I added the ability Hastening Vigor by which a Primalist support can be clearly identified.

My local tests with different logfiles were successful with the changes.

SQL for the changes:

DELETE FROM `prancingturtledb`.`abilityrole` WHERE  `Id`=43;
INSERT INTO `prancingturtledb`.`abilityrole` (`AbilityLogId`, `AbilityName`, `Soul`, `RoleIconId`, `PlayerClassId`) VALUES ('1604872421', 'Corrosive Spores', 'Chloromancer', '2', '2');
INSERT INTO `prancingturtledb`.`abilityrole` (`AbilityLogId`, `AbilityName`, `Soul`, `RoleIconId`, `PlayerClassId`) VALUES ('1692284998', 'Hastening Vigor', 'Mystic', '3', '5');
@hewisaurus
Copy link
Owner

DB Updated on 20171023. Need to add these two to the defaults

@hewisaurus
Copy link
Owner

Reopened as I haven't yet added these two records to the defaults.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants