Andor's Trail

Repeatedly changing the screen orientation seems to reset the timer for the actor conditions so things like Shadow Regeneration never tick.

I'm not by anything that can poison you right now, but I would assume this method could also be used to prevent poison damage.


DroidX 2.3.3

JohanX wrote:Repeatedly changing the screen orientation seems to reset the timer for the actor conditions so things like Shadow Regeneration never tick.

I'm not by anything that can poison you right now, but I would assume this method could also be used to prevent poison damage.


DroidX 2.3.3

I tested this with Dazed and Weak poison on Blackwater Mountain and i see the same effect. I have had both conditions without having either of them actually go through one round by tilting the phone back and forth over and over again.

The only thing is that because i am tilting the phone i am unable to move easily so i dont see how this would be too much of a advantage.

There's a reason for it, I can't exactly remember off the top of my head but it has to do with Android re-initializing Activities (the visible part of the program) when the orientation changes. I believe Oskar explained it in another post but I can't seem to find it at this point and time.

If the screen orientation changes everything is reloaded from a "savegame". Currently there seems to be only the information in it how many rounds of the Actor Condition are left. (not how many milliseconds of the current round have passed)

It's the same thing that happens if you turn your phone in a shop. (there is only information in the "savegame" about the kind of shop you are in, not about how many items are available.)

I found Oskar's post about it: http://code.google.com/p/andors-trail/i ... ail?id=132

When starting a new Android Activity (such as the view item Activity), the game is actually saved and restored when you return to the game screen. This is similar to what happens if you for example leave to another program on your device, or take a phone call.

Savegames currently only support saving the state between turns.

What would happen if the actor conditions were based on combat rounds and movement steps taken instead of the timer?

JohanX wrote:I found Oskar's post about it: http://code.google.com/p/andors-trail/i ... ail?id=132

When starting a new Android Activity (such as the view item Activity), the game is actually saved and restored when you return to the game screen. This is similar to what happens if you for example leave to another program on your device, or take a phone call.

Savegames currently only support saving the state between turns.

What would happen if the actor conditions were based on combat rounds and movement steps taken instead of the timer?

Interesting. That would remove the standing around to get rid of some conditions since we'd have to move then.

Black Wind wrote:

JohanX wrote:I found Oskar's post about it: http://code.google.com/p/andors-trail/i ... ail?id=132

When starting a new Android Activity (such as the view item Activity), the game is actually saved and restored when you return to the game screen. This is similar to what happens if you for example leave to another program on your device, or take a phone call.

Savegames currently only support saving the state between turns.

What would happen if the actor conditions were based on combat rounds and movement steps taken instead of the timer?

Interesting. That would remove the standing around to get rid of some conditions since we'd have to move then.

Not exactly. Time still goes by even if you are standing still.

Pyrizzle wrote: Not exactly. Time still goes by even if you are standing still.

True, after reading it again, I guess saw the words "movement steps" and forgot about the rounds mentioned only a couple words earlier.

Not sure if that was because I'm all for making things harder or if it was because at first I wrongly thought rounds were movement based.

Black Wind wrote:Interesting. That would remove the standing around to get rid of some conditions since we'd have to move then.

Black Wind, this was correct to what I was thinking about.

Pyrizzle wrote:Not exactly. Time still goes by even if you are standing still.

That is the way it is now, I was proposing a hypothetical on what would happen with a different system.

Black Wind wrote:True, after reading it again, I guess saw the words "movement steps" and forgot about the rounds mentioned only a couple words earlier.

Not sure if that was because I'm all for making things harder or if it was because at first I wrongly thought rounds were movement based.

I was wondering what would happen if rounds were redefined as your character taking X number of steps or Y number of combat turns (Both you and enemy using all AP) instead of the timer based round we have today that has issues with combat and screen orientation.

I'm not even sure if there is a technical way to have whatever timer/counter is used persist through starting a new Android Activity.

I feel that battle sequences should take rounds, so that actor conditions could wear off while in battle, also to make weapons which apply conditions to enemies, such as the barbed dagger: 50% bleeding wounds 5 rounds, could actually effect the battle. a it is now, in order for bleeding wounds to effect a mob, you'd need to flee from battle once the effect were applied, rather than each stack doing the one damage per turn a described in the items stats. just my humble opinion... saving up for a lappy so I can start teaching myself java while at work, so haven't actually gotten to take a look at how hard this would be to implement...