{"id":1516,"date":"2025-05-11T18:53:43","date_gmt":"2025-05-11T18:53:43","guid":{"rendered":"https:\/\/sites.wsagames.com\/et4g23\/?p=1516"},"modified":"2025-05-11T19:22:13","modified_gmt":"2025-05-11T19:22:13","slug":"gateway-scenes","status":"publish","type":"post","link":"https:\/\/sites.wsagames.com\/et4g23\/2025\/05\/11\/gateway-scenes\/","title":{"rendered":"Gateway Scenes"},"content":{"rendered":"\n

Although their respective dungeons wont be a part of the vertical slice, their gateway scenes will still be in the game to show them off.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

In the hub scene, it is simple enough to create a transition to each of the gateway scenes, simple a matter of loading the scene when the player collided with a certain trigger.<\/p>\n\n\n\n

However, getting the player to spawn in a certain area of the Hub scene when the player returns from a gateway scene is a lot more complicated. To do this I created three new C# scripts, a ‘Door’ script<\/em><\/strong>, a ‘PlayerSpawnPoint’ script<\/strong><\/em> and a static ‘SceneDoorData’ script<\/strong><\/em>.<\/p>\n\n\n\n

\n
\n

The Door script<\/strong><\/em> stored data on what scene was going to be loaded if the player interacted with it.<\/p>\n\n\n\n

It also stored the data of the PlayerSpawnPoint gameobject in the next scene the player would spawn at.<\/p>\n<\/div>\n\n\n\n

\n
\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure><\/div><\/div>\n<\/div>\n\n\n\n
\n
\n

The PlayerSpawnPoint script<\/strong><\/em> stored data on the Door of the previous room, and if the player went through the door correlating to it, it would set the player’s transform.position to the correct place.<\/p>\n\n\n\n

The correct place being the transform <\/em><\/strong>of the PlayerSpawnPoint gameobject<\/strong>.<\/p>\n<\/div>\n\n\n\n

\n
\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n<\/div>\n<\/div>\n\n\n\n
\n
\n

The SceneDoorData script <\/strong><\/em>was a simple one that stored the data of where the player should end up in the next scene, however it was necessary as a static class so that the data wouldn’t be destroyed when the next scene was loaded.<\/p>\n<\/div>\n\n\n\n

\n
\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n<\/div>\n<\/div>\n\n\n\n

The following is an example of what the Anger Gateway scene transition looked like:<\/p>\n\n\n\n