Cross Platform: Does not meet requirements situation.

Hey all,

I searched for a resolution within the forums. Got no matches.

I've been trading items successfully however it's been a bit frustrating. When trading the same situation arises:

Game is created by me or the other. The person attempting to join is told that they do not meet the game requirements. The error says: You must be between levels XX and XX. XX is the level of the person who created the game. If they are level 1 then XX and XX = 1 and 1. If they are 88 then XX and xx = 88 and 88. Meaning that you need to be the same level to trade?

The last two trades were both on PS5 consoles in North America yet the issue still happened. However, both trades were with a person that is flagged as PC. So I suspect a Cross Platform issue is at the heart of it.

I've read that if a PC player wants to trade with a PlayStation player, the PC play must have registered both PC and PlayStation versions of the game first on BattleNet. Am I right? Or do I need to buy a PC version of the game and install it/ register it with BattleNet?

This is nerve wracking as I've doubled, tripled and quadruple check my settings. My settings are correct as people enter and leave my public games of whom the trading person should be able to see and join. These other players are of many different levels yet my trading partner is stuck with XX and XX?

Was there a Trading Rules Document that I forgot to read? What is going on?

I just found the document. Ignore.

After reading that Cross Platform thread... I'm depressed. LOL. This is hopeless and is too much work. Pulling up stakes.

No it's been an issue since last update. But someone wrote this

post4088329.html#p4088329

Hope this helps

DwPvsZtO wrote: 10 hours ago

No it's been an issue since last update. But someone wrote this

post4088329.html#p4088329

Hope this helps

Thanks. I'll read through the article.

QuadraHedron wrote: 10 hours ago

After reading that Cross Platform thread... I'm depressed. LOL. This is hopeless and is too much work. Pulling up stakes.

Make a public game with a custom name and password. Then the forced level restrictions aren't there. The glitch is when you create a private game. (EDIT: I can only confirm this works for xbox, but it's likely to work on Switch, and PS5).
And PC can't trade directly with console. For example I play PC and Xbox. But I can log in with the same account on either system, just not at the same time. If I want to trade with PC I log into PC. If I want to trade on xbox I log into xbox.

The level restriction error despite not having any level restrictions enabled is a newish bug that was introduced in the latest patch. It affects all platforms as far as I know, but there are ways to get around it.

(NOTE: the below is about PC)

It depends on where you're joining from (where in the game/menu you are when you join the other game);

1. If you're coming from inside a quick-play game, you get the level restriction error (whether if joining via friend list or if accepting a game invitation doesn't matter).
2. If you're coming from inside a lobby created game, it works.
3. If you're coming from the lobby screen (not actually inside a game), it works.

The difference between case #1 and #2 is -

• in case #1, the game throws you back to the char select screen before attempting to join the target game - this seems to be the trigger.
• in case #2, the game throws you back to the lobby screen before attempting to join the target game

I.e., as far as I can tell, it does not matter how the game you're joining was created - it doesn't matter if you're joining a quick-play game or a game created via lobby - so the game creator's options are irrelevant.

NOTE: the above is on PC - the cause and workaround might not be exactly the same on console. But it should work on all platforms if you join via game name + password (since you're effectively joining via a lobby where you have to manually input game name & password) instead of joining via friend list or invite.

ShadowHeart wrote: 8 hours ago

The level restriction error despite not having any level restrictions enabled is a newish bug that was introduced in the latest patch. It affects all platforms as far as I know, but there are ways to get around it.

(NOTE: the below is about PC)

It depends on where you're joining from (where in the game/menu you are when you join the other game);

1. If you're coming from inside a quick-play game, you get the level restriction error (whether if joining via friend list or if accepting a game invitation doesn't matter).
2. If you're coming from inside a lobby created game, it works.
3. If you're coming from the lobby screen (not actually inside a game), it works.

The difference between case #1 and #2 is -

• in case #1, the game throws you back to the char select screen before attempting to join the target game - this seems to be the trigger.
• in case #2, the game throws you back to the lobby screen before attempting to join the target game

I.e., as far as I can tell, it does not matter how the game you're joining was created - it doesn't matter if you're joining a quick-play game or a game created via lobby - so the game creator's options are irrelevant.

NOTE: the above is on PC - the cause and workaround might not be exactly the same on console. But it should work on all platforms if you join via game name + password (since you're effectively joining via a lobby where you have to manually input game name & password) instead of joining via friend list or invite.

What Knappogue said is right on the nail for console. Had that issue myself and that was exactly what resolved it.

First off. I want you all to know that I was not passing blame at diablo2.io. diablo2.io did nothing wrong. This is not the site's fault. It is unfortunate that the developer released this situation upon their fans and players. I may have been stuck and caught up in my own failure path. Very frustrated, I made some comments that may have hurt some members in this community. For that, I apologize.

I have read and understand, though not tested, the process of using a Lobby created Custom Game(Game name and Password) or Joining a game from the Lobby in order to avoid the glitch. Hopefully Blizzard will have this issue resolved very soon and game play can feel like game play once again.

QuadraHedron wrote: 1 hour ago

First off. I want you all to know that I was not passing blame at diablo2.io. diablo2.io did nothing wrong. This is not the site's fault. It is unfortunate that the developer released this situation upon their fans and players. I may have been stuck and caught up in my own failure path. Very frustrated, I made some comments that may have hurt some members in this community. For that, I apologize.

I have read and understand, though not tested, the process of using a Lobby created Custom Game(Game name and Password) or Joining a game from the Lobby in order to avoid the glitch. Hopefully Blizzard will have this issue resolved very soon and game play can feel like game play once again.

I just reread the entire thread and I don't get the impression you were mad at dablo2.

Io or any of its members. Your frustration accurately comes out at Blizzard and the semi-opaque cross-platform play. You're fine dude. This game has a unique way of finding and getting our each of our last nerves