View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000952 | The World of Secfenia | Battle | public | 2017-10-04 08:39 | 2017-10-24 20:41 |
| Reporter | bridget | Assigned To | daviceroy | ||
| Priority | normal | Severity | major | Reproducibility | have not tried |
| Status | resolved | Resolution | fixed | ||
| Product Version | 3.0.6 | ||||
| Target Version | 3.0.6a | Fixed in Version | 3.0.6a | ||
| Summary | 0000952: Duels stop at 100 rounds | ||||
| Description | The duel between Bridget and Alder went to 100 rounds and then stopped. No declared winner. | ||||
| Steps To Reproduce | Duel someone. Have it go 100 rounds... | ||||
| Additional Information | Just a suggestion: if 100 rounds is the max, either a winner should be declared (the most fit character) or a draw should be called. | ||||
| Tags | No tags attached. | ||||
|
|
Considering that both players were fairly healthy after the duel's end (Alder was down 0.5 hearts at reset, Bridget at 1.5 hearts down apparently), maybe it would be worth making damage numbers higher in general, otherwise I don't think duels between high level characters will end in 300 rounds, let alone 100. Alder was taking about 30 ish damage (on average) per hit, which is going to mean that it will take a very very long time to chop through all of his 3500 (ish) hp (added to recuperate which heals him 50 ish every few rounds and parry/dodge which remove damage every few rounds, plus, if he was using spells, healing from priest way which would be 80 ish every few rounds)... I mean, I have 55 events saying he was damaged and he was still at 2700 (ish) hp by the end of it. Then again, two other duels with high end characters (one with Alder vs Logo and one with Bridget vs Scarlet) were resolved by the end of 100 rounds, so maybe this was just the effect of having 2 characters with the defender way totally learned against each other. |
|
|
Looks like I might need to tweak damage a little bit more for duels. Contacting player to verify what I believe the confusion is. The duel does have a winner in the system, but I think the confusion may sit with the fact that the Duel doesn't log the Winner in the Duel Log. |
|
|
I'd like to add that it did not appear on the news and that neither player was even close to the standard 'severe injury' threshold of 1 half heart remaining (even though we are phasing out that system, I'd imagine we'd still be looking at somewhere like that sort of percentage of their health remaining). So, even if there is a winner in the system, I don't think there should have been one yet, especially since the last blow was landed by the person who was on lower hp after that blow was landed. |
|
|
Sorry, I hadn't noticed the winner posted on the side. Can you explain how the winner is declared in this new system? |
|
|
A player reported the issue that a duel lasted to the end of the normal rounds and we modified it so that it increased from the old 50 rounds limit to 100 rounds limit. In addition, each time someone does damage, they get assigned 1 Point for "winning" the round. Stalemates do not given any points that round. This way if the round limit is hit then the tie-breaker is whomever has the most points. (There are more details about the different type of Duels and victory conditions in the Duels Tutorial as well: https://www.secfenia.org/tutor2.php?id=232 ) It appear that the issue revolves around the winner not being published in the same way as other Duels which caused understandable confusion. Will need to sync up this bit of code so that it: 1) Displays it in the Duel Log (which was updated into the reset script for 10/5) 2) Displays in the News Scroller (which is added into the reset script for 10/6) I've also tweaked the Duel system also to change up some of the numbers regarding damage for future Stat Duels. Will keep an eye on the Stat Duels in the future to see how this affects things. |
|
|
Adjusting Numbers a little bit more in Stats Duels as the initial change has helped, but not as much as wanted yet. |
|
|
Tweak looks good at this point. Closing out for now. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-10-04 08:39 | bridget | New Issue | |
| 2017-10-04 08:39 | bridget | Status | new => assigned |
| 2017-10-04 08:39 | bridget | Assigned To | => testing |
| 2017-10-04 09:54 |
|
Note Added: 0000642 | |
| 2017-10-04 23:11 | daviceroy | Note Added: 0000643 | |
| 2017-10-05 06:03 |
|
Note Added: 0000645 | |
| 2017-10-05 08:31 | bridget | Note Added: 0000646 | |
| 2017-10-05 17:01 | daviceroy | Assigned To | testing => daviceroy |
| 2017-10-05 17:01 | daviceroy | Status | assigned => confirmed |
| 2017-10-05 17:02 | daviceroy | Product Version | => 3.0.6 |
| 2017-10-05 17:02 | daviceroy | Target Version | => 3.0.6a |
| 2017-10-05 19:34 | daviceroy | Note Added: 0000648 | |
| 2017-10-16 17:37 | daviceroy | Note Added: 0000656 | |
| 2017-10-24 20:41 | daviceroy | Status | confirmed => resolved |
| 2017-10-24 20:41 | daviceroy | Resolution | open => fixed |
| 2017-10-24 20:41 | daviceroy | Fixed in Version | => 3.0.6a |
| 2017-10-24 20:41 | daviceroy | Note Added: 0000659 |
