|
Post by tenson on Mar 11, 2008 15:33:33 GMT -5
I thought I'd save some space and ask questions on 2 topics. Speech: - Is it possible (or already in place) to select speech option as "say/party/raid/whisper"? I'd like to announce spells like "Rebirth" to the one being rez and the raid as well. Currently I only found either "say/raid/party" OR "whisper".
- Is it possible (or already in place) to NOT say things when I'm by myself? For example, I don't need to tell myself that I've been Innervated...
An idea would be to replace the current drop down list with checkboxes and whatever's checked (say/yell/party/raid/whisper) would be announced. Then, have another checkbox for "[x] Silence when Solo" Buttons: Is it possible to allow movement of main Sphere and some menu-buttons but not all? I think right now it's either All on or All off? For example, I have some menu-buttons detached for quest item/buff purposes, which I'd like to drag-move some time, but I plan on using some detached menu-buttons as the main action bar, and would prefer if they don't move at all. Once again, thanks for providing such a great tool for making our WoW lives more fun. ;D
|
|
|
Post by Moongaze on Mar 11, 2008 16:03:48 GMT -5
Speech: - Is it possible (or already in place) to select speech option as "say/party/raid/whisper"? I'd like to announce spells like "Rebirth" to the one being rez and the raid as well. Currently I only found either "say/raid/party" OR "whisper".
- Is it possible (or already in place) to NOT say things when I'm by myself? For example, I don't need to tell myself that I've been Innervated...
An idea would be to replace the current drop down list with checkboxes and whatever's checked (say/yell/party/raid/whisper) would be announced. Then, have another checkbox for "[x] Silence when Solo" The check box idea would work well, but if you select Say, Group, and Raid, the speech will trigger and say it's thing in all three channels. As it is now, if you set it to Group/Raid, it will pick the "highest" group you are in and announce it there. Maybe I can stick with the drop down as-is, and add check boxes for another section called "Also announce to:" which will announce it to the check boxes you have. This will allow for the default channel stuff to work, and force LunarSphere to say the speech in a specified channel as well (for example, whisper). I can also add a checkbox for the "Silence when solo" feature, as that would make sense. Would that idea work? Channel : [[Drop down list]] Also display in: [ ] Say [ ] Yell [ ] Group [ ] Whisper [ ] Raid Of course, if you have "Say" in the channel box and you check Say as well, LunarSphere won't duplicate the speech. It will be smart about that and will only broadcast to a channel once. The same will be said about the Say/Group/Raid idea. If you select that and you are in a group, it will broadcast to Group. If you selected "Say" from the "also display in" section, it will also display in Say also, since it only displayed in "Group" so far. I hope that idea works best for you, because I kinda want to keep the listbox Sure, I can add a "Lock movement" option to each menu button next to the "Detach" option. That way, when it is detached, it won't be able to be dragged by accident when the sphere can be dragged. Welcome
|
|
|
Post by tenson on Mar 11, 2008 16:27:04 GMT -5
Did I mention how awesome you are? ;D
Wouldn't the drop down list be redundant once the "also say in" is added?
In my mind, the code would see which of the option is checked, then just perform those actions:
Channel(s): [ ] Off when solo [ ] Say [ ] Yell [ ] Group [ ] Whisper [ ] Raid [ ] emote
Right?
|
|
|
Post by Moongaze on Mar 11, 2008 16:43:28 GMT -5
At first, I thought it would be redundant ... but you have the issue of people who want a speech to be said to the group if they are in a group, or the raid if they are in a raid, or the say channel when they are not in a group at all. So, they select Say/Group/Raid. When the speech goes off, it will say the speech in the raid (if it exists), or the group (if it exists), or, if none of those exist, the say channel.
Doing it where the check boxes for Say, Group, and Raid are selected, you will have the speech go to all THREE groups, so you'll see:
[Raid]: This is my speech! [Group]: This is my speech! [Say]: This is my speech!
Where as with the dropdown with "Say/Group/Raid" selected, you will just see:
[Raid]: This is my speech!
The Group/Raid selection will work the same way, but will ignore the say channel.
I suppose I could just drop the list and add the "Group/Raid" and "Say/Group/Raid" to the check boxes. Then, the person can click "Say/Group/Raid" and "Say" and it will display the text to the Raid or Group or Say first, then to the Say channel (if the Say channel wasn't already chosen by the previous one).
|
|
|
Post by tenson on Mar 11, 2008 17:13:28 GMT -5
OMG Fast replies! Ok, I thought the "Say/Party/Raid" means, it does all 3, but now I understand it takes the highest settings. How about this? Channel(s): [ ] Off when solo [ ] Say [ ] Yell [ ] Party [ ] Whisper [ ] Raid [ ] emote [ ] Grouped
Where Grouped would be equal to "Say/Party/Raid" which chooses the highest to display (and if solo, do "say"). Like such (using Innervate): Channel(s): [x] Off when solo [x] Say [ ] Yell [ ] Party [x] Whisper [ ] Raid [ ] emote [x] Grouped
What it will do (in theory): 1. Innervate my target and announce in "say" and "whisper" and, 2. "party" if I'm only in 5 man, or, 3. "raid" if I'm in raid. Just trying to brainstorm ways to reduce codes. Doh! What about when I want to do the above (assuming code works), but I don't want to hear "You've been Innervated!" when I apply on myself? Maybe the top checkbox should be: Channel(s): [ ] Off on self [ ] Off when solo
That way, if I check "off when solo", I can still /w to my target if I'm questing and I throw Innervate to someone low on mana. That is, it will disable "say" or "yell", but not "whisper" (or grouped 5+, but since I'm solo, the grouped conditions won't apply). And if I check "off on self" then all checked conditions are ON except when target=player. Summary: [ ] off on self: - when applying spell on self, no speech occurs
- otherwise, speech occurs according to check marks
[ ] off when solo: - when ungrouped, disable /say, /yell,
- do /whisper if checked
Thoughts?
|
|
|
Post by Moongaze on Mar 11, 2008 18:20:06 GMT -5
Well, "Off while solo" and "Off on self" are good and need to be there. As to how they will work, I would assume that if it is "Off while solo," that speech will be ignored if you are not in some kind of group. Including whispers.
However, if you want the target to be notified when you do an Innervate, and your "Off while solo" feature is off, it will simply whisper or say to the target what's going on. If you have "Off while solo" on and you are in fact solo at that time, the target won't get anything. This would make since since you told the script to be off while soloing. If it whispered someone, it technically isn't off.
I'm assuming that if you were to Innervate someone, you would announce it to the group/raid, and whisper the target. So, having "Off while solo" unchecked, "group/raid" checked, and "whisper" checked, you will do:
[group/raid]: Innervated Moongaze [whisper to Moongaze]: Innervated Moongaze
If you are solo, you will get:
[whisper to Moongaze]: Innervated Moongaze
Of course, I would rather have two messages. One for informing the group who recieved the Innervate, and the other informing the target "You have been Inervated". So, a speech that says:
"Innervated <target>!<newline><whisper>You have been innervated"
... will accomplish that and you only need to have "group/raid" checked, since the whisper will be a forced channel output anyway. Assuming, of course, that the speech can be ran. If you have "off while solo" turned on, and you are solo, the speech will never be ran and will be ignored, even with the <whisper> parameter added.
"Off on self" would do exactly what one would expect, which is if the target happens to be the player, it will ignore the speech.
Thoughts?
|
|
|
Post by tenson on Mar 11, 2008 22:17:18 GMT -5
I suppose that logic works in terms of coding: "Off while solo" == "all off".
(if target==player OR Not_grouped) ignore speech (else) do picked speech (end)
I know more if/else/conditionals will only add more work for you, so I'll explain my "ideals", but not requesting them to be implemented.
The way I play, if I'm solo questing, and I see a fellow faction player low on mana while fighting, I may offer to heal (as a druid), and sometimes give out Innervate. At that moment, it's just a nice reminder to send a "whisper", but don't need to execute "say" or "yell".
On a big blanket if/else, it would be similar to:
(if target==player) ignore speech (else) (if Not_grouped) only do whisper (else) do picked speech (end)
I'm not a programmer (only as a hobby), so my logic is probably flawed, but the above case would be what I described.
I can't think of a case where I have to have things only whispered while solo, so if your logic can be implemented it would be great.
Besides, I'm on a PvE server, and I think "off while solo" is important for those PvP, as they wouldn't want speech bubble to give out their position to the opposing faction.
Thanks again for taking the time to read through our requests. =)
|
|
|
Post by tenson on Mar 11, 2008 22:23:24 GMT -5
Hmm. Can the current version do: "Innervated <target>!<newline><whisper>You have been innervated" ?
Meaning, if I use drop down to pick "say/party/raid", and typed the above line of speech, it will also whisper to my target because <whisper> is found?
That would be cool since right now I only do "whisper" on my target with Innervate, since I seem to be able to choose either "whisper" or "say/party/raid" but not both (like the check boxes we discussed).
|
|
|
Post by Moongaze on Mar 11, 2008 22:48:44 GMT -5
Yes, that feature is implimented. Not many people know about it unless you have a good memory and read all my patch notes Give it a try, it pretty much does what you wanted, hehe. It just requires some extra speech tags to be added to the speech ;D One nice feature that someone suggested was the multi-line speech a while back. With the possibilities for lots of fun, I also added the ability to force a channel to be used in the speech with <whisper> and <emote>. I haven't added <raid>, <party>, <say>, or <yell> yet, but plan to in the future. With this feature, you can do something like: (Channel to display: Say) "Come on out, Felhound!<newline><emote>scribbles some runes on the ground.<newline>Hurry up, I don't have all day!<newline><emote>tabs their foot." And you'll get: Moongaze says: Come on out, Felhound! Moongaze scribbles some runes on the ground. Moongaze says: Hurry up, I don't have all day! Moongaze taps their foot. ;D
|
|
|
Post by cidhighwind on Mar 12, 2008 12:09:07 GMT -5
Just because it seems to fit with that example, would it be possible to use a wait in that string, so it waits with the next line until the cast is done?
|
|
|
Post by tenson on Mar 12, 2008 15:42:20 GMT -5
Cool. I'll definitely try those codes.
One more question: Is it easier for you to allow the same syntax as macro codes instead of supporting new tags? For example, instead of <target>, just support %t (meaning current target, used in macros).
I don't know if there're code conflicts or secure issues, or what, but it seems like an extra cost to come up with new syntax for /p, /s, %t, etc. I know it's not as intuitive as <target>, <newline>, but these can be written into a "how-to" guide when LS goes public.
Thoughts?
|
|
|
Post by Moongaze on Mar 12, 2008 19:04:43 GMT -5
Just because it seems to fit with that example, would it be possible to use a wait in that string, so it waits with the next line until the cast is done? It's not there yet, but I do plan to add more tags to achieve this. One such tag would be <after> which is for after spell cast, and another is <delay:n> which would n seconds before the speech appears. The <delay:n> is more a bonus for roleplayers who want to have some speeches split up, or for guild masters who want to just cast a spell or use an item or something to say a speech which, well ... explains the boss battle ... I might actually allow for people to say a speech manually with an "execute" button on the speech tab, or let people use a macro to say specific speeches from a script. That would be something for later on though. Cool. I'll definitely try those codes. One more question: Is it easier for you to allow the same syntax as macro codes instead of supporting new tags? For example, instead of <target>, just support %t (meaning current target, used in macros). I don't know if there're code conflicts or secure issues, or what, but it seems like an extra cost to come up with new syntax for /p, /s, %t, etc. I know it's not as intuitive as <target>, <newline>, but these can be written into a "how-to" guide when LS goes public. Thoughts? The reason I choose these tags is because they are common in the other Sphere type addons (necrosis, cryolysis, totemus, etc) and I'm keeping the format so people can import speeches from those very easily. I was thinking of using tags like /s /g /r /w /e /y for channel switching, but I will also have <delay:n> <newline> <summon> <pet> etc. And if it is "/s" for say, and /summon for summon spell name, the speech engine will most likely replace /summon with the say command and will display "ummon" in the say channel. Obviously, making sure the user puts a space between each tag would make more sense, but I can't assume the user will use the tags properly, or format it properly, so enclosing them in a bracket of some kind gives me and the speech engine confidence to do the job right. I'll have a button that one can click to see all available tags, and they can mouse over the tag to get a description of what it does. I know I am reinventing the wheel, so to say, but there are a lot of these tags that already exist in these sphere type addons and some roleplaying helpers Does that help to explain the reasoning behind my madness?
|
|
|
Post by cidhighwind on Mar 16, 2008 11:33:36 GMT -5
Also since many users already wrote tons of lines with those tags, I would step away from the guess changing it afterwards... . Just a lot of work for nothing really significant :\. O.K. I give in I just wouldn't like to rewrite my own lines
|
|
|
Post by Moongaze on Mar 16, 2008 13:48:02 GMT -5
No worries If I did change the tags to a different format, I would have code that would run once that would cycle through all speeches and replace the old stuff with the new stuff. Of course, if the speeches were somewhere else (like a text file), they would be not be affected. I would still have a "filter" or "convert" feature somewhere that the user could run at any time to do the conversion as well ... either way, I would take care of you the best I could.
|
|
|
Post by tenson on Mar 19, 2008 15:28:52 GMT -5
No worries If I did change the tags to a different format, I would have code that would run once that would cycle through all speeches and replace the old stuff with the new stuff. Of course, if the speeches were somewhere else (like a text file), they would be not be affected. I would still have a "filter" or "convert" feature somewhere that the user could run at any time to do the conversion as well ... either way, I would take care of you the best I could. Told ya Moongaze is awesome like that. /stealth ego-boost
|
|