v.0.9.9.5 still force closes

[Braingeyser]

High Luck (>=250) still triggers force closes, as does high Technical (>=125?).  I have only seen the crashes during combat, when attacking (normally or using cards).  Attacking with a battle skill like Fireball does not trigger a crash.

Using the battle skill "Luck+" when my natural stat was on the cusp (249) triggered a crash as well, so it is not just the natural stats that cause the problem.

Times I have NOT seen crashes (mostly just tested with high Luck):

• Fleeing combat, including Rabbit Dash
• Guarding
• Power Guarding
• Encountering Traps
• Using cards in combat to re-equip or use items
• Using attack skills like Fireball and Dark Spear
• Searching
• Using card skills like Combo Up and Power Up
• Descending to a new level
• Stepping onto unrevealed tiles
• Stepping on bombs
• Encountering Guilde

For the purposes of troubleshooting:  I am using a Samsung Moment (or SPH-M900) running Android 1.5.  In the US, if that matters.

[Tomo]

Hi,

First, thank you for providing me this much details!

I have few questions before I try to debug this problem
and would really appreciated if you can answer following questions:

1) Do you get force close repeatedly during the battle?
    If you have reliable way to produce force close(s),
    it would be very helpful if you could tell me how to.
    (for example, do you get force close by just attacking monster? or combo? etc)

2) Do you manage to get that high level/stats by playing V 0.9.9.5 alone,
    (if so, I would love to know how you did it ... I thought I close that loop hole)
    or you loaded previously played version (with loop hole)?


Thank you very much in advance!

[Braingeyser]

1) Do you get force close repeatedly during the battle?
    If you have reliable way to produce force close(s),
    it would be very helpful if you could tell me how to.
    (for example, do you get force close by just attacking monster? or combo? etc)

It is very reliable, very repeatable.  It happens anytime I attack, with or without combos (although not when using battle skill attacks like Fireball) if one of those stats is too high.  It crashes right after it says "Phen attack ______!" or "Phen attack ______ with X hits combo!" and before it shows any damage.  It identifies the process "game.activity."

However, I did realize something: I trigger this bug by using the exploit below; I have only been playing a couple of days, so I don't know what real stats will eventually look like.  If Luck will never reach 250 and Technical will never reach 125 without cheating, I realize this "bug" doesn't actually matter except to cheaters* like me.

(*Well, maybe not cheaters.  Basically, I wanted to explore the game mechanic and understand more about skills and combat and cards and training and Wisdom crafting and such, before I committed to building a character.  I hate making a character only to find out ten levels and two weeks later that I did everything entirely wrong from the beginning.  So when I discovered this loop, I exploited it to take a look around while, basically, invincible.)

2) Do you manage to get that high level/stats by playing V 0.9.9.5 alone,
    (if so, I would love to know how you did it ... I thought I close that loop hole)
    or you loaded previously played version (with loop hole)?

There is still an exploit available allowing unlimited XP, gold, and items.  Do you want me to post it here, or should I send it to you privately? 

[Tomo]

I don't think you are a *cheater*,
(unless you hack the player data in binary editor or something along that line)
and it is really my fault to keep introducing the loop hole.

In the full version, the highest you can get to is ~LV50
and that means it is still possible to reach 50*5 = 250
(very unlikely though - because allocating all level bonus to one stats
 makes this game insanely difficult)

I'm still curious as to why it force close ... it might be strictly because of high stats
(in this case I can probably reproduce it by creating such character)
but could be something else... In order for me to debug this issue properly
it is best to load your play record. Do you think you can zip up all files under
/dungeonwonders/ folder in your SD card and email it to me?
I know I'm asking you a lot but this is how I managed to fix (or I thought I fixed)
the previous issues with high LUCK. Thank you very much in advance
for you help.

2) Oh ... my ... (sigh)
    I think I know how ... I'm at work now and couldn't test it myself but ...
    I think I know how. If it doesn't work, I might send you email and ask you how
    but for now, I think I'm good.

Once again, thank you for providing me this much detail
I'll try to fix all issues that you've reported to me in next release.

[Braingeyser]

In the full version, the highest you can get to is ~LV50
and that means it is still possible to reach 50*5 = 250

Oy.  I went straight to level 120 or 130.


I have sent the files, along with the details of the exploit.

[Tomo]

Wow, thank you very much for quick response.
I'll be very busy this weekend so most likely I will be
looking at this issue early next week. Once I find out
about what is causing the force close, I'll post the detail here.

[Tomo]

Hi,

I loaded play data you've emailed me and just fixed issue.
When player attack, there is a piece of code to check whether
your attack was a technical hit (sort of like critical hit - to increase damage)
and within that logic, what I'm doing was something like:

1) use TECHNICAL and LUCK to get some number
2) 100 - number obtained in 1)
3) use few other parameters to come up with a number (call it *lucky number*)
4) use random generator with number obtained in 2) and see if it is a *lucky number*

when your stats is high, the number obtained in the 2) was negative value
and then force close ... fix was to check for negative value and change the value
to positive.

Thank you very much to report this issue and sending me your play data.
Without your help, this bug is very difficult to reproduce - and sure, you need
very high stats to trigger this problem but still feel great to be able to fix
potential issue. Who know, this might happen in full version and I could be burned
down (by players) for this!