Anonymous | Login | Signup for a new account | 06-12-24 03:13 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 | |
0002311 | SphereServer | executable - windows build | public | 20-04-14 22:04 | 22-04-14 02:01 | |
Reporter | Coruja | |||||
Assigned To | Ben | |||||
Priority | normal | Severity | minor | Reproducibility | have not tried | |
Status | resolved | Resolution | fixed | |||
Platform | OS | OS Version | ||||
Product Version | ||||||
Target Version | Fixed in Version | 0.56c Nightly | ||||
Summary | 0002311: TYPEDEF t_light_lit not decaying | |||||
Description | when an item with ATTR=attr_decay reach TIMER=0, the normal behavior is decay this item but there's a problem on items with TYPEDEF t_light_lit because they wont decay. Instead decay, it will decrease "-1 light charge", will change ATTR=attr_decay (02) to attr_move_never (010) and goes back to TIMER=600 when the light lit charge goes to 0 the item will decay. But now there's another problem: the item ATTR is 010 (attr_move_never) but it will decay even without attr_decay set | |||||
Tags | No tags attached. | |||||
Nightly Version | Automated (specify build number) | |||||
Experimental Flags | None | |||||
Option Flags | None | |||||
Internal Build Number | ||||||
Attached Files | ||||||
Notes | |
(0002065) Ben (manager) 21-04-14 02:52 |
So with all this... what do you suggest the behavior be? |
(0002066) Coruja (developer) 21-04-14 06:25 |
[TYPEDEF t_light_lit] ON=@Timer IF (<ATTR> & attr_decay) REMOVE ELSE proceed with light charges (without change attr and without remove the item when light charges = 0) ENDIF |
(0002069) Feeh (developer) 21-04-14 17:14 |
What Coruja said makes sense. The flag is there to make things decay; that whats the name suggests |
(0002070) Ben (manager) 22-04-14 02:01 |
Ok, changed things around a little for t_light_lit and it seems to work properly now. Charges will decrease on timer like it used too. When charges reach 0, few things can happen (these were already available options, except for attr_decay not working right) 1 - if (ATTR_DECAY) || (TDATA4 == 0)...burn out (torches do this) 2 - if (TDATA4 == ID same as defname)...It turns into infinite charges 3 - If (TDATA4 == some other ID)...turn into that ID (lanterns do this) |
Issue History | |||
Date Modified | Username | Field | Change |
20-04-14 22:04 | Coruja | New Issue | |
21-04-14 02:52 | Ben | Note Added: 0002065 | |
21-04-14 06:25 | Coruja | Note Added: 0002066 | |
21-04-14 17:14 | Feeh | Note Added: 0002069 | |
22-04-14 02:01 | Ben | Note Added: 0002070 | |
22-04-14 02:01 | Ben | Status | new => resolved |
22-04-14 02:01 | Ben | Fixed in Version | => 0.56c Nightly |
22-04-14 02:01 | Ben | Resolution | open => fixed |
22-04-14 02:01 | Ben | Assigned To | => Ben |
Copyright © 2000 - 2010 MantisBT Group |