Don't do it!
Just... Please. People will just complain about it being used in the first place.
Don't do it!
Just... Please. People will just complain about it being used in the first place.
I'm pretty sure our chat system has those capabilities though. If they can add a chyme that plays whenever we receive a /tell, I don't see why they can't add a sound effect triggered by a certain text command. My only hope is that if they do add <call>, which I am very much in favor of, is that they add some sort of timer on it so people can't spam it as they did in XI. Maybe once a <call> has been used in party chat, you must wait 30 seconds before a party member can do it again, or something to that effect.
There is indeed a limitation: It's called time. Every game development has that limitation though.
There's really no need to misinterpret statements just to cause more whining.
(And there's probably no need to tell Rukkirii how to do her job either.)
OH GOD NO!! Were you....... "THAT GUY"????
You know the one who macro'd...
{Found It} Soldier Crawler! <call4>
{Ranged Attack} Soldier Crawler! <call5>
Incoming Soldier Crawler {Prepare for battle} <call6>
TP 100% SATA Ready <Call7>
Skillchain GO <call8>
I think <call14> was about the only one I could tolerate.
Adding <call> would be a great idea though. few times I typically tab out between fights and typically just say I'll tab in when i hear the cs. failing that people just shout over mumble. but a call would certainly be usefull.
<call>ing back afk members while building parties for things, cause we've all spent 2 hours building a party, is about the only time I ever used the generic <call> and even then only after giving fair warning cause it really was obnoxious, but useful as all get out.
Having multiple <call>s like they eventually did in FFXI would be great. I have a count down macro for things like Hellfire and being able to just have a <call-normal volume> at the 5 second mark would make it a bit more noticeable. Adding a slider to the audio controls just for general call volume seems like a good idea too, though I think that being able to completely turn them off is defeating the purpose. A delay between uses like /yell in XI where once you use it you have to wait N seconds before using again so people don't just spam.
Having them tied into the vibration was something they had in XI too, right outta the gate, nothing was more entertaining than a 5AM xp pt where your starting to nod out then your controller jumps outta your hands and rattles across a floor/desk, while the game makes horrible noises.
On the note of adding it, the input parser already processes <blah> there's really no reason at all that having /call or <call> work should be that much work. Unless of course the code isn't modularized well and the parser is spread across 3000 files jumbled in with other crap.
XIV Pad: http://xivpads.com/?Elasandria-Servion-Hyperion
Linkshell: http://sd-is.guildwork.com
Rig: https://www.dropbox.com/sc/jv56yukhpi7413q/gQTzd-DS9y
FX-8150 @4.1GHz; 8Gigs ripjaws @1600; OCZ Vertex 3 128GB SSD; WDC 1TB HDD;
XFX Radeon HD 7970;
http://www.youtube.com/watch?v=RZKBSFtAi1E
Relevant 1:20 onwards.
That's why they need to implement some form of timeout/cooldown so ppl can't just spam noise, and of course it should be party only like it was in XI.
<call> isn't bad, it's how ppl used it to be jackasses that was.
XIV Pad: http://xivpads.com/?Elasandria-Servion-Hyperion
Linkshell: http://sd-is.guildwork.com
Rig: https://www.dropbox.com/sc/jv56yukhpi7413q/gQTzd-DS9y
FX-8150 @4.1GHz; 8Gigs ripjaws @1600; OCZ Vertex 3 128GB SSD; WDC 1TB HDD;
XFX Radeon HD 7970;
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.