<call#> do we want it?

[Zehira]

If they put in call, it should just be a party command for a specific player like /pcmd call <player>. That way u dont get bombarded with macros w <call> and it shouldnt just be limited to the leader cause what if the leader is the one who is unannounced afk or falls asleep?

It should give them <call> once every 5-10 mins so it can stop them spamming calls. I think use <call> in /tell to wake someone up without annoying your party members would be helpful.

However, I know calls can annoy people someday but I don't want to see someone being afk and we are unable to wake him/her up so replace someone is the only way to go though.

[Gerrr]

Y E to the ESSSS!!!!

[Imoen]

I personally like <Call> (With the exception of people that abuse it, but how hard is it to kick them out or block them?)

Things that draw your attention to the chat log at critical moments is really nice, for people that don't want to use voice...

I personally don't like hearing everyone talking while playing my games, it can be more annoying. (Especially when adult conversations/language pops up with my kid sitting there, and why the hell should I always have to use headphones?) Sure I'll turn it on if I really must for something but... I don't have to like it, an alternative such as <call> would be nice.

[Tibian]

I don't care as long as their is an option to turn it off in the settings.

[Lillium]

My opinion (and those of others) on <call> was brought about a year ago here: http://forum.square-enix.com/ffxiv/threads/46696 and more specifically here: http://forum.square-enix.com/ffxiv/t...l=1#post711913 with references to WoW for it's /raidwarning and the popular add-on Deadly Boss Mods.

The short version is: I support and want <call> but allow players some sort of controls/preferences in the configuration menu. /readycheck is something different, but I absolutely support that as well.

The not so short (and possibly over thinking it) version:
Settings might include call volume, limit whose calls you can hear (friends, party, LS, FC, raid, party or raid leader, party or raid assistant (if SE creates this kind of role), a specific list, etc.,) blacklist/substitute certain sounds so you don't hear them but do hear others. Maybe calls can have visual effects/ controller vibration that the user can set to on (attention grabbing), on (subtle), and off. Set a limit on how many calls you hear from one person in a reasonable/select-able time range. The option to /echo a call so that only you hear it if you are only looking to alert yourself about something such as using it in conjunction with /wait. Maybe there could be a text component such as with WoW's raid warnings.

As for how useful it can be, I think that all depends on how individuals or groups use it.

- One of the best arguments for <call> is admittedly probably among the least used (at least appropriately?) Strategy. I'm in a link shell where not everyone is able to communicate with a microphone over a voice program. They use party chat, of course, but it is easy for it to get lost with everything else going on in my log. A call could alert members to something that has happened, such as the squishy mages coming under attack by monsters that just spawned.
- - Maybe a line of text that is <call>ed out will linger longer at the top of the chat window (visually called out?) before it fades out (while the rest of the chat log scrolls normally beyond it) so that party members have a better chance to read it before it fades out. This way it is still helpful even if the sound effect is turned off by some user preference.
- - Maybe a button could be placed in a chat window that could show you only called out chat if you need to reference a previous call quickly if it has faded. press the button again to return that chat tab to it's normal state.
- - expanding on this, a party could associate a sound with an event in battle. When they hear it, they may not even need to read the text, they know what it means and can act accordingly. This could be a warning of danger, an alert saying it is safe to do/resume something, and instruction to take up a strategic position. If timing is important, this could be used in conjunction with some kind of alert that sets up a timer... granted user defined timers could use a thread of it's own. Really, just a thought at this point.

- A means of getting the attention of a sleepy person or someone who is afk but otherwise within earshot of their speakers is definitely useful. You may not want a sleepy person in combat, true! But there is a lot more to an MMO than fighting. You might want <call>s in other situations.

- Doing something playful with friends is good, but there should be something in place to prevent even well meaning macros from being unpleasant. Maybe you have a good reason for having call on every line of your macro... it doesn't mean others will understand it. Even if they do, they might not (probably don't) want it.


Sure, calls can be used to some annoying effect, but so can emotes that have any kind of audio effect attached to them. I don't think that is reason enough to not have them.

Some of my arguments might be made moot in beta. For now I will continue to support <call>, but with a "wait and see" attitude. I'm pleased to see that this is still a topic the devs are paying attention to, regardless of how it may ultimately conclude.

side note: /readycheck seems like a no brainer to me. It would be great to have with any size group. I've never been trolled by a ready check. If someone tries it, they could end up alone really quick.

I agree with you.
If they do add the <calls> I think they should have a option in your settings to turn it off or possibly turn the volume of the <calls> down. Much like the option to change your /tell settings to alert you or not.

The <calls> I could see being most useful! A problem my Linkshell and I were having would have been solved with <calls>. We all use voice chat except for a few of us and other players we would party with. Sometimes we would miss a message in the text box that was super important because we just didn't see it in time or we were not paying attention (we are human after all). Not to mention after a while of grind leveling or doing runs for long periods of time your mind starts to wander and you tend to pay less attention. These <calls> could be very very useful in my eyes. Plus we had a lot of funny moments in XI with them =)

[ChiefCurrahee]

The biggest reason behind <call> lines in a WS macro in FFXI was for the fact that WS linked with other members WS. People would toss a <call> to inform their SC partner of the opening WS, and for the Blm to get ready to magic burst.

Yes you had the person who put an annoying <call> in their boost, so every 15 secs you would get a <call>

or an inappropriate <call> in a TP check macro, or a pulling macro.

In XIV WS are basically on-demand and until we see how limit break skills work, WS don't combo with other members WS. Their is little need for macro WS, unless you have a Buff > WS type deal.


I'm curious to see what the devs have in place to to make players situationally aware. From the videos I've seen a visual field filled to the brim with information and fancy particle effects. The only way I can think of grabbing a players attention will be to scroll large font across their screen for several seconds.

I'd rather just deal with a brief sound.

[Sophia]

I'd like a call function provided it's not abused... aww who am I kidding of course it will

[Skinwalker]

"We start a bit later? Give me a <call> when we're rdy. I Have my speakers on while I watch some TV"

WE NEED THIS BACK !!!11111oneoneone

[Zehira]

Whoa! The OP got many likes! I think it's going to happen. mhmm Time to discuss about how to make <calls> less annoying.

Now, time for bed. Please do not <call> on me. Thanks! ^.~

[Illusion]

Yes I said it before and I say it again I want it, yes there are some annoying people who abuse it but trust me not too many, in all the years I have played FFXI I was never annoyed with it.

Someone with <call> in their macro? Really? I have never witnessed that (Might have forgotten though),but even then the whole PT would have bashed that person to get that the F* out lol.