Gooey respawning

[iojw]

Based on some of my testing while writing up the test plan, after spawning when I first load the world, Gooey still seems to respawn at random timings even as I remain in the same area. There doesn't seem to be anything specific that triggers this respawning.

Also, here are some minor spelling mistakes in Gooey's dialog that should be easy to fix 🙂 dungoen -> dungeon Thats -> That's

[flo]

Whenever Gooey spawns/teleports to you he has a new quest. Thanks for the typo findings.

[flo]

Wow you put a lot of effort in that test plan.

If you are also interested in adding new dungeon rooms to gooey's quests or new quests or other content let me know

[flo]

To explain the spawning a bit further:

The game searches the area near the player for possible dungeon spawn locations. If one is found it checks if gooey can be spawned in a good way (e.g. infornt of player, not in or behind wall). There is also a cooldown (I think it was 1 minute) after a dungeon got found to prevent gooey from offering constantly quests.

[iojw]

Hey @flo, sorry for not replying to your irc message earlier, was asleep.

No problem with the test plan, it was quite fun making it 😄. Those skeletons are pretty spooky!

Ah I see, if that's intended you can go ahead and close this then. Will definitely tell you if I come up with any ideas.

[Cervator]

Hey @flo :-) Yeah lots of good activity from our GCI students. Maybe we could make a multi-instance task that requests the student to add a new room type? (pinging @skaldarnar @rzats @nihal111)

As for the spawning could a check be added for an existing Gooey within range x ? Since then you could prevent the sort of odd respawning of an already existing Gooey

[flo]

Hmm no I don't think we schould have people been paid to make new rooms. It is actually fun to add rooms when you figure out how and is basically just building ingame plus some copying together of json. I still plan to add at dome point to add a better structure template editor to get rid of that manual json editing at the end(with @rzats treeview component).

[Cervator]

Oh GCI works a little different than that. Unlike GSOC which is university students being paid by Google to work full time over the summer GCI is pre-university students doing tasks to learn more about open source and coding. There are some swag-based prizes like shirts and hoodies, with a few grand prizes being trips to visit the Google campus.

So this is a much more enthusiasm-directed effort than paid work :-) And the tasks are meant to average 3-5 hours so learning how the GQ module and the structural templates work then making one new room seems just about the right scope for one task.

[flo]

ok, well if it is like this (Skaldanar just mentioned it also via slack to me) then nothing speaks against such a task. It might actually be a good idea :)

[rzats]

@flo: I've added the task to the GCI website (here's how it looks from a student's point of view: https://codein.withgoogle.com/tasks/5112862332682240/), let me know if any changes are needed 🙂 We could also send you a GCI mentor invite so that you can review this particular task!

[flo]

Well you can send me a CGI mentor invite, but in the next few days I won't have time to respond properly.

I think the task could be changed to create a new quest for the gooey's quest module. And not as a separate module, but as a PR for it.

The quest could simply generate one of the following structures:

• Sunken ship
• Underwater cave entrance with some glowing blocks/cystals
• Crypt with the option to have it be a entrance to a dungeon.

[Cervator]

@flo: invite sent :-)

Looks like another address on your domain got invited already, probably only want to accept one invite. There's another 3 weeks left so there's time to get more stuff done.

We're getting used to "task chains" of multi-instance tasks so maybe something like this could work:

• A simple intro (existing task) - make any structure template anywhere. We could put those to use later somewhere else or not
• Enhance GooeysQuests by adding a new dungeon segment and test out that it gets used on occasion (gets the student used to hooking into the existing system)
• Create a new quest line with its own procedural structure with multiple segments picked at random / as appropriate by the location (gets the student through the process of editing Gooey's UI lineup and picking a suitable spot in the terrain)

I might try to add those soon when I find time. Sound like a good idea? Might need some guidance from you on the details but that can be later (we can prepare tasks but then not publish them)