I personally love the new visible cloaks in 1.68, but I can understand how some players might not want them to display in game. In my PW, characters who like dresses or skimpy attire, or those with wings or tails, have requested an invisible cloak option. Simply drop this tiny hak file into your override folder, or merge it into your 2da hak, and you're all set. It adds an Invisible option to the cloak appearance list in the toolset. The Invisible cloaks still have inventory icons, so alter the cloak to your liking in the toolset before selecting the Invisible appearance. Now players who want to hide their cloaks can do so, while the rest of us can enjoy Lisa and DLA's fine work.
Bloodsong: The easiest way to make your cloak invisble is to ask a DM on your server to build one in the toolset and mule it in for you. Naturally, this assumes that your server is also using this hak. Any existing cloak can be converted to an invisible copy with a few mouse clicks. If your server allows local characters, you can easily fire up the toolset and convert your own cloak. I am working on a script that will allow easy manipulation of cloak colors and appearances by players in-game, for use with clothing shops, Milambus' tailoring models, and such. There are quite a few good ones already found on the Vault, and as long as they read the cloakmodel.2da from your module's hak resources, they should work with this hak. Ask your server admin to compare them and see which is best for the server if invisible cloaks are something they want to add. I also have versions of this 2da that support Lisa and Raven_Xan's additional cloak packs, winged cloaks, tail cloaks, and a combination of both, and will gladly send it to you upon request. _________________________ Realms Of Destiny PW
Posted by bloodsong at 2006-09-07 16:22:00 Voted 10.00 on 09/07/06
okay, dumb question:
im a player, using this in my override. how do i change a cloak in the game to the invisible cloak entry? or i can't, unless the server adds a script to do that?
hopefully, the option to have a non-visible cloak will become standard.
Okay, thanks :) My file works the same way for players, but so far, I don't have any feedback from builders :( I hope that will change :) _________________________ Never pass up a good opportunity!
Silver Star: My file can be used either by players or by builders. A player can simply drop it into the override folder and it will work. It is so small that it can be easily moved in and out of the override folder to integrate with the haks used on various servers. A builder can simply merge it into the 2da hak for his module and it will also work. Either way, the hak file is tiny and can be installed with one step, which was the idea. My browsing of the BioWare forums made me decide that ease of use was most important, since so many people were having technical problems with the new cloaks, most of which could have been avoided if they had simply updated their hak files or waited for their PW admins to do so. _________________________ Realms Of Destiny PW
Okay, been doing some thinking on this issue :) Is your file for mod builders, so they can make a choice, or is it for players as well? My file is players only, and the way I did mine, no cloaks show up at all, unless there is some hak file involved (and they might not even then). I'm just curious. _________________________ Never pass up a good opportunity!
Well, let me reiterate, what I've said, and the 2da file I did, is not meant to detract from your cloaks in any way. It does seem to me that some problems have popped up, and hopefully someone will come out with a better patch, and better compromise, than myself or Big_Shoe has so far. Before cloaks were visible, using one was like getting a third ring, second belt, extra amulet, etc., just one extra thing for bonuses. I guess we all just got used to being without cloaks, and now with some of the problems that have happened, more work needs to be done. What I did see of the cloaks, before I implemented my hak, are nicely done :) Once again, PLEASE let me start my hak is NOT meant to detract from your very nice work :) _________________________ Never pass up a good opportunity!
Well Lisa, the problem with the cloaks to this point is, they don't match armor, and cover up wings, and cover armor shoulder pads.
???????????????????????????????
1. Those were bioware default choices, which for default they had to make and which I agree with. However, others might not so they made it easy to see your wings and tails and shoulderpads if you want - its a trivial change anyone can do with notepad in the cloakmodel.2da. Change the 1's to 0's in the "hide" column. Put your new cloakmodel.2da in override and bingo, all the wings and tails you want :) Some of the models were made to display 1 or both shoulder pads - others will look funky with shoulder pads o.n, TBH But the Wings and tails on or off, even DLA has altered that from default for our upcoming module ;)
2.) I didn't set up the cloak slot programming or even know about it until it was completed. That was done the fantastic programmer guys at bioware. Now, they chose to set cloaks up like helms. Helms have their colors that are set/dyed independantly of the rest of your outfit. It is rare to find a helm that will match your armor - you gotta dye them usually. Cloaks are the same. If you want them to match - you can dye them.
I do not think that "color" inheritance is even a blip on the bio teams radar at this point as the seperate coloration of cloaks was like for helms a deliberate choice on their part.
Also if you check the vault - plenty of peeps are posting lots of nice crafting scripts to handle dyeing as well as changing models.
Finally if I start to think of all the creative ways that the now visible cloak slot can be used - color independance, transparency independance, and which parts are hidden set by model - make it much more flexible (like I made a hat up as a "cloak") Course that is my opinion.
I'm glad your hak works, but it doesn't address some of the issues raised in the bioware forums :) I guess in the end, this will be a matter of personal taste :) Lisa, I think your cloaks are nice and well done, but until there is a way to dye them to match the rest of armor, and a way to still wings and shoulder pads on armor, this debate will continue. _________________________ Never pass up a good opportunity!
SilverStar, my hak has been tested and works just fine. Your hak makes all cloaks invisible, whereas mine allows builders to mix visible and invisible cloaks in the same module. I am a big fan of Lisa's work, and would never have posted a hak that removed it all by default, thus this compromise. :-) _________________________ Realms Of Destiny PW
Well Lisa, the problem with the cloaks to this point is, they don't match armor, and cover up wings, and cover armor shoulder pads. Maybe some of this could be fixed in the 1.69 patch that will be the last patch. We'll have to wait and see to be sure. I've even heard that when you dye a cloak to match armor, it might not turn out right. Those are the comments from the forums btw. I've seen your cloaks, they look really good :) What I did with my file is not meant as a detraction to your nice cloaks in any way :) Just some of use are unhappy with cloaks showing when they just don't match the armor, or cover wings. Just some comments :) _________________________ Never pass up a good opportunity!
Nice compromise. Certainly we don't all have the same playing styles. I'm sure plenty of other peeps will appreciate this as well...even if I would not use a null cloak myself (but I'm prejudiced - I admit)
Lisa
I'm not sure yours would work. My 2da file is different, and will likely do the better job. However, if you want visible cloaks, you can always rename my file to something like put cloakmodel.2da.bak :) Then you can name it back to it's original name when you need invisible cloaks again. To be honest, I was going to do something like you've posted, but I did mine differently, and it works like it should to give invisible cloaks :) _________________________ Never pass up a good opportunity!
You must be Logged In to post comments in this section.