 |
| groundzero2010 |
Posted: Tue Feb 27, 2018 3:59 am
Increment Variable DB Item |
|
groundzero2010
Novice
Joined: 30 Sep 2004
Posts: 47
Location: Arkansas
|
 Posted: Fri Mar 09, 2018 9:18 pm
|
| Quote: |
It is possible you may have corrupted your package.
Does the Issue persist if you get rid of the original variable and allow it to recreate itself? |
Thats usually how I test, just by deleting the variable and let it recreate. Still has the issue. I'm attempting to copy over somethings to a different character session and adapting it and see if I still get the issue. |
|
|
|
|
groundzero2010
Novice
Joined: 30 Sep 2004
Posts: 47
Location: Arkansas
|
Posted: Fri Mar 09, 2018 9:28 pm
|
| Quote: |
| Try using #DELKEY to get rid of increased, rather than setting it to 0. You are right, it is treating the data as a string... |
I set increased to 0 in the initial trigger to try to initialize that key and value so it could be incremented in the second trigger. Should I not do that? |
|
|
|
|
shalimar
GURU
Joined: 04 Aug 2002
Posts: 4671
Location: Pensacola, FL, USA
|
Posted: Fri Mar 09, 2018 10:08 pm
|
In theory that should work, though there is no need to nest it inside %eval.
The net result is the same.
Which is why i started wondering about corruption. |
|
_________________
Discord: Shalimarwildcat |
 |
|
|
groundzero2010
Novice
Joined: 30 Sep 2004
Posts: 47
Location: Arkansas
|
Posted: Fri Mar 09, 2018 10:29 pm
|
I'll try without. I think I originally started using %eval because I wanted to try forcing it to save as an integer instead of text.
|
|
|
|
|
shalimar
GURU
Joined: 04 Aug 2002
Posts: 4671
Location: Pensacola, FL, USA
|
Posted: Fri Mar 09, 2018 10:53 pm
|
%int is better for that purpose, but 0 should autotype as an integer
|
|
_________________
Discord: Shalimarwildcat |
|
|
|
|
|
|
