+++Australia Rocks 2.0+++
Interesting, i had assumed that rune level influenced the base order, I hadn’t made the connection to the matching algorithm, but can see that that would make sense.
I had been assuming that matching was influenced by team score, which may not be the case...guess the only way to know how they do it is for SP to let us know.
I do think the new matching system needs to be reviewed. I believe it’s hurting the teams that are in the top 100 but don’t have that many high level nemesis. There’s clearly a big discrepancy between non nemesis teams and nemesis teams when predicting war outcomes. ( not counting you guys as a nemesis team btw ) This is not inline with the matching algorithm that seems to not put enough weight to this factor. I guess one unfortunate outcome of having such monster imablences.
I also agree that AR and Untamable should have had more battles in the past, as we aren’t that far behind you guys..and the first time we have is when the new matching was in acted. Even so it needs to be reviewed as right now it doesn’t look it’s matching the mid level teams correctly
I believe there is quite a disproportionate gap between the top teams and the mid level teams that the matching algorithm is not taking into account.
Number of monsters -
unless I’m missing something why is this relevant? The number of monsters is seems completely irrelevant when it comes to team score and war matching and should not be included.
MP calculation needs improvement. As we all know all monsters are not equal. In L as a general rule Nemesis >VIP>Standard Ls ... this is not taken into consideration.
As far as I know Rune level is not taken into consideration
Seems a pretty easy fix to MP calculation to put a simple multiple on different classes of L. Also seems pretty easy to add a multiple on rune level, perhaps not on the rune on each monster as these can be changed etc... but a simple ratio of rune level or actual number of runes in each category to monster count with different weighting’s for each rune level would seem to be appropriate. This would then give weighting to the runes in scoring the team.
90 day war coins average.
This seems like a metric one would want, maybe it gets thrown off during the races when teams change..
perhaps a weighted average would be better with the near term battles carrying a larger weight than older battles.
Also seems like race jumping needs to be stopped to make this metric more meaningful, as right now it’s an advantage to change teams.
Thoughts would be appreciated. Right now I am assuming that Team score and matchmaking is somewhat connected.
First testing of the delay tap did produce some unusual and negative results... very inconsistent.
I’ll try and do a little more testing, but so far looks like Oscurs amulet is working and the delay trap is not.
I’m a little wary to even suggest Oscurs amulet is working correctly, just in my testing, which had reasonable coverage, it produced only positive results.
This is quite a shame as monsters with Amulet and Trap relic slots would have quite some fun with both relics fitted.
Greedy, frostbite... I think goldfield as well from memory.
I also must have battled about 50 times now with early and late trigger turn order speed boosts and after the update I haven’t once noticed an unfavorable outcome. This has been done on multiple monsters with 1 Oscurs amulet to 3 Oscurs amulets .. with one triggering at a time to all three triggering in subsequent turn order.
The one thing I did notice is the speed effects don’t stack.. so if 1 2 or 3 are active it simply adds just 1 of them... not sure if it’s the last one that’s applied or the first, as all my Oscurs amulets are level 1
Anyway.. leveling up the beauty now.... I think it might be quite a powerful little amulet given what I’ve seen.....
Bone head error on my part.... Looks like speed trap error I was seeing is attributed to me battling on my phone rather than my iPad, which was not updated.. thought it was.. doh.
The good news is I now have quite an accurate picture of testing with a before and after the update.. same battle, same set up , same turn activation etc.. so can see a true before and after under the same circumstances
Very clear from the testing the issue of turn order, it was quite consistent in its error, given the same turn trigger on the same monster. ... that was before the update.. after the update seems to be working now to the players advantage, if correctly, still not sure, but I’m guessing it is.
Well I’m all updated on all devices now and I’m quite liking Oscurs amulet now .. think I might level it!
PS note to self, don’t battle on a device when traveling that you don’t usually play on
I can confirm the speed traps are still broken, I will do some more testing to see if I can provide some more exacting data, but just used Oscurs amulet, triggered a few turns into the fight..and immediately reshuffled the turn order and I lost the next 2turns that should have been mine.