<call#> do we want it?

[Tinks]

Unequivocally, yes.

[Romper]

If this was in game I would do it all the time for fun.

Every macro, every action, all the time!
CALL!

Call is only good for making music with your LS in the middle of town.

I vote no for <call> based on the fact that this guy is in my LS.

As useful as it can be, we are not stuck with "PS2 limitations" no real need for <call> when VoIP is the standard nowadays.

[Zehira]

I vote no for <call> based on the fact that this guy is in my LS.

As useful as it can be, we are not stuck with "PS2 limitations" no real need for <call> when VoIP is the standard nowadays.

<call> has nothing to do with PS2 limitations. How "standard" is VoIP when not everyone has to/want to use it?

[Romper]

<call> has nothing to do with PS2 limitations. How "standard" is VoIP when not everyone has to/want to use it?

I’ll bite.
“PS2 limitations”………………… more options and solutions can be used instead of the lame ass <call> system. This is a New Game not an updated version of a circa 2000 MMO.
As far as not everyone wanting to use a VoIP while playing a game, I understand. But why should I cater to a bunch of G.I.R.L.’s who don’t want to use VoIP less they be revealed of their masculine nature.
A more valid response would be that even joining /sh groups (which I avoid like the plague) for content; I have rarely ever found a group doing anything worthwhile that did not have a vent, mumble, team speak, tin cans tied to strings, etc, etc…. available for players to use.

[Mychael]

I vote no for <call> based on the fact that this guy is in my LS.

As useful as it can be, we are not stuck with "PS2 limitations" no real need for <call> when VoIP is the standard nowadays.

Call wasn't a derivative of PS2 limitation. If a PS2/Xbox player wanted to VOIP with PC players, they would use their PC to do so while playing on their console. It happened a lot in XI. If EVERYONE used VOIP, or if it was integrated into the game itself, it would alleviate the need for such things; but situations where you would want <call> still exist as things are. Pickup groups DO happen, whether or not you avoid them like the plague. Then, some people don't use VOIP, even in a guild that does. So on. If you use VOIP and don't want to hear calls, I think the recurring theme in this thread has been to offer an off switch for them.

[MyKotoShi]

VoIPてなんですか？

[Yolteotl]

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?

[Zehira]

VoIPてなんですか？

VoIPは友達がいない人々のためである w

[Seirra_Lanzce]

If u are going to sleep shut down the game. Not staying awake to play. The game is not like ffxi where u camp and sleep in game get a feaking life

[TwinMoon]

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.