Anonymous | Login | Signup for a new account | 03-01-25 05:47 CET |
Main | My View | View Issues | Change Log | Roadmap |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | |||||
ID | Project | Category | View Status | Date Submitted | Last Update | |
0001582 | SphereServer | executable - generic | public | 25-02-09 12:32 | 02-11-14 01:46 | |
Reporter | khaos | |||||
Assigned To | Ben | |||||
Priority | normal | Severity | minor | Reproducibility | always | |
Status | resolved | Resolution | fixed | |||
Platform | OS | OS Version | ||||
Product Version | ||||||
Target Version | Fixed in Version | 0.56c Nightly | ||||
Summary | 0001582: Dex being configured after @hittry | |||||
Description | As stated on sphere forums. In @hittry, you cannot configure in dexterity like you would think can. Any formula using dexterity within it might as well be tossed out. From testing from multiple sources. Pyromapes, Myself, Admin Phoenixer, plus more... we came to a harsh conclusion there is no way to intercept the dexterity values. | |||||
Tags | No tags attached. | |||||
Nightly Version | 09-09-2008 | |||||
Experimental Flags | None | |||||
Option Flags | None | |||||
Internal Build Number | ||||||
Attached Files | ||||||
Notes | |
(0000179) pyromapes2k (reporter) 06-03-09 12:25 edited on: 06-03-09 12:26 |
This is the related post: http://www.sphereserver.net/forums/index.php?s=&showtopic=45972&view=findpost&p=220615 [^] While we can change the time taken to hit after @Hittry (although the time taken there seems to be 50% of the time given), we cannot alter the time between hits. I recommend the way it worked out in the first test to be the default. 50% of the time given being the delay atfer the swing starts and 50% of the time given being the delay before the next swing. This would mean the dexterity speed for the next swing is calculated just before @hittry so the total default value is stored in Argn1 and is thus, fully editable. |
(0000280) khaos (developer) 12-09-09 08:19 |
Still waiting on a fix for this. I should have not classified this as minor, but a major flaw. |
(0002542) Ben (manager) 02-11-14 01:46 |
This can be worked out with @hitcheck |
Issue History | |||
Date Modified | Username | Field | Change |
25-02-09 12:32 | khaos | New Issue | |
25-02-09 12:32 | khaos | Nightly Version | => 09-09-2008 |
25-02-09 12:32 | khaos | Experimental Flags | => None |
25-02-09 12:32 | khaos | Option Flags | => None |
06-03-09 12:25 | pyromapes2k | Note Added: 0000179 | |
06-03-09 12:26 | pyromapes2k | Note Edited: 0000179 | |
06-03-09 12:26 | pyromapes2k | Note Edited: 0000179 | |
12-09-09 08:19 | khaos | Note Added: 0000280 | |
22-09-09 02:52 | AnarchCassius | Issue Monitored: AnarchCassius | |
02-11-14 01:46 | Ben | Note Added: 0002542 | |
02-11-14 01:46 | Ben | Status | new => resolved |
02-11-14 01:46 | Ben | Fixed in Version | => 0.56c Nightly |
02-11-14 01:46 | Ben | Resolution | open => fixed |
02-11-14 01:46 | Ben | Assigned To | => Ben |
Copyright © 2000 - 2010 MantisBT Group |