Mystic Emporium, I think. However, 'Summoning' Luggage places luggage when you use the scroll, and it's 'permanent'.

I seem to remember looking at it, so it should be "necessary". I'll check again, though, and see if there's not another way.

There's quite a few of them and writing them up would take a while... Tes4Edit to the rescue, though - they're under cobTi... note there are also some misc items (hides, etc.).

:shrug: What did you read, or try, or what are you expecting it to do? From glancing at your mod, I'm not sure you get anything from it.

well, since I am going to be looking through this anyways, I am gonna type up a list of alchemy ingredients and their effects. Want a copy of the table for future references? also, I am making a mod that uses cobl, may I have your permission to publish?

I could have used that a few weeks ago :laugh: Thanks, and I'll try to upload it to UESP. Mods - you never have to ask for a mod that uses the Cobl, it's the point of Cobl

Mainly, I'd just like to know what he does there. If the private room is part of the mod, then I can advise Sylar on how to work around the conflict (right now in Anvil there's a major conflict where the room is trying to be shared by Wallace Vey and as the rental room).

Yeah, it was there.

The big thing was I had to not go in for X days (5 in my case) to wait for his inventory to respawn. Oops.

here is the link for the Ingredients spreadsheet. It contains OOO and Cobl

http://www.4shared.com/document/RCZVN9dw/ingredients.html

So, is there any danger in making a not-already-persistent Cobl alchemy sorter persistent to be used with a Home Plate? I don't really know what persistent means, so I'm flying blind here Particularly if said sorter is really, really, really full. Really.

I've never tried it, but I think it will work - the number of items in it really doesn't matter (especially because most of them are script-less).

Persistence - is a horrible word choice. A persistent object will keep its info persistent in memory when you leave the cell - so scripts can still reference it, etc. A non-persistent object only hangs around in memory when you enter the cell and until it's removed from memory (usually right after you've left the cell).

I know that cobl comes with a grinder, I like it alot, is it, or can it be added to a vendor to purchase and place in a house? I want it in frostcrag

> I know that cobl comes with a grinder, I like it alot, is it, or can it be added to a vendor to purchase and place in a house? I want it in frostcrag

This would be a wonderful addition.
A merchant, who sells grinder scrolls (like luggage scrolls) or grinders (like the trashcan).

and a buyable alchemy sorter would be a very nice addition too.

dlc "homes" with cobl grinder, alchemy sorter and luggage = perfect

I thought there was a Cobl-Frostcrag mod? Anyway, easy to do and it will be in the next version.

----

And another topic, a bit bigger and more important for the future of Cobl:
(and an apology - I really should have picked up on this sooner. Been busy :blush2: )

Cobl has made a large attempt to walk a fine line when it comes to OBSE. We use it when the player has it, but it's not a requirement. This shatters that line, though.

If everyone is really^really careful, this has a simple solution - when editing, only use OBSE v17. But, I'll be honest, even I'm not that careful - of all the times I've tested Cobl, needing to switch back from a plugin to a master, I've remembered it 90% of the time. Hell, I need to go recompile a script for the upcoming version. So, I don't expect others to remember this rule either (or even to know about it).

I believe this leaves me with only one option - create separate OBSE and non-OBSE Cobls. I don't really like that idea, though, so if anyone has another option I'm all ears.

Drop support for non-OBSE builds ? I know that that goes against one of the major principles of the mod, but when the alternative is to book-keep two different versions, I'd think it should be considered. Especially when you're talking about a library of this size. Let the next release be the last one to support the shrinking non-OBSE crowd. The perks of doing so speak for themselves.

I agree with shadeMe from a users point of view.

You can’t please everyone and at some point in time one has to accept that backwards compatibility and new features don’t go together very well.
I suppose the fast majority of Cobl users has OBSE installed anyway.

Crash

Using OBSE all the way would probably open the door to even more cool features... and anyone unwilling to install OBSE is likely unwilling to install Cobl as well. OBSE is so ubiquitous these days that I think abandoning support for non-OBSE setups is the best way to go.

from the cobl readme


I dont use one, so didnt place it. I also dont use reborn or revisited.
So I am glad you are considering the selling of them with scrolls



I will have to agree, drop it, most people, not all but most, who are using mods have at least one that requires obse anyways

Non-OBSE crowd? I did not know it existed. Is it a new species?

There's literally no reason to not use OBSE so I don't know why you would put yourself through all the extra work for like the 5 people that don't use it. To each their own I guess.

I agree with this.

Maybe including latest non-beta OBSE in Cobl package as a foolproof measure?

Just make OBSE a requirement. You'll be hard pressed to find very many people who can't use it. Plus a good many mods that require COBL also require OBSE anyway.

I'm in agreement with the above comments: the only reason not to use OBSE is if you've got D2D Oblivion, which is increasingly rare. People who use mods either learn or know not to buy that version, and so you'd be hard pressed to find someone who was going to use mods that couldn't use OBSE.

I don't think that it would be worth the work in supporting two versions of the mod just for those tiny fraction of users that don't have OBSE. Making it a requirement would save a lot of upkeep work. Plus, the more versions you have to work on, the easier it is to make mistakes, applying changes to the wrong version, etc.

I'm sorry, I don't understand what your query, question or comment about Item Interchange is...?

Vac

Thanks for the replies so far.

Dropping support - not going to happen. Can't happen. There are many, many mods that use Cobl without an OBSE requirement, so we can't require it now.

'Forget the non-OBSE peoples' - not going to happen. This is what's commonly known as a bad polling sample Look at the names that have replied.... you guys are the ones who respond the most in the more advanced threads (OBSE, Bash, creating your own OBSE plugins and massive integrated mods). So, of course you're big OBSE fans (and I am too, and will refuse to make non-OBSE/non-Pluggy versions of my own mods). But the current version of Cobl has had 23,140 downloads in the past 6 months (ouch, has it really been that long) and I need to worry about those un-vocal fans and users too.

On work load of 2 mods - the amount doesn't bother me. Actually, it's been a bit hard to write activator functions and scripts that accommodate both. And there have been many places where I'd like to update from OBSE v13 functions to the more recent ones.

The things that concern me are errors:

• Would make it possible for modder to load up the wrong Cobl. However, I don't believe they'd get very far before realizing something is wrong.
  
• It would be simple for me to copy things over to the vanilla version or to the OBSE version. But it's another chance to forget something.

Ultimately, I've been thinking about splitting them for a while now and this seems to require it anyway. However, it's a major decision and one I want out in the public - especially if there are work-arounds that would make everyone happy

I believe the poster was just pointing out an available Frostcrag mod. The text just happened to be from II.

I don't mean this to sound jerkish, but if you didn't expect this sort of answer, why did you ask here? You may not think so but COBL itself tends toward more advanced modders who are aware that you can capitalize on resources like this. If you want to know what those unspoken 23,000 users think, you should probably be asking where they're most likely to respond.

Hey Haama, you haven't commented this:


How bad would that be?