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

Add Perlin-Noise #1269

Closed
wants to merge 4 commits into from
Closed

Conversation

SharkPool-SP
Copy link
Collaborator

Simple Perlin Noise Extension utilizing built in methods and not libraries 👍
image

@WAYLIVES
Copy link

Hello, cool extension!!! I just didn't quite understand how to work with it. Could you show through the screenshots what can be done with this extension?

@SharkPool-SP
Copy link
Collaborator Author

Hello, cool extension!!! I just didn't quite understand how to work with it. Could you show through the screenshots what can be done with this extension?

Basically you generate noise which can be used for making terrain in 2d or 3d games.

@WAYLIVES
Copy link

Hello, cool extension!!! I just didn't quite understand how to work with it. Could you show through the screenshots what can be done with this extension?

Basically you generate noise which can be used for making terrain in 2d or 3d games.

Oh, OK, got it ;)

@c00lkase
Copy link

c00lkase commented Apr 6, 2024

really cool extension! it can probably fix the formatting issue if you run npx prettier --write path/to/file.js

@SharkPool-SP
Copy link
Collaborator Author

The problem is idk where to run that

@c00lkase
Copy link

c00lkase commented Apr 6, 2024

You can run it anywhere as long as the path given leads to your JavaScript file

@SharkPool-SP
Copy link
Collaborator Author

You can run it anywhere as long as the path given leads to your JavaScript file

What counts as "anywhere"

@CST1229
Copy link
Collaborator

CST1229 commented Apr 6, 2024

really cool extension! it can probably fix the formatting issue if you run npx prettier --write path/to/file.js

no, use npm run format in the repo folder (so it gets formatted according to the repo's style)

@c00lkase
Copy link

c00lkase commented Apr 6, 2024

no, use npm run format in the repo folder (so it gets formatted according to the repo's style)

ohh ok, i saw that way but i've used the way i recommended and ended up passing all checks

@SharkPool-SP
Copy link
Collaborator Author

really cool extension! it can probably fix the formatting issue if you run npx prettier --write path/to/file.js

no, use npm run format in the repo folder (so it gets formatted according to the repo's style)

wheres that

@c00lkase
Copy link

c00lkase commented Apr 7, 2024

repo folder is the folder you pulled the repository from

@SharkPool-SP
Copy link
Collaborator Author

repo folder is the folder you pulled the repository from

Do you have a video, sorry for being stupid but have 0 idea what's going on

@CST1229
Copy link
Collaborator

CST1229 commented Apr 7, 2024

really cool extension! it can probably fix the formatting issue if you run npx prettier --write path/to/file.js

no, use npm run format in the repo folder (so it gets formatted according to the repo's style)

wheres that

it's the folder that contains the package.json and stuff, it looks like this

image

@SharkPool-SP
Copy link
Collaborator Author

really cool extension! it can probably fix the formatting issue if you run npx prettier --write path/to/file.js

no, use npm run format in the repo folder (so it gets formatted according to the repo's style)

wheres that

it's the folder that contains the package.json and stuff, it looks like this

image

So I have to download the repo to my computer?

@c00lkase
Copy link

c00lkase commented Apr 8, 2024

You needed to follow the "A better development server" step, which had you pull the repo to your computer

@GarboMuffin GarboMuffin added the pr: new extension Pull requests that add a new extension label Oct 14, 2024
@SharkPool-SP
Copy link
Collaborator Author

Deprecated:

#1815

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr: new extension Pull requests that add a new extension
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants