- Status Closed
- Percent Complete
- Task Type Bug Report
- Category Engine → Crafting
-
Assigned To
weltall - Operating System
- Severity Low
- Priority
- Reported Version
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
Attached to Project: PlaneShift
Opened by Illysia - 27.04.2008
Last edited by Tuathanach - 30.03.2014
Opened by Illysia - 27.04.2008
Last edited by Tuathanach - 30.03.2014
FS#1451 - Slicing from far away
When you are cooking, you can put an apple on the prep table, walk away, and still slice up the apple. I think you should have to be in range for that since slicing apples from across the room is odd and a bit inconvenient.
| ID | Project | Summary | Priority | Severity | Assigned To | Progress | |
|---|---|---|---|---|---|---|---|
| 2656 | PlaneShift | FS#2656 - list of crafting bugs | Low | Davide Vescovini, Tuathanach |
assigning to oskaris
I think its not a bug but a conceptual problem.
Preparation table is defined as auto container (alike furnace).
But the idea of a auto container is you can put things into it
and it transforms them automatically.
So using a auto container character is not put into work mode and
no work/trade event is assigned to it.
I would like to add that it's also true for the grill, maybe the oven and pot too. And you can get practice point out of it. That leads to an exploit : put any kind of food into a grill and go away, to do whatever you want. The food will transform into burnt food, awarding you practice points. Then regularly, the grill retransform food into burnt food, awarding you practice point again. Repeatable as much as you want.
unassigning as requested
Please assign this to Rules / Bovek / In progress
The repeating junk item was fixed. That the prep table allows you to walk away is due to it being an auto-container. I'm not sure why it is defined as such, and perhaps that should be undone. Settings should comment on that point.
probably because you can't keep in hand many types of food (which should be fixed)
Fix it as you consider best.
Suggested fix: completion of transform should seek out next viable transform for result and execute with AutoContainer flag NOT set.
Expected behavior with AutoContainer flag NOT set:
- Combines will auto-start associated transform
- Player will have to /Use to begin normal transforms
- Completion of Transform will self-start next transform if there is one
- Player cannot move away from device or change their state while transform is executing…if they do everything stops
Is still still the case? I know other transformation break if you move (even if only by checking when the transformation/action finishes, such as with repair).
If not, weltall, can you look at Boveks solution?
Yeah, it's still the case.
Still happens with auto start containers.