What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

issue with grift lvl settings

PokeKoki

New Member
Joined
Aug 4, 2016
Messages
60
Reaction score
0
i play atm @42 i did completed but i can´t select higher lvl in adventure/trinity
annyone knows maybe why?
had same issues with lower levels but after a while it was possible to go higher.
thx in advance
 
Start a game with the bot off. Then open the trinity settings and go to adventurer.
 
Start a game with the bot off. Then open the trinity settings and go to adventurer.

Adventurer will not set higher than 46, even though I have completed 53. Tho it does have the gems at correct lvl.

I started a tier 54 Grift with Bot set off (Start showing); opened Adventurer through the plugins> Trinity> Adventurer and it's still stuck at 46 tier as highest possible.

Following your suggestion did not help :(

>>>>>> EDIT <<<<<<<<

The game crashed with DB so I restarted and now correct tier Grift lvl shows in Adventurer.

So I guess we have to close DB after a new tier has been done. Then restart again and again.
 
Last edited:
Adventurer will not set higher than 46, even though I have completed 53. Tho it does have the gems at correct lvl.

I started a tier 54 Grift with Bot set off (Start showing); opened Adventurer through the plugins> Trinity> Adventurer and it's still stuck at 46 tier as highest possible.

Following your suggestion did not help :(

>>>>>> EDIT <<<<<<<<

The game crashed with DB so I restarted and now correct tier Grift lvl shows in Adventurer.

So I guess we have to close DB after a new tier has been done. Then restart again and again.

Back when Adventurer was a stand alone plugin it required you to enter a game before being allowed to change/view its settings. That is because it needs to be in a game to view your current GR level, acquired gems and gem levels.
Although the merge with trinity means we can access the adventurer settings without being in town/in game/with the bot stopped, the plugin obviously still requires those conditions to be met.
I had the issue everybody is describing too, but with the above in mind it's extremely easy to fix/work around.
 
Back
Top