Small QoL Improvements

[Hasrat]

Unless I'm missing it, I'd really like to see some hotbar transparency sliders. Preferably ones I could set per hotbar (i.e. hotbar 7 is in a place that sometimes fills with other [often useless] information, would like to have it somewhat transparent, but every other hotbar is fine).

[Khemorex]

im not sure if it was mentioned yet somewhere , but it would be nice if we could have 2 chat boxes with tabs , right now u can only have more then one tabs in the main chat box , if u pull something out then its just a solo chat box , would be nice if there was an option so we could split the 4 chat tabs in like 2 x 2 chat windows instead ^^

or even better if u could pull out some chat tabs on to the 2nd screen ^^

[Jpec07]

For RMT reporting, adding the "Report RMT Activity" option to the right click context menu for targets would be extremely helpful. I've come across numerous bots while leveling recently, and there is no easy way to report their cheating. While I could open a ticket, there are some problems:

• They use junk names which are hard to type.
• Because of how fast they teleport around the map, I cannot isolate their names before they've moved.
• Even if I took a screenshot, they usually stand on top of each other, so seeing their names is impossible.

Fortunately, each of these has another simple QoL solution:

• Add an option to copy a player's/target's name to the clipboard from the right click context menu for target players.
• Add a piece of verification logic to the middleware endpoint for updating location that checks if a player could even actually move that quickly (I'll update this post in a few minutes with some example logic in JavaScript format).
  EDIT:

  //	Position object class
  //	x, y, z as coordinates
  function Position(x, y, z)
  {
  	if(typeof(x) == "undefined" || !x
  	|| typeof(y) == "undefined" || !y
  	|| typeof(z) == "undefined" || !z)
  	{
  		return new Error("Position: must define x, y, and z as coordinates.");
  	}
  	const X = Number(x);
  	const Y = Number(y);
  	const Z = Number(z);
  	//	Setting the time: JavaScript returns milliseconds, but we only need to work in seconds (cuts down on calculation effort).
  	const Time = Math.floor(Date.now()/1000);
  	/*	function Position.validate()
  	 *
  	 *	Validates whether or not this position is acceptable within the constraints of the system.
  	 *
  	 *	@param oldPos (Position) - the old position to check against
  	 *	@param opt (Object) - The options for the validation. Required:
  	 *		dim: whether to use 2 or 3 dimensions in the rate calculation.
  	 *		maxRate: the max rate, as units of distance per second
  	 */
  	this.validate = function(oldPos, opt) {
  		//	First check if oldPos is a Position object, and opts have everything we need
  		if(!(oldPos instanceof Position))
  		{
  			console.error(new Error("Position.validate(): oldPos is not a position!"));
  			return false;
  		}
  		else
  		//	Next check if opt is valid
  		if(typeof(opt) != "Object"
  		|| !('dimensions' in opt)
  		|| !opt.dimensions
  		|| !('maxRate' in opt)
  		|| !opt.maxRate)
  		{
  			console.error(new Error("Position.validate(): Some required options missing.");
  			return false;
  		}
  		else
  		{
  			var deltaX = Math.abs(X - oldPos.getX()),
  				deltaY = Math.abs(Y - oldPos.getY()),
  				deltaZ = Math.abs(Z - oldPos.getZ()),
  				deltaTime = Math.abs(Time - oldPos.getTime());
  			var deltaXY = Math.sqrt(deltaX^2 + deltaY^2);
  			var deltaXYZ = Math.sqrt(deltaXY^2 + deltaZ^2);
  			var rate = 0;
  			if(opt.dim <= 2)
  			{
  				rate = deltaXY/deltaTime;
  			}
  			else
  			if(opt.dim >= 3)
  			{
  				rate = deltaXYZ/deltaTime;
  			}
  			//	Allowing some leniency for latency
  			if(rate > opt.maxRate*1.5)
  			{
  				return false;
  			}
  			else
  			{
  				return true;
  			}
  			
  		}
  	}
  	this.getX = function()
  	{
  		return X;
  	}
  	this.getY = function()
  	{
  		return Y;
  	}
  	this.getZ = function()
  	{
  		return Z;
  	}
  	this.getTime = function()
  	{
  		return Time;
  	}
  }
  
  //	On middleware call to register position, call this method:
  
  Character.prototype.setPos = function(x, y, z)
  {
  	var newPos = new Position(x, y, z);
  	if(newPos.validate(this.position, {"dim": 2, "maxRate": this.getMaxVelocity()}))
  	{
  		//	Position is valid, so update it on the Character.
  		this.position = newPos;
  	}
  	else
  	{
  		//	Position is invalid, so flag this character for scrutiny so the GMs can nuke their cheating arses from orbit.
  		this.flagForRMTReview();
  	}
  }

• Add an option to the UI configuration to control how the behavior of overlapping status bars (e.g. overlap, cluster, list, etc.).

All of these would make it easier for us to help the GMs and support staff combat the problems of botting and RMT, by neutering the ability of botters to generate the supply.

[rockint]

The game gets way too quiet when friends aren't on, and linkshells aren't exactly advertised, so how about an optional global chat channel so that people in this game can start talking to each other?

[Vshunyi]

What about a hotbar copy? Like how you can copy HUD 1 to HUD 2 to make things faster if it's just for minor changes. It's not game-breaking, but would be convenient. Especially on the controller since you can't just drag and drop skills as easily as the KB+M crowd.

[Niwashi]

What about a hotbar copy? Like how you can copy HUD 1 to HUD 2 to make things faster if it's just for minor changes. It's not game-breaking, but would be convenient. Especially on the controller since you can't just drag and drop skills as easily as the KB+M crowd.

Already exists.

/hotbar copy [class 1] [#1] [class 2] [#2]
　　Copy the contents of [class 1] hotbar [#1] to the [class 2] hotbar [#2].
　　The subcommand "current" can be used to specify your current class.
　　The subcommand "share" can be used instead of a class to specify your shared hotbar.

or

/chotbar copy [class 1] [number 1] [class 2] [number 2]
　　Copy the contents of [class 1] cross hotbar [number 1] to the [class 2] cross hotbar [number 2].
　　The subcommand "current" can be used to specify your current class.
　　The subcommand "share" can be used instead of a class to specify your shared hotbar.

http://na.finalfantasyxiv.com/lodest.../text_command/ (under the "hotbars" tab on the left). There are other options under /hotbar and /crosshotbar as well, besides copying the whole thing. Those commands can also be used to set specific actions to the bar, or to control the share and display settings.

[Jpec07]

An option to make my mouse cursor more visible would be extremely helpful.

[Hasrat]

Feature I'd love to see. "Sort" option that applies only to selected tab of inventory. Having inventory already psuedo-sorted into respective tabs manually, sometimes would like to be able to sort within each tab.

[Sida]

An option to make my mouse cursor more visible would be extremely helpful.

At least there is already a keybind that makes the mouse cursor be very easy to spot when you press it. Mouse locator, or some such.

[Sicycre]

Hi, everyone!

Thank you all for the quality of life suggestions and continued feedback to help improve FFXIV!

Today I bring news of a feature which players that have a number of retainers in various markets should enjoy. In 4.0, we'll be adding a display so that you'll be able to tell which region your deployed retainers are selling items in.

Also, when submitting suggestions and feedback, we ask you to please include as many details as possible to help us best relay your ideas to the development team! Thanks!