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

FallenDev Act1 Profile

a1 totally is very dangerous i think

you need a lot of EHP, much more that for a3

1. no avoidance from Grotesque exploding
2. no avoidance from poison flowers
3. no avoidance from bull's charge

i usually have, for example, 4 death per hour with a1 and 1 death per hour with a3 profile (mostry by fallen maniacs)
 
Last edited:
a1 totally is very dangerous i think

you need a lot of EHP, much more that for a3-2-4

1. no avoidance from Grotesque exploding
2. no avoidance from poison flowers
3. no avoidance from bull's charge

i usually have, for example, 4 death per hour with a1 and 1 death per hour with a3 profile (mostry by fallen maniacs)


You are extremely crazy if you think Act1 is more dangerous then Act 4 or even act 2 with the wasps. Download the newest Trinity, and up your avoidance.
Also get better gear, you should be sitting at 800+ Resist All. My Demon Hunter that has 500 Resist All does not die, and he's under geared. Also
this does not pertain to my profile set so please do not troll this thread. Thank you.

~Fallen
 
ye i was wrong about a4 and a2
but A3 better with DPH
dunno

tell me you stats from d3rawr?
just ehp and dps

i have

Damage: 244299.81
Effective Health: 215609



Download the newest Trinity, and up your avoidance.

i dont write smthing if i donk know it
this threereason of death not presented in trinity :o
 
Last edited:
My stats are uploaded on Act3's Thread, I have a photo there that you can look at.

i dont write smthing if i donk know it
this threereason of death not presented in trinity

TreeSap avoidance and others were updated in the last Trinity, with wait timers and such.
The next trinity will be even more advanced. Just keep it updated, rrrix works hard on it.
 
Here is my wizard with all the buffs activated.

I crit 600k - 1.4m

Wizard.webp
 
Act 1 is extremely hard at times, the poison from the trees is very powerful, obviously I am speaking MP7+ but even on lower MP's it can be quite harsh.

@quadrotony - I suggest really increasing your EPH, 215k is quite low, specially if you're lacking other decent defensive stats.
 
my demonhunter

Damage: 591575.78 (using sharpshooter)
Effective Health: 304149

2-4 deaths at mp8
85m/h
4-6 legs/h
 
Weep n Misery profile is just running weeping hollow over and over again from my experience.

everything else is looking great so far. Thanks for all the hard work FD.
 
===== Misc Statistics =====
Total tracking time: 10h 42.00m 5s
Total deaths: 6 [0.56 per hour]
Total games (approx): 0 [0.00 per hour]
(your games left value may be bugged @ 0 due to profile managers/routines etc., now showing games joined instead:)
Total games joined: 2 [0.19 per hour]
Total XP gained: 2.40 million [0.22 million per hour]

===== Item DROP Statistics =====
Items:
Total items dropped: 6847 [639.81 per hour]
Items dropped by ilvl:
- ilvl58: 395 [36.91 per hour] {5.77 %}
- ilvl59: 199 [18.60 per hour] {2.91 %}
- ilvl60: 1000 [93.44 per hour] {14.60 %}
- ilvl61: 2316 [216.42 per hour] {33.83 %}
- ilvl62: 1868 [174.55 per hour] {27.28 %}
- ilvl63: 1069 [99.89 per hour] {15.61 %}

Items dropped by quality:
- White: 2285 [213.52 per hour] {33.37 %}
--- ilvl 58 White: 112 [10.47 per hour] {1.64 %}
--- ilvl 59 White: 60 [5.61 per hour] {0.88 %}
--- ilvl 60 White: 257 [24.02 per hour] {3.75 %}
--- ilvl 61 White: 745 [69.62 per hour] {10.88 %}
--- ilvl 62 White: 662 [61.86 per hour] {9.67 %}
--- ilvl 63 White: 449 [41.96 per hour] {6.56 %}
- Magic: 3213 [300.24 per hour] {46.93 %}
--- ilvl 58 Magic: 194 [18.13 per hour] {2.83 %}
--- ilvl 59 Magic: 104 [9.72 per hour] {1.52 %}
--- ilvl 60 Magic: 522 [48.78 per hour] {7.62 %}
--- ilvl 61 Magic: 1116 [104.28 per hour] {16.30 %}
--- ilvl 62 Magic: 842 [78.68 per hour] {12.30 %}
--- ilvl 63 Magic: 435 [40.65 per hour] {6.35 %}
- Rare: 1331 [124.37 per hour] {19.44 %}
--- ilvl 58 Rare: 88 [8.22 per hour] {1.29 %}
--- ilvl 59 Rare: 35 [3.27 per hour] {0.51 %}
--- ilvl 60 Rare: 220 [20.56 per hour] {3.21 %}
--- ilvl 61 Rare: 453 [42.33 per hour] {6.62 %}
--- ilvl 62 Rare: 361 [33.73 per hour] {5.27 %}
--- ilvl 63 Rare: 174 [16.26 per hour] {2.54 %}
- Legendary: 18 [1.68 per hour] {0.26 %}
--- ilvl 58 Legendary: 1 [0.09 per hour] {0.01 %}
--- ilvl 60 Legendary: 1 [0.09 per hour] {0.01 %}
--- ilvl 61 Legendary: 2 [0.19 per hour] {0.03 %}
--- ilvl 62 Legendary: 3 [0.28 per hour] {0.04 %}
--- ilvl 63 Legendary: 11 [1.03 per hour] {0.16 %}

5/25/2013 1:56:52 PM: Original Destination=<764.5125, 596.1276, 11.366>. Current player position when stuck=<761.3881, 603.662, 0.1>
Profile Name=Fallen Scavenger's Den
5/25/2013 2:04:17 PM: Original Destination=<285, 720, 20>. Current player position when stuck=<441.9142, 718.8792, 20.1>
Profile Name=Fallen Festering Woods
5/25/2013 2:26:01 PM: Original Destination=<409.9431, 635.9089, 3.139971>. Current player position when stuck=<412.1384, 634.2499, 3.624445>
Profile Name=Fallen Highlands
5/25/2013 3:25:35 PM: Original Destination=<590, 1062.5, 0>. Current player position when stuck=<728.9379, 1028.874, 0.09999999>
Profile Name=Fallen Agony 2
5/25/2013 3:28:30 PM: Original Destination=<2950, 1910, 0>. Current player position when stuck=<2859.805, 1986.284, 0.4263772>
Profile Name=Fallen Weeping Hallow
5/25/2013 4:07:24 PM: Original Destination=<272.0601, 176.29, -2>. Current player position when stuck=<272.128, 176.51, -2.522583>
Profile Name=Fallen Festering Woods
5/25/2013 4:26:06 PM: Original Destination=<382.665, 656.2692, 3.239971>. Current player position when stuck=<392.1202, 641.9905, 3.239972>
Profile Name=Fallen Highlands
5/25/2013 4:28:58 PM: Original Destination=<342.5, 642.5, 3.139973>. Current player position when stuck=<320.6861, 629.7496, 3.363334>
Profile Name=Fallen Highlands
5/25/2013 4:32:48 PM: Original Destination=<272.0601, 176.29, -2>. Current player position when stuck=<272.0628, 176.2996, -2.393439>
Profile Name=Fallen Festering Woods
5/25/2013 4:52:04 PM: Original Destination=<369.3902, 634.3372, 5.616472>. Current player position when stuck=<367.5085, 648.5802, 3.239971>
Profile Name=Fallen Highlands
5/25/2013 5:15:10 PM: Original Destination=<308.5675, 613.4154, 0>. Current player position when stuck=<315.532, 593.0331, 0.543038>
Profile Name=Fallen Scavenger's Den
5/25/2013 5:36:42 PM: Original Destination=<2112.5, 1805, 0.01909208>. Current player position when stuck=<2084.571, 1868.815, 0.1863254>
Profile Name=Fallen Fields of Misery
5/25/2013 5:41:16 PM: Original Destination=<872.5, 590, 0>. Current player position when stuck=<799.2841, 593.1551, 0.09999999>
Profile Name=Fallen Scavenger's Den
5/25/2013 5:50:41 PM: Original Destination=<1970, 640, 0>. Current player position when stuck=<1843.856, 695.5743, -0.2171496>
Profile Name=Fallen Fields of Misery
5/25/2013 6:13:35 PM: Original Destination=<370, 627.5, -3.366206>. Current player position when stuck=<320.2577, 627.4114, -6.387152>
Profile Name=Fallen Decaying Crypt
5/25/2013 6:24:41 PM: Original Destination=<1042.5, 1107.5, 0>. Current player position when stuck=<1043.993, 1108.092, 0.1000001>
Profile Name=Fallen Agony 2
5/25/2013 7:00:42 PM: Original Destination=<622.6243, 435.9314, 9.175852>. Current player position when stuck=<622.6072, 435.9601, 0.1>
Profile Name=Fallen Scavenger's Den
5/25/2013 7:32:49 PM: Original Destination=<2160, 805, 0>. Current player position when stuck=<2103.564, 746.9119, 0.1>
Profile Name=Fallen Fields of Misery
5/25/2013 8:04:58 PM: Original Destination=<272.0601, 176.29, -2>. Current player position when stuck=<272.1201, 176.4849, -2.507121>
Profile Name=Fallen Festering Woods
5/25/2013 8:19:22 PM: Original Destination=<2080.787, 604.0875, -2.950492>. Current player position when stuck=<2083.069, 610.0339, -2.422441>
Profile Name=Fallen Scavenger's Den
5/25/2013 8:46:22 PM: Original Destination=<576.9863, 764.0355, 9.730615>. Current player position when stuck=<577.1303, 763.9198, 0.1>
Profile Name=Fallen Scavenger's Den
5/25/2013 9:15:25 PM: Original Destination=<590, 957.5, 20>. Current player position when stuck=<583.4512, 957.4147, 20.1>
Profile Name=Fallen Festering Woods
5/25/2013 9:31:59 PM: Original Destination=<812.2009, 762.5164, 8.706129>. Current player position when stuck=<813.7009, 762.0923, 0.1>
Profile Name=Fallen Scavenger's Den
5/25/2013 10:15:37 PM: Original Destination=<2041.534, 902.8871, -4.015403>. Current player position when stuck=<2038.967, 903.1157, -3.866634>
Profile Name=Fallen Scavenger's Den
5/25/2013 11:10:37 PM: Original Destination=<454.7096, 609.8162, 3.239976>. Current player position when stuck=<443.7934, 612.2817, 3.239976>
Profile Name=Fallen Highlands
5/25/2013 11:14:10 PM: Original Destination=<371.9756, 694.0159, 3.239971>. Current player position when stuck=<370.962, 711.1496, 3.239971>
Profile Name=Fallen Highlands
5/25/2013 11:22:42 PM: Original Destination=<702.5, 820, 0>. Current player position when stuck=<748.9423, 788.9439, 0.1>
Profile Name=Fallen Agony 2
5/25/2013 11:37:05 PM: Original Destination=<341.5901, 658.5814, 3.157242>. Current player position when stuck=<345.6891, 673.5679, 3.239972>
Profile Name=Fallen Highlands
5/25/2013 11:38:59 PM: Original Destination=<0, 0, 0>. Current player position when stuck=<236.2269, 609.0834, 4.073715>
Profile Name=Fallen Highlands
5/25/2013 11:54:22 PM: Original Destination=<2107.5, 1302.5, 0>. Current player position when stuck=<2106.474, 1309.865, 0.1000001>
Profile Name=Fallen Fields of Misery

very nice profile very good job you are insane :)

(-) Highlands Act1 v5.0
 
In No highlands 5.0, profile is completely skipping Misery for me. It doesn't even load, just leaves game and restarts fallen_Start.

There you have a log, I'm surprised nobody has experienced this, maybe it has something to do with trinity? dunno.

To save you some time parsing through the gazillion exceptions my logs are these days, go straight to 22.01 !


EDIT: Comparing misery.xml from 4.5.1(that works well for me , at least it goes to the map itself :) and misery.xml from 5.0, I find these lines:

<If condition="not ZetaDia.CurrentLevelAreaId == 19952">
<WaitTimer questId="1" stepId="1" waitTime="1000" />
<UseTownPortal questId="1" />
<WaitTimer questId="1" stepId="1" waitTime="1000" />
</If>

that are located after the neph buff check, are missing from 5.0 profile. Could it be that's the reason it is not loading properly for me?
 

Attachments

Last edited:
Testing new FD modded version now, will let u know and post logs if anything is wrong, thanks for updating Fallendev :-)

Edit one:

I don't know what you changed in the FD Weeping script, but it tried to load FoM while still exploring, then it noticed it wasn't there and terminated script to start over again; as seen in the log i posted.

Edit two:

Did it again, teleport to town and resetted the run :(

See u editted the moveto part, maybe that's why its bugging?

Edit three:

After carefully watching it seems after step 16 it isn't waiting for it to teleport thus just loading the Misery.xml part and since its not in range of a node it reloads the profile to Fallen_start_

Done testing for today going to sleep now, will watch tomorrow after you applied fixes, GN!
 

Attachments

Last edited:
In No highlands 5.0, profile is completely skipping Misery for me. It doesn't even load, just leaves game and restarts fallen_Start.

There you have a log, I'm surprised nobody has experienced this, maybe it has something to do with trinity? dunno.

To save you some time parsing through the gazillion exceptions my logs are these days, go straight to 22.01 !


EDIT: Comparing misery.xml from 4.5.1(that works well for me , at least it goes to the map itself :) and misery.xml from 5.0, I find these lines:

<If condition="not ZetaDia.CurrentLevelAreaId == 19952">
<WaitTimer questId="1" stepId="1" waitTime="1000" />
<UseTownPortal questId="1" />
<WaitTimer questId="1" stepId="1" waitTime="1000" />
</If>

that are located after the neph buff check, are missing from 5.0 profile. Could it be that's the reason it is not loading properly for me?
Testing new FD modded version now, will let u know and post logs if anything is wrong, thanks for updating Fallendev :-)

Edit one:

I don't know what you changed in the FD Weeping script, but it tried to load FoM while still exploring, then it noticed it wasn't there and terminated script to start over again; as seen in the log i posted.

Edit two:

Did it again, teleport to town and resetted the run :(

See u editted the moveto part, maybe that's why its bugging?

Edit three:

After carefully watching it seems after step 16 it isn't waiting for it to teleport thus just loading the Misery.xml part and since its not in range of a node it reloads the profile to Fallen_start_

Done testing for today going to sleep now, will watch tomorrow after you applied fixes, GN!

Thanks you two, I'll look into why misery is acting up. And fix it.
 
Thanks you two, I'll look into why misery is acting up. And fix it.

In my case, just manually added those lines after the buff check and it went back to working fine , as in pre 5.0

<If condition="not ZetaDia.CurrentLevelAreaId == 19952">
<WaitTimer questId="1" stepId="1" waitTime="1000" />
<UseTownPortal questId="1" />
<WaitTimer questId="1" stepId="1" waitTime="1000" />
</If>

Other thing is the implementation of scavenger den: just found it for the first time, bot run to it, used the portal, stood inside for a few seconds, took the portal out and kept exploring FoM.
here's the log:

[02:38:48.810 V] Path generation failed! Couldn't find valid start point!
[02:38:48.810 D] Could not generate path!

O.o !
 

Attachments

In my case, just manually added those lines after the buff check and it went back to working fine , as in pre 5.0

<If condition="not ZetaDia.CurrentLevelAreaId == 19952">
<WaitTimer questId="1" stepId="1" waitTime="1000" />
<UseTownPortal questId="1" />
<WaitTimer questId="1" stepId="1" waitTime="1000" />
</If>

Other thing is the implementation of scavenger den: just found it for the first time, bot run to it, used the portal, stood inside for a few seconds, took the portal out and kept exploring FoM.
here's the log:

[02:38:48.810 V] Path generation failed! Couldn't find valid start point!
[02:38:48.810 D] Could not generate path!

O.o !

Appreciate it, don't know how that code went missing from that version.
Absolutely need it there, wonder why more people didn't speak up.
Eh I'll take a look at scavenger den too lol

Well that code is also not good to add, because you don't start the profile out in 19952, so a currentworldId would be better... don't worry I'll have that released shortly.
 
Last edited:
In my case, just manually added those lines after the buff check and it went back to working fine , as in pre 5.0

<If condition="not ZetaDia.CurrentLevelAreaId == 19952">
<WaitTimer questId="1" stepId="1" waitTime="1000" />
<UseTownPortal questId="1" />
<WaitTimer questId="1" stepId="1" waitTime="1000" />
</If>

Other thing is the implementation of scavenger den: just found it for the first time, bot run to it, used the portal, stood inside for a few seconds, took the portal out and kept exploring FoM.
here's the log:

[02:38:48.810 V] Path generation failed! Couldn't find valid start point!
[02:38:48.810 D] Could not generate path!

O.o !

Also wonder if it's something with your systems security with reading ram... this was before every interact error
--> System.AccessViolationException: Could not read bytes from 00000008 [299]!
 
Also wonder if it's something with your systems security with reading ram... this was before every interact error
--> System.AccessViolationException: Could not read bytes from 00000008 [299]!

I hope not! Lots of people were having this could not read bytes issue recently, there were several reports about it in support section. As it does not create a crash, guess most people would just ignore them or not even realize they were happening, cause they wouldn't look up the logs.

So, are you not having this kind of messages in your logs? I gave up looking for a solution, and I thought it was something that was happening to everybody....
 
I hope not! Lots of people were having this could not read bytes issue recently, there were several reports about it in support section. As it does not create a crash, guess most people would just ignore them or not even realize they were happening, cause they would look up the logs.

So, are you not having this kind of messages in your logs? I gave up looking for a solution, and I thought it was something that was happening to everybody....

I'm actually not having the problem, but I am making the rules in the profile more strict which might help alleviate your problem. If your having it someone else prolly is too. So might as well fix it.
 
Back
Top