UE 5 TUTORIAL - How to pass DATA (Variables) from LEVEL to LEVEL using GAME INSTANCE.

[@navidumardaraz7163]

Great explanation

[@Fioelkais]

Thanks for the clear and concise explanations!

[@ThePavilionWeb]

Very useful, thanks for sharing!

[@springcar]

Useful work. Wish you success creating

[@KamskiStudio]

Thank you very much :)

[@pablito5326]

This Helped me carry over inventory Data to a new level Thank you. I now also understand my inventory code better Thank you for that as well 🙏

[@ECHSBACHS]

Thanks! : )

[@DiasJohnDias]

Tks man!

[@Gibon123_]

fajny tutorial tylko mozesz mi powiedziec czy jak sie wyjdzie z gry tez te kolory beda zapisane? z góry dziekuje za odpowiedz.

[@alaabahattab]

How do you go back and forth without loading or anything?

[@tejassaran4462]

helped in my first project

[@siepath]

Can you make a tutorial for score system in Multiplayer using Game State? Thank You

[@noeantoniosierraortega5923]

how would i do this if im trying to pass inventory such as weapons and healing items? passing variables makes sense but is it possible to save actual weapons?

[@Revotur]

Czy jest jakaś wada w stosowaniu Game Instance?

[@AwsD]

Hi, Is it possible to use interfaces to share the variable containing color and avoid casting? //OR making interface that connect to one small variable holing blueprint that's present on booth maps, and on that maps load - get the color from the interface connected to that variable holing blueprint. I don't know how exactly the engine allocates and frees the memory and blueprints, so idk if map change to another would result in that blueprint reseting or not.

[@nexus1g]

There's no reason to avoid making a hard reference like casting in this case. The game instance will always be loaded into memory, which is the reason we want to avoid casting in most cases (e.g. we don't want to load an enemy into memory that may not even appear on a level). Making a hard reference is fine for things that will always be loaded regardless.

[@NeatWolf]

Hi there - I'm assuming this does not stop to "Colours". Is it good practice to use the GameInstance as a Global Variables/Systems container? I'm "kind of" new to UE5 and coming from Unity and a programming background. This sounds a bit like a persistent level/entity used as Singleton? What about saving the state of the game? Are there better ways to do this (both passing data and saving the game state) - or is this solution targeted at low-complexity, entry level projects?

[@pro.giciel9084]

If you can do C++ you should look into subsystems, there is gameinstance subsystem, and others but you can specified them how you want without the GI being a mess and can be replicated. For save/load, UE already has this system in place, look at savegame blueprint, it's really easy to implement.

[@МартаРыбий]

Thanks

[@klovvin]

This is bad practice because it would get messy fast. Might be a time to use a Struct or a Saveslot file.

[@BKay121]

You sound like gatis kandis from Got Takent