Skip to content

Import/Export player.dat Files #88

@jessedufrene

Description

@jessedufrene

I am redoing my entire server and unfortunately i have run into a wall. In the first server, i had multiverse core and portals. i had the main worlds (world, world_nether, world_the_end) and i had a protected plot world as a safe haven for the members' important belongings. (using multiverse core and portals, and plotme for plots). the inventories were automatically linked together (and stored in \world\players\usernamehere.dat) so i didnt need mv inventories for what i was doing.

now i have a brand new server. i redid almost everything from the ground up. but i took the main worlds from the 1st server and put em in the new one as multiverse worlds. because of the setup i want on my new server, i now need the mvinventory. and the problem is i cant do anything to get my members' inventories on to the multiverse world (that used to be the main world on the 1st server) without having it on the main world as well (i want it to be 2 different inventories). i have tried several things but it just comes down to figuring out how to import or convert my players' vanilla inventories to mvinventories.

the inventories i need to convert to are located at \plugins\Multiverse-Inventories\group\my2ndgroup\usernamehere.yml

(1st server inventories are .dat while 2nd server with MVInv is .yml, which i need to convert to)

i have all the config files set up correctly and working the way i want it. the inventories are separated between the worlds successfully, but i still need the old inventories from the first server on only the multiverse worlds.

sorry if this is long and repetitive, i did my best to explain things. thank you for any help you can give. :D

EDIT: i have experimented on this issue greatly and have concluded the only current way for me to convert the .dat files to .yml would either to 1) get my old members to join while the server is set up so the inventories are linked between worlds (so mvInv creates .yml files for them) or to 2) use a hacked client to log in as each member's username manually. both options are out of the question for me.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Resolution: AcceptedMV-Team is aware of the issue/PR and will be looking into it.Type: IdeaSuggestion for a new feature or enhancement.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions