There is a checkbox that has just been renamed in 2.50.210 but used to say 'Auto Level Gems', it now says 'Automatically reduce rift level'What this option does is, it looks at your gems and works out what the rift level would be to get 100% chance to upgrade the lowest gem you have (which for most people is going to be a level 1 gem in your stash somewhere). However it will be restricted in how low a rift it can open by the number in the box beside it labelled 'max reduction'. So lets say you have your rift set to 70, max reduction set to 20, and a level 1 gem in your stash. It could then open a rift level 40 (-20 and -10 required for 100% chance).The point being that it would make completing rifts very fast and if you left it running would slowly increase the rift level as all of your gems increased in level.This option has always been OFF by default, but i can see how the label 'auto-level gems' seems like something people would want to enable.
So i renamed it after tony brought the confusion to my attention. Hopefully this new name makes a bit more sense. Glary utilities pro serial 2019. Maybe it should be 'Automatically reduce rift level for gems'? Or one may assume its reducing rift level based on if its too hard or not.Anyway, turn it off except if you're trying to level-up low-level gems.Aside from that there were some bugs with the rift level setting not being saved properly and reverting back to 1. These bugs should be resolved now with 2.50.210 let me know if you're still seeing issues with it.
There is a checkbox that has just been renamed in 2.50.210 but used to say 'Auto Level Gems', it now says 'Automatically reduce rift level'What this option does is, it looks at your gems and works out what the rift level would be to get 100% chance to upgrade the lowest gem you have (which for most people is going to be a level 1 gem in your stash somewhere). However it will be restricted in how low a rift it can open by the number in the box beside it labelled 'max reduction'. So lets say you have your rift set to 70, max reduction set to 20, and a level 1 gem in your stash. It could then open a rift level 40 (-20 and -10 required for 100% chance).The point being that it would make completing rifts very fast and if you left it running would slowly increase the rift level as all of your gems increased in level.This option has always been OFF by default, but i can see how the label 'auto-level gems' seems like something people would want to enable. So i renamed it after tony brought the confusion to my attention.
Demonbuddy Reduce Portal Lvl 4
Hopefully this new name makes a bit more sense. Maybe it should be 'Automatically reduce rift level for gems'? Or one may assume its reducing rift level based on if its too hard or not.Anyway, turn it off except if you're trying to level-up low-level gems.Aside from that there were some bugs with the rift level setting not being saved properly and reverting back to 1. These bugs should be resolved now with 2.50.210 let me know if you're still seeing issues with it.
![Demonbuddy reduce portal lvl 2 Demonbuddy reduce portal lvl 2](https://d2skuhm0vrry40.cloudfront.net/2017/articles/1/8/9/3/6/6/4/149133248696.png/EG11/resize/300x-1/quality/75/format/jpg)
![Portal Portal](/uploads/1/2/3/9/123944552/451111812.png)
![Diablo Diablo](/uploads/1/2/3/9/123944552/263401651.jpg)
You make a second global to determine sort direction and a second calc field. The calc fields have exactly the same thing in them except that they have one extra condition. If the Sort global is null (empty) then the first calc field is populated and the second is empty. If the Sort Global has a value in it, then the second calc field is populated and the first is empty.One you have the two calc fields created, you set one to sort Ascending and one to sort Descending in the Sort order. Depending on the value in the Sort global, one of them will be populated and the other will be null. You can just add a checkbox of Sort global or you can get a little fancier and create a calculated container field that references the Sort global and two additional container fields that hold up arrow and down arrow graphics. Add the calculated container field to the screen and attached a Set Field script step to it that simply switches the Sort Global from null to 1.
Do you mean the global that determines what field you're sorting on? I had forgotten that you were wanting to select the field that the sort is being based on and had a global and calc field for doing that. I would guess that if you are using the same global and calc field to determine the sort order for both portals then yes, both portals would re-sort if you change the sort field.Ultimately, the way most people handle this is with multiple, fixed sort portals and an invisible tab object. It's more work to set it up and to modify it down the line, but it eliminates the slowdown of having the portal resorted because the sort order for each portal is fixed.
You might be able to do it with one TO and the Sort applied at the portal level. I haven't really tested to compare sorting at the Portal vs the TO level.You might check out the Virtual Sort option at.