OTClient Restoring Open Backpacks on Login – Is It Possible?

[Kelah]

Hello everyone,


I would like to know if anyone has managed to make the client automatically reopen the backpacks that the character had open before logging out.


Specifically, when a character logs back in, is it possible to restore the same backpacks (and their order) that were open at the moment of disconnection? This could be either through a client feature, a server-side implementation, or any workaround you may have found.


At the moment, I managed to reopen the backpacks on login, and I can see the following logs:

[Containers] No saved containers file for GM Adoriban
[Containers] Saving opened containers...
[Containers] Container 0 is in inventory slot 3
[Containers] Container 1 is nested (item id: 2854)
[Containers] Container 2 is nested (item id: 2854)
[Containers] Container 3 is nested (item id: 2854)
[Containers] Saved 4 containers to file for GM Adoriban
[Containers] Restoring 4 containers for GM Adoriban
[Containers] Opened container from inventory slot 3
[Containers] Opening 3 nested containers...
[Containers] Opened nested container (item id: 2854)
[Containers] Opened nested container (item id: 2854)
[Containers] Opened nested container (item id: 2854)




The issue is that, since the nested backpacks all have the same item ID, only one of the three that were previously open is actually restored correctly.


Also, to clarify my original goal: what I was really looking for was not just reopening the backpacks after login, but preventing them from closing in the first place — so that when the character logs back in, the backpacks are already open exactly as they were before logging out.


If anyone has dealt with a similar situation or has suggestions on how to properly persist container states across sessions, I would really appreciate your input.


Thank you in advance.

 

[Tenzhiro]

Saving opened backpacks and sending them onlogin · OTCv8/forgottenserver@08b6839

A free and open-source MMORPG server emulator written in C++, compatible with OTClientV8 - Saving opened backpacks and sending them onlogin · OTCv8/forgottenserver@08b6839

github.com

 

[Acubens]

Did you have clown dick for breakfast, or why are you being so funny?

Why get annoyed when someone suggests using the search function before starting a new thread that has been solved before xD!?!

This is how new accounts users come to Otland, very decent greetings but in reality they are demons in disguise looking for help

 

[Kelah]

Why get annoyed when someone suggests using the search function before starting a new thread that has been solved before xD!?!

This is how new accounts users come to Otland, very decent greetings but in reality they are demons in disguise looking for help

It’s assumed that when someone creates a new post, it’s because they’re looking for help since they couldn’t find what they were looking for. Do you seriously think everyone is an idiot like you?


Thanks for your miserable help. I already solved it thanks to other people. You were completely useless—only good for trying to be funny.

Post automatically merged: Dec 30, 2025

Saving opened backpacks and sending them onlogin · OTCv8/forgottenserver@08b6839

A free and open-source MMORPG server emulator written in C++, compatible with OTClientV8 - Saving opened backpacks and sending them onlogin · OTCv8/forgottenserver@08b6839

github.com

Thank you, my friend. I solved it through another approach. it’s not the client that I need to modify. I appreciate your help!

 

[Sorky]

it’s not the client that I need to modify

I would strongly advise against keeping such a script on the server side; the client should be responsible for this functionality.

 

[Kelah]

I would strongly advise against keeping such a script on the server side; the client should be responsible for this functionality.

The problem I have is that the client does not differentiate between IDs; that is, if there are 2 or 3 backpacks open with the same ID, it only opens one.

 

[Sorky]

The problem I have is that the client does not differentiate between IDs; that is, if there are 2 or 3 backpacks open with the same ID, it only opens one.

The problem with your approach is that you don’t really want to open a specific backpack. A better solution would probably be to store the opened backpacks in a tree, then reopen them by opening the slots “by hand”. This way you’re not operating on ItemIds but on the item structure itself, and it should behave much more predictably.

 

[Tenzhiro]

It’s assumed that when someone creates a new post, it’s because they’re looking for help since they couldn’t find what they were looking for. Do you seriously think everyone is an idiot like you?


Thanks for your miserable help. I already solved it thanks to other people. You were completely useless—only good for trying to be funny.

Post automatically merged: Dec 30, 2025

Thank you, my friend. I solved it through another approach. it’s not the client that I need to modify. I appreciate your help!

This is for Server.

 

[Kelah]

The problem with your approach is that you don’t really want to open a specific backpack. A better solution would probably be to store the opened backpacks in a tree, then reopen them by opening the slots “by hand”. This way you’re not operating on ItemIds but on the item structure itself, and it should behave much more predictably.

That is exactly what I want to achieve! I had made it so the main backpack opens on login, but sometimes it opens and sometimes it doesn’t.


Have you seen any guide that explains how to do what you’re telling me?


The guides I’ve been looking at didn’t help me at all.