Posts from Azure_Zero | Pathfinder Online

Page 51 of 86
←
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
→

Azure_Zero 06.13.2015 14:14
	Midnight It would be very rude to login to an active feud, and sooner or later someone will. The login screen needs a warning if your character is involved in an active feud. That is a very good idea, Though it should reference the character(s) that are in the Feud. Quote

Azure_Zero 06.09.2015 09:57
	Now a question to ask is; Should there be faction elements at not only the character level, but also at the company and settlement level? Quote

Azure_Zero 06.09.2015 07:13
	They should have it that after the character has finished loading it sends the settlement company data, as company data hardly changes. We do like to review it at times, and if you want to reduce overhead and still give the data just send it once, or hourly. Quote

Azure_Zero 06.05.2015 11:53
	Bob Drogon understandable, I am just trying to think outside the box until you get the bug fixed…, what about putting a hard cooldown on each monster hex of 2-3 days before it can respawn anything? is this what the fallow time is attached to already or is it tied to the specific type of escalation that was recently killed in that spot? That's kind of what the fallow system does. When an escalation is defeated, it tells the hex not to launch another escalation for a certain number of hours, that number being specified by the defeated escalation. That effectively puts a cooldown on the hex. Unfortunately, something about downtime is clearing or ignoring that cooldown. You could do a bit of a hack, at about say 10 minutes before server down, the server writes a file with the STR of escalation, Defeated flag and a Defeat time stamp. when the server boots it reads the file and if defeated == false it sets STR based on the STR in the file, or if Defeated == true it reads the Defeat time stamp and does some calculations and sets how much time is left before it spawns an escalaton. Quote

Azure_Zero 06.05.2015 11:53

Bob
Drogon
understandable, I am just trying to think outside the box until you get the bug fixed…, what about putting a hard cooldown on each monster hex of 2-3 days before it can respawn anything? is this what the fallow time is attached to already or is it tied to the specific type of escalation that was recently killed in that spot?

That's kind of what the fallow system does. When an escalation is defeated, it tells the hex not to launch another escalation for a certain number of hours, that number being specified by the defeated escalation. That effectively puts a cooldown on the hex. Unfortunately, something about downtime is clearing or ignoring that cooldown.

You could do a bit of a hack,
at about say 10 minutes before server down, the server writes a file with the STR of escalation, Defeated flag and a Defeat time stamp.
when the server boots it reads the file and if defeated == false it sets STR based on the STR in the file, or if Defeated == true it reads the Defeat time stamp and does some calculations and sets how much time is left before it spawns an escalaton.

Quote

Azure_Zero 05.30.2015 09:54
	Ouch…. I hope that gets fixed Quote

Azure_Zero 05.27.2015 11:31
	NOTICE: Due to the New installer Package setup, that RELIES on the solely on the Patcher, PFO can no longer run on linux until further Notice. Quote

Azure_Zero 05.27.2015 09:58
	If you want there is an Early version of the guide up on Coalroad.com for now. It'll be updated and fixed a bit more later, included next to the video file is another guide for PFO. Quote

Azure_Zero 05.27.2015 09:58
	If you want there is an Early version of the guide up on Coalroad.com for now. It'll be updated and fixed a bit more later, included next to the video file is another guide for PFO. Quote

Azure_Zero 05.27.2015 08:43
	I'll be releasing a Guide for 32-bit Windows users that should fix the problem, and free up more resources for PFO. It'll be released in June, first Via a video File, then Youtube. The HRC will be getting the first view on Coalroad.com, so I can fix things before public the major release. And there are beneficial side effects for using the guide, and they will be mentioned in the video. Quote

Azure_Zero 05.27.2015 08:29
	I'll be releasing a Guide for 32-bit Windows users that should fix the problem, and free up more resources for PFO. It'll be released in June, first Via a video File, then Youtube. The HRC will be getting the first view on Coalroad.com, so I can fix things before public the major release. And there are beneficial side effects for using the guide, and they will be mentioned in the video. Quote

Page 51 of 86
←
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
→

Cookies Disclaimer

All posts created by Azure_Zero