Page 1 of 1
Furniture: dresser
Posted: Tue Jul 21, 2015 12:14 pm
by sona
I think it'd be really handy to have a piece of furniture, like a dresser that functions a bit different from current containers, if code can allow for it. My hope would be for something like:
open dresser drawer 1
put blouse in dresser drawer 1
closer dresser drawer 1
open dresser drawer 2
put trousers in dresser drawer 2
close dresser drawer 2
open dresser drawer 4
put socks in dresser drawer 4
close dresser drawer 4
ad nauseum.
It would probably require the use of the second term for each command, but I think that's a much better compromise for organization's sake than having 5 wardrobes, and having tops in one wardrobe, bottoms in another, dresses/gowns in a third, etc.
Re: Furniture: dresser
Posted: Tue Jul 21, 2015 12:20 pm
by Kunren
sona wrote:I think it'd be really handy to have a piece of furniture, like a dresser that functions a bit different from current containers, if code can allow for it. My hope would be for something like:
open dresser drawer 1
put blouse in dresser drawer 1
closer dresser drawer 1
open dresser drawer 2
put trousers in dresser drawer 2
close dresser drawer 2
open dresser drawer 4
put socks in dresser drawer 4
close dresser drawer 4
ad nauseum.
It would probably require the use of the second term for each command, but I think that's a much better compromise for organization's sake than having 5 wardrobes, and having tops in one wardrobe, bottoms in another, dresses/gowns in a third, etc.
I -THINK- I've seen something similar somewhere.
Re: Furniture: dresser
Posted: Wed Jul 22, 2015 1:04 am
by Akila
I want this, despite having no logical room in my wagon for one!
Re: Furniture: dresser
Posted: Fri Jul 24, 2015 7:22 am
by Jirato
This isn't really something I'm willing to code right now. Maybe if I get some inspiration but right now I'm just thinking about the stuff I'd have to modify for this to work, and I can't think of a way to do it without rewriting a significant portion of the container and target finding code.
Re: Furniture: dresser
Posted: Fri Jul 24, 2015 8:41 am
by Fayne
I'm just curious why simply owning a dresser and putting everything in it isn't good enough. All putting seperate drawers on them would do is make them a pain to use. I get immersion, but organizing my sock drawer is something I would prefer be left OOC.
Re: Furniture: dresser
Posted: Fri Jul 24, 2015 8:45 pm
by sona
lets say you have 30 socks/stockings, 20 dresses, 25 tops, 25 bottoms. That's a lot of sifting in jumbled, mixed up strings that I can't focus on, or read. When I struggle with skim reading straight lines like that, in no organized fashion looking for stuff, I feel like my best current option is seriously considering getting a screen reader.
On ideas to tackle it that might be easier than a lot of coding:
maybe have it like a nested container. desser+drawers. then you just get items from drawer 1, etc. The big coding change that'd be needed here, is the ability to put stuff directly into a nested container. We can already take stuff out of a nested container, so long as it's only 1 deep. ie: a backpack in a wagon, you can "get <thing> from backpack" to get stuff from the backpack in the wagon.
Re: Furniture: dresser
Posted: Fri Jul 24, 2015 8:48 pm
by Xyra
Have you tried 'look in dresser list'? It helps out quite a bit for me when going through that sort of thing.
Re: Furniture: dresser
Posted: Fri Jul 24, 2015 8:51 pm
by sona
Yeah, but even with that, which is great, if the quantity of objects is relatively small, unless I take a good amount of time, and read through the list a couple of times, my eyes just have trouble with larger lists. If I colored them alternatively somehow, that'd help, but that seems a lot harder to manage. I mean, this isn't a game breaking issue, nor one of any major importance, It'd just be a nice thing that would let me organize stuff more nicely. After all, there is nothing wrong with having 5 chests with different clothing slot stuff in each.
Re: Furniture: dresser
Posted: Fri Jul 24, 2015 8:53 pm
by Xyra
You could set up a macro to auto-sort them for you if you'd like.
Re: Furniture: dresser
Posted: Tue Aug 11, 2015 12:50 am
by jilliana
sona wrote:lets say you have 30 socks/stockings, 20 dresses, 25 tops, 25 bottoms. That's a lot of sifting in jumbled, mixed up strings that I can't focus on, or read. When I struggle with skim reading straight lines like that, in no organized fashion looking for stuff, I feel like my best current option is seriously considering getting a screen reader.
On ideas to tackle it that might be easier than a lot of coding:
maybe have it like a nested container. desser+drawers. then you just get items from drawer 1, etc. The big coding change that'd be needed here, is the ability to put stuff directly into a nested container. We can already take stuff out of a nested container, so long as it's only 1 deep. ie: a backpack in a wagon, you can "get <thing> from backpack" to get stuff from the backpack in the wagon.
Heh. Not sure if you were serious, but screenreaders don't make skim reading very feasible, just FYI.
As for the topic of the post, I found that for Jilliana I use different containers for different types of things. Dressers for socks, blouses and pants, trunk for shoes, wardrobe for coats, dresses and skirts, etc etc.
Re: Furniture: dresser
Posted: Tue Aug 25, 2015 4:48 am
by Jirato
jilliana wrote:
Heh. Not sure if you were serious, but screenreaders don't make skim reading very feasible, just FYI.
Not sure if this helps any since I don't use a screen reader, but have you tried this:
look in (container) list
Give it a shot.
Re: Furniture: dresser
Posted: Fri Sep 25, 2015 5:02 pm
by jilliana
Jirato wrote:jilliana wrote:
Heh. Not sure if you were serious, but screenreaders don't make skim reading very feasible, just FYI.
Not sure if this helps any since I don't use a screen reader, but have you tried this:
look in (container) list
Give it a shot.
I haven't tried it, but that already looks promising. Thank you.
Re: Furniture: dresser
Posted: Sat Oct 31, 2015 12:19 pm
by ydia
I agree this idea would be cool, but lots of coding for Jirato.