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

New extension: MoreEventsFor3D #1348

Closed
3 tasks done
Kravataf opened this issue Aug 21, 2024 · 1 comment
Closed
3 tasks done

New extension: MoreEventsFor3D #1348

Kravataf opened this issue Aug 21, 2024 · 1 comment
Labels
✨ New extension A new extension

Comments

@Kravataf
Copy link

Description

adds new events to make using the native 3d easier

How to use the extension

currently there are 2 events (there were more but got deleted because they didnt work properly..)

1: Raycast hit side of block? (Raycaster3D)

  • checks if raycaster3D (different extension) hit side of 3D Box object.. this can be helpful when making minecraft-like building system or stuff like that!

2: Rotate like FPS camera (MousePointerLock)

  • the basic camera rotation (+ clamping) you just dont need to make the same events each time

Checklist

  • I've followed all of the best practices.
  • I confirm that this extension can be integrated to this GitHub repository, distributed and MIT licensed.
  • I am aware that the extension may be updated by anyone, and do not need my explicit consent to do so.

What tier of review do you aim for your extension?

Community (Unreviewed)

Example file

moreevents3dexample.zip

Extension file

MoreEventsFor3D.zip

@Kravataf Kravataf added the ✨ New extension A new extension label Aug 21, 2024
Copy link
Contributor

👋 Thanks for your submission! Unfortunately, all submitted extensions have to meet some minimal quality standard - the extension best practices - and our system has found that your extension does not fully comply 😔. You can find all of those rules on the GDevelop wiki.

The following issues have been found by the system concerning the respect of those best practices by your extension:

  ⟶ ❌ [Dots in sentences]: Field 'shortDescription' of the extension description misses a dot at the end of the sentence!
  ⟶ ❌ [Filled out names and descriptions]: Required field 'description' of the function 'raycasthitsideofblock' is not filled out!
  ⟶ ❌ [Filled out names and descriptions]: Required field 'description' of the function 'raycasthitsideofblock parameter 'block' is not filled out!
  ⟶ ❌ [Filled out names and descriptions]: Required field 'description' of the function 'fpscamerarotate' is not filled out!
  ⟶ ❌ [Filled out names and descriptions]: Required field 'description' of the function 'fpscamerarotate parameter 'Object' is not filled out!
  ⟶ ❌ [PascalCase for internals names]: Internal name 'raycasthitsideofblock' should begin with an uppercase letter (Raycasthitsideofblock)!
  ⟶ ❌ [PascalCase for internals names]: Internal name 'fpscamerarotate' should begin with an uppercase letter (Fpscamerarotate)!

Please update your original submission post with a new zip file containing your extensions updated to follow those guidelines 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✨ New extension A new extension
Projects
None yet
Development

No branches or pull requests

1 participant