Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes for alchemy dude's quest part 2 #2362

Merged
merged 2 commits into from
Sep 15, 2023
Merged

Fixes for alchemy dude's quest part 2 #2362

merged 2 commits into from
Sep 15, 2023

Conversation

scooterboo
Copy link
Contributor

Description

Make platforms able to reset: First part of the puzzle.
A seelie goes around some torches when you get near to the seelie. You can trigger the seelie again after it has made a circuit. It also seems to cancel a timer on the torches before lighting them again. Logically you ought to be able to do that without bailing the function early.

Fix Seelies: Second part of the puzzle.
Implemented HandlerClientScriptEventNotify which is the source for EVENT_AVATAR_NEAR_PLATFORM. Shoutout to @Hartie95 for the code. I took the opportunity to also quiet down the platform functions. They should mostly be good to go now.

Issues fixed by this PR

Minor technical things that didn't work in the puzzle in alchemy dude's quest.

SEELIES WORK! WOO HOO!

Type of changes

  • Bug fix
  • New feature
  • Enhancement
  • Documentation

Checklist:

  • My code follows the style guidelines of this project
  • My pull request is unique and no other pull requests have been opened for these changes
  • I have read the Contributing note and Code of conduct
  • I am responsible for any copyright issues with my code if it occurs in the future.

platforms apparently are able to run again once reaching the last point. As well, canceling a timer seems to return a 0, not a 1
Added HandlerClientScriptEventNotify (shoutouts to Hartie!) and cleaned up the platform stuff in ScriptLib.

There is a problem with HandlerClientScriptEventNotify where the client seems to only pass 0 into param1 instead of the configId. I coded in a workaround, but someone with greater access to things should check up on what is going on
@KingRainbow44 KingRainbow44 merged commit 84e1371 into Grasscutters:development Sep 15, 2023
2 checks passed
@scooterboo scooterboo deleted the patch-2 branch September 15, 2023 01:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants