Creepso/Wplace-BlueMarble
1
0
Fork 0
mirror of https://github.com/SwingTheVine/Wplace-BlueMarble.git synced 2026-04-20 18:32:04 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

WPF plugin test

Browse source
This commit is contained in:
AloeSapling 2025-08-15 17:52:56 +02:00
parent 21ae2e8eab
commit c57c61041a
10 changed files with 2168 additions and 117 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
.eslintignore
View file

@ -1 +0,0 @@
*

1
.prettierignore
View file

@ -1 +0,0 @@
*

1746
package-lock.json generated
View file

File diff suppressed because it is too large Load diff

8
package.json
View file

@ -7,10 +7,16 @@
"patch": "node build/patch.js && npm run build"
},
"devDependencies": {
"@eslint/js": "^9.33.0",
"esbuild": "^0.25.0",
"eslint": "^9.33.0",
"globals": "^16.3.0",
"jsdoc": "^4.0.4",
"minami": "^1.2.3",
"terser": "^5.43.1"
"prettier": "^3.6.2",
"prettier-plugin-curly": "^0.3.2",
"terser": "^5.43.1",
"typescript-eslint": "^8.39.1"
},
"dependencies": {
"@types/greasemonkey": "^4.0.7"

184
src/blah copy.js Normal file
View file

@ -0,0 +1,184 @@
/** This is a summary of the file's purpose as a top-of-file JSDoc comment.
* This is an optional, detailed explanation.
* The first line of the comment should be 1 sentence.
* If more sentences are needed, they are put after the first line.
* @since 1.2.3
* @author SwingTheVine
*/
/*! Import lines go here, usually in 1 logic block */
import fs from 'fs';
import { foo, bar } from './foobar.js';
import { foo } from './foobar.js'; /*! There is ALWAYS a whitespace around the braces for imports. */
/*! Import lines can optionally be grouped into logic blocks, based on type.
* For example, all default imports could be grouped together, or all "require" imports could be in a different logic block from the "import"s.
* If multiple logic blocks are used. There must ALWAYS be a comment before the logic block that explains the common logic of why all of the imports are in this specific logic block.
* If there are multiple import logic blocks, there must ALWAYS be 1 blank line between them.
*/
// CommonJS "imports" which require "require" in order to be imported
import { createRequire } from 'module';
const require = createRequire(import.meta.url);
const terser = require('terser');
const foo = require('foo');
/*! There should ALWAYS be 1 blank line between the last import logic block, and the class definition logic block. */
/** A 1 sentence description of what the class does.
* An optional multi-line detailed description of what the class does.
* @class Foo
* @since 1.2.3
* @example
* // An example of how to use the Foo class
*/
export default class Foo {
/* An optional multi-line comment to further explain things about the Foo class.
* This is rarely used, but comes in handy when you want to explain how the inside of the class works, but you don't want to flood the class JSDoc comment with details, since the JSDoc should only contain information about how to *use* the class and what the class *does*, not how the class *works*.
* This multi-line comment should ALWAYS be right under the class definition.
*/
/*! There should ALWAYS be 1 blank line after the logic block that defines the class. */
/** This line should declare if this is the main constructor, or an overload.
* An optional description of why this constructor should be used.
* @param {*} foo - What foo is.
* @param {*} bar - What bar is.
* @since 1.2.3
* @see {@link Foo}
*/
constructor(foo, bar) { /*! Opening braces are ALWAYS on the same line as declaration */
/*! There should NEVER be a whitespace before the first variable, and after the last variable. */
/*! The blank line after the declaration is optional for constructors */
this.foo = foo; // The description of foo should go here only if there is no JSDoc...
this.bar = bar + 5; // ...but if the passed in variable is modified, a comment should be added to explain why.
this.hatMan = 'a'; /*! Constants are ALWAYS camelCase */
this.color = foo.RED_APPLE; /*! Enum variables are ALWAYS SCREAMING_SNAKE_CASE */
/*! There is NEVER a blank line after the end of the last logic block in a statement */
}
/*! Closing braces are ALWAYS on their own line if the statement contains more than 1 line of code.
* The closing brace is aligned with start of the statement.
* However, if there are multiple closing braces, they can optionally be stacked onto the same line.
*/
/** A 1 sentence description of what the function does.
* An optional multi-line detailed description of what the function does.
* @param {*} foo - What foo is.
* @param {*} [bar=''] - What bar is.
*/
function bar(foo, bar='') { /*! There should NEVER be a whitespace between the function name and the passed in variables.
* There should NEVER be a whitespace before the first variable passed in when the variables are all on the same line as the function declaration.
* There should NEVER be a whitespace after the last variable passed in when the variables are all on the same line as the function declaration.
*/
/* An optional multi-line comment to further explain things about the bar function.
* This is rarely used, but comes in handy when you want to explain how the inside of the function works, but you don't want to flood the function JSDoc comment with details, since the JSDoc should only contain information about how to *use* the function and what the function *does*, not how the function *works*.
* This multi-line comment should ALWAYS be right under the function definition.
*/
/*! There should ALWAYS be 1 blank line after the logic block that defines the function. */
// Logic blocks with short comments use single-line comments.
// Even if multiple single-line comments are needed.
foo = `${foo} ${bar} + 5 foos`; /*! Template literals are prefered over strings when concatenating. */
const barfoo = foo + 'apple'; /*! There should ALWAYS be a whitespace before and after math operators that do not use parentheses. */
const flap = String.toLowerCase(foo + '.'); /*! There should NEVER be whitespaces after the opening parentheses, and before the closing parentheses (assuming the parentheses are on the same line). */
/*! There should ALWAYS be 1 blank line between logic blocks. */
// IF bar exists, AND the length of bar is greater than 0...
if (!!bar && bar.length > 0) {
// ...then prepend bar to foo
const goo = `${bar}${foo}`;
foo = goo;
}
// IF foo exists, then set bar to foo
if (!!foo) {
bar = foo; /*! When the entire conditional statement is 1 logic block, which includes all code within the conditional statement, and the conditional statement itself, there is NEVER a blank line after the statement declaration. */
}
/*! The comment line immediately above conditional statments SHOULD be spoken form of the conditional statement.
* In addition, the comment ALWAYS uses all captital letters for logical operators and conditional statements.
* E.g., "IF", "ELSE IF", "AND", "WHILE", "XOR", "NOT", "NOR", "greater than", "integer", "one", "bitwise OR", "then", "try", "exists"
* In addition, the comment ALWAYS ends with an eclipse.
* The eclipse is continued on the start of the next comment inside the conditional statment, and finishes the "thought" about what the conditional statement does.
* If multiple comments are needed, then they MAY all start and end with eclipses to show a"continual thought process" that requires you to read multiple lines of comments, which arescattered apart.
* However, if the conditional statement is 1 logic block, which includes all code within the conditional statement, and the conditional statement itself, then no eclipse is added, and the purpose of the logic statement is combined with the comment line that contains the spoken form of the conditional statement.
* If nested logic is used within the conditional statement, it is written as follows...
*/
// IF foobar exists...
// ...AND foo exists...
// ...OR bar exists, AND goo exists...
if (!!foobar && (!!foo || (!!bar && !!goo))) {
// ...then set foobar to bar
let goo = foo * bar; // Describe why foo * bar is used
goo += 5; // Describe why 5 is being added here
foobar = goo;
}
// Sum 1 + 1, then try to set a & b to the result
const sum = ((a, b) => (a + b)); /*! Parentheses MIGHT be used around arrow functions and IIFEs. */
try {
const a, b = sum(1, 1);
} catch (exception) { /*! It is perfered that the caught error variable be named "exception" */
throw new Exception('lol get pwned');
}
} /*! There is ALWAYS no blank line after the last logic block, and the ending brace. */
/** A 1 sentence description of what the function does.
* An optional multi-line detailed description of what the function does.
* @param {Object} [object] - NEVER describe the optional object here unless there are multiple objects being passed in.
* @param {Array<string>} [object.never] - What never is.
* @param {string} [object.gonna] - What gonna is.
* @param {Boolean} [object.give] - What give is.
* @param {Number} [object.number] - What you is.
* @param {Number} [object.up] - What's up.
* @since 1.2.3
* @author SwingTheVine
* @example
* // One example
* @example
* // One example
* @example
* // One example
*/
function #foo({
never: [''], // A comment should describe each default value of these, ONLY if not described in @param
gonna: '', // Going to hold "foobar" in gonna, or default to empty string if nothing is passed in.
give: true,
you: 1,
up: 0.5, /*! Trailing comment is ALWAYS used on the last variable in objects UNLESS it causes lint warnings or errors. */
} = {}) {
never = ['foo', 'bar']; /*! Trailing comment is NEVER used on the last index of an array UNLESS it causes lint warnings or errors. */
/*! Variables are named in the order of their most common denominator of what property they share. */
const fooApple = undefined;
const fooBar = undefined;
const fooBarCarrot = undefined;
const fooBarCarrotColor = 'orange';
const fooHit = 'hurts others';
const fooHitByBarFight = 'hurts me';
const fooHitByTruck = 'hurts me more';
/*! And the variable declarations can be in logic blocks */
const bars = undefined;
const barsLocations = undefined;
const barsApple = undefined
const barDrink = undefined;
return true;
}
// Assume there is a JSDoc comment here
function call() {
#foo({
you: false,
});
}
}

191
src/blah.js Normal file
View file

@ -0,0 +1,191 @@
/** This is a summary of the file's purpose as a top-of-file JSDoc comment.
* This is an optional, detailed explanation.
* The first line of the comment should be 1 sentence.
* If more sentences are needed, they are put after the first line.
* @since 1.2.3
* @author SwingTheVine
*/
/*! Import lines go here, usually in 1 logic block */
import fs from "fs";
import { foo, bar } from "./foobar.js";
import { foo } from "./foobar.js"; /*! There is ALWAYS a whitespace around the braces for imports. */
/*! Import lines can optionally be grouped into logic blocks, based on type.
* For example, all default imports could be grouped together, or all "require" imports could be in a different logic block from the "import"s.
* If multiple logic blocks are used. There must ALWAYS be a comment before the logic block that explains the common logic of why all of the imports are in this specific logic block.
* If there are multiple import logic blocks, there must ALWAYS be 1 blank line between them.
*/
// CommonJS "imports" which require "require" in order to be imported
import { createRequire } from "module";
const require = createRequire(import.meta.url);
const terser = require("terser");
const foo = require("foo");
/*! There should ALWAYS be 1 blank line between the last import logic block, and the class definition logic block. */
/** A 1 sentence description of what the class does.
* An optional multi-line detailed description of what the class does.
* @class Foo
* @since 1.2.3
* @example
* // An example of how to use the Foo class
*/
export default class Foo {
/* An optional multi-line comment to further explain things about the Foo class.
* This is rarely used, but comes in handy when you want to explain how the inside of the class works, but you don't want to flood the class JSDoc comment with details, since the JSDoc should only contain information about how to *use* the class and what the class *does*, not how the class *works*.
* This multi-line comment should ALWAYS be right under the class definition.
*/
/*! There should ALWAYS be 1 blank line after the logic block that defines the class. */
/** This line should declare if this is the main constructor, or an overload.
* An optional description of why this constructor should be used.
* @param {*} foo - What foo is.
* @param {*} bar - What bar is.
* @since 1.2.3
* @see {@link Foo}
*/
constructor(foo, bar) {
/*! Opening braces are ALWAYS on the same line as declaration */
/*! There should NEVER be a whitespace before the first variable, and after the last variable. */
/*! The blank line after the declaration is optional for constructors */
this.foo = foo; // The description of foo should go here only if there is no JSDoc...
this.bar = bar + 5; // ...but if the passed in variable is modified, a comment should be added to explain why.
this.hatMan = "a"; /*! Constants are ALWAYS camelCase */
this.color = foo.RED_APPLE; /*! Enum variables are ALWAYS SCREAMING_SNAKE_CASE */
/*! There is NEVER a blank line after the end of the last logic block in a statement */
}
/*! Closing braces are ALWAYS on their own line if the statement contains more than 1 line of code.
* The closing brace is aligned with start of the statement.
* However, if there are multiple closing braces, they can optionally be stacked onto the same line.
*/
/** A 1 sentence description of what the function does.
* An optional multi-line detailed description of what the function does.
* @param {*} foo - What foo is.
* @param {*} [bar=''] - What bar is.
*/
#bar(foo, bar = "") {
/*! There should NEVER be a whitespace between the function name and the passed in variables.
* There should NEVER be a whitespace before the first variable passed in when the variables are all on the same line as the function declaration.
* There should NEVER be a whitespace after the last variable passed in when the variables are all on the same line as the function declaration.
*/
/* An optional multi-line comment to further explain things about the bar function.
* This is rarely used, but comes in handy when you want to explain how the inside of the function works, but you don't want to flood the function JSDoc comment with details, since the JSDoc should only contain information about how to *use* the function and what the function *does*, not how the function *works*.
* This multi-line comment should ALWAYS be right under the function definition.
*/
/*! There should ALWAYS be 1 blank line after the logic block that defines the function. */
// Logic blocks with short comments use single-line comments.
// Even if multiple single-line comments are needed.
foo = `${foo} ${bar} + 5 foos`; /*! Template literals are prefered over strings when concatenating. */
const barfoo =
foo +
"apple"; /*! There should ALWAYS be a whitespace before and after math operators that do not use parentheses. */
const flap = String.toLowerCase(
foo + "."
); /*! There should NEVER be whitespaces after the opening parentheses, and before the closing parentheses (assuming the parentheses are on the same line). */
/*! There should ALWAYS be 1 blank line between logic blocks. */
// IF bar exists, AND the length of bar is greater than 0...
if (!!bar && bar.length > 0) {
// ...then prepend bar to foo
const goo = `${bar}${foo}`;
foo = goo;
}
// IF foo exists, then set bar to foo
if (!!foo) {
bar =
foo; /*! When the entire conditional statement is 1 logic block, which includes all code within the conditional statement, and the conditional statement itself, there is NEVER a blank line after the statement declaration. */
}
/*! The comment line immediately above conditional statments SHOULD be spoken form of the conditional statement.
* In addition, the comment ALWAYS uses all captital letters for logical operators and conditional statements.
* E.g., "IF", "ELSE IF", "AND", "WHILE", "XOR", "NOT", "NOR", "greater than", "integer", "one", "bitwise OR", "then", "try", "exists"
* In addition, the comment ALWAYS ends with an eclipse.
* The eclipse is continued on the start of the next comment inside the conditional statment, and finishes the "thought" about what the conditional statement does.
* If multiple comments are needed, then they MAY all start and end with eclipses to show a"continual thought process" that requires you to read multiple lines of comments, which arescattered apart.
* However, if the conditional statement is 1 logic block, which includes all code within the conditional statement, and the conditional statement itself, then no eclipse is added, and the purpose of the logic statement is combined with the comment line that contains the spoken form of the conditional statement.
* If nested logic is used within the conditional statement, it is written as follows...
*/
// IF foobar exists...
// ...AND foo exists...
// ...OR bar exists, AND goo exists...
if (!!foobar && (!!foo || (!!bar && !!goo))) {
// ...then set foobar to bar
let goo = foo * bar; // Describe why foo * bar is used
goo += 5; // Describe why 5 is being added here
foobar = goo;
}
// Sum 1 + 1, then try to set a & b to the result
const sum = (a, b) => a + b; /*! Parentheses MIGHT be used around arrow functions and IIFEs. */
try {
const { a, b } = sum(1, 1);
} catch (exception) {
/*! It is perfered that the caught error variable be named "exception" */
throw new Exception("lol get pwned");
}
} /*! There is ALWAYS no blank line after the last logic block, and the ending brace. */
/** A 1 sentence description of what the function does.
* An optional multi-line detailed description of what the function does.
* @param {Object} [object] - NEVER describe the optional object here unless there are multiple objects being passed in.
* @param {Array<string>} [object.never] - What never is.
* @param {string} [object.gonna] - What gonna is.
* @param {Boolean} [object.give] - What give is.
* @param {Number} [object.number] - What you is.
* @param {Number} [object.up] - What's up.
* @since 1.2.3
* @author SwingTheVine
* @example
* // One example
* @example
* // One example
* @example
* // One example
*/
#foo({
never = [""], // A comment should describe each default value of these, ONLY if not described in @param
gonna = "", // Going to hold "foobar" in gonna, or default to empty string if nothing is passed in.
give = true,
you = 1,
up = 0.5 /*! Trailing comment is ALWAYS used on the last variable in objects UNLESS it causes lint warnings or errors. */,
} = {}) {
never = [
"foo",
"bar",
]; /*! Trailing comment is NEVER used on the last index of an array UNLESS it causes lint warnings or errors. */
/*! Variables are named in the order of their most common denominator of what property they share. */
const fooApple = undefined;
const fooBar = undefined;
const fooBarCarrot = undefined;
const fooBarCarrotColor = "orange";
const fooHit = "hurts others";
const fooHitByBarFight = "hurts me";
const fooHitByTruck = "hurts me more";
/*! And the variable declarations can be in logic blocks */
const bars = undefined;
const barsLocations = undefined;
const barsApple = undefined;
const barDrink = undefined;
return true;
}
// Assume there is a JSDoc comment here
call() {
foo({
you: false,
});
}
}

8
src/index.js Normal file
View file

@ -0,0 +1,8 @@
(function () {
return {
patches: [],
load: () => {
console.log("Example Plugin Loaded!");
},
};
})();

49
src/main.ts
View file

@ -1,40 +1,39 @@
import { Context } from "./types";
import { getGMResourceText } from "./utils";
import { Context } from './types';
import { getGMResourceText } from './utils';
/** Injects code into the client
* This code will execute outside of TamperMonkey's sandbox
* @param {*} callback - The code to execute
* @since 0.11.15
*/
function inject(callback: Function, context: Context) {
const script: HTMLScriptElement = document.createElement('script');
script.textContent = `(${callback})(${JSON.stringify(context)});`;
document.documentElement?.appendChild(script);
script.remove();
function inject(callback: (x: Context) => void, context: Context) {
const script: HTMLScriptElement = document.createElement('script');
script.textContent = `(${callback})(${JSON.stringify(context)});`;
document.documentElement?.appendChild(script);
script.remove();
}
const cond = true;
if (cond) {console.log('test');console.log('test');}
const context: Context = {};
// Needs to be wrapped in async functionality to keep synchronous flow with the async GM functions
(async () => {
context.HTMLData = await getGMResourceText('HTML-BM-File');
context.CSSUrl = await GM.getResourceUrl('CSS-BM-File');
context.HTMLData = await getGMResourceText("HTML-BM-File");
context.CSSUrl = await GM.getResourceUrl("CSS-BM-File");
/** What code to execute instantly in the client (webpage) to spy on fetch calls.
* This code will execute outside of TamperMonkey's sandbox.
* @since 0.11.15
*/
inject((ctx: Context) => {
console.log('Test', ctx);
/** What code to execute instantly in the client (webpage) to spy on fetch calls.
* This code will execute outside of TamperMonkey's sandbox.
* @since 0.11.15
*/
inject((ctx: Context) => {
console.log("Test", ctx)
const link: HTMLLinkElement = document.createElement('link'); // Create element in order to link css
link.rel = 'stylesheet';
link.href = ctx.CSSUrl || '';
document.head.appendChild(link); // Links the css to the document
const link: HTMLLinkElement = document.createElement("link") // Create element in order to link css
link.rel = "stylesheet";
link.href = ctx.CSSUrl || "";
document.head.appendChild(link); // Links the css to the document
document.body.innerHTML += ctx.HTMLData; // Inserts the raw html into body
}, context);
})();
document.body.innerHTML += ctx.HTMLData; // Inserts the raw html into body
}, context);
})();

9
src/manifest.json Normal file
View file

@ -0,0 +1,9 @@
{
"id": "blue-marble",
"name": "Blue Marble",
"version": "0.0.0",
"authors": ["SwingTheVine"],
"versions": {
"framework": ">=0.1.0-beta"
}
}

88
src/overlay.js
View file

@ -1,88 +0,0 @@
export const html = `<div id="bm-overlay" style="top: 10px; right: 75px">
<header id="bm-contain-header">
<div id="bm-bar-drag">
<img
src="https://raw.githubusercontent.com/SwingTheVine/Wplace-BlueMarble/main/dist/assets/Favicon.png"
alt="Blue Marble Icon - Click to minimize/maximize"
style="cursor: pointer"
onclick="VAR_clickfunc"
/>
<h1>VAR_name</h1>
</div>
<hr />
<div id="bm-contain-userinfo">
<p id="bm-user-name">Name:</p>
<p id="bm-user-droplets">Droplets:</p>
<p id="bm-user-nextlevel">Next level in...</p>
</div>
<hr />
<div id="bm-contain-automation">
<div id="bm-contain-coords">
<button id="bm-button-coords" class="bm-help" style="margin-top: 0">
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 4 6">
<circle cx="2" cy="2" r="2"></circle>
<path d="M2 6 L3.7 3 L0.3 3 Z"></path>
<circle cx="2" cy="2" r="0.7" fill="white"></circle>
</svg>
</button>
<input
type="number"
id="bm-input-tx"
placeholder="Tl X"
min="0"
max="2047"
step="1"
required="true"
/>
<input
type="number"
id="bm-input-ty"
placeholder="Tl Y"
min="0"
max="2047"
step="1"
required="true"
/>
<input
type="number"
id="bm-input-px"
placeholder="Px X"
min="0"
max="2047"
step="1"
required="true"
/>
<input
type="number"
id="bm-input-py"
placeholder="Px Y"
min="0"
max="2047"
step="1"
required="true"
/>
</div>
<label>
Upload Template
<input
id="bm-input-file-template"
type="file"
accept="image/png, image/jpeg, image/webp, image/bmp, image/gif"
/>
</label>
<div id="bm-contain-buttons-template">
<button id="bm-button-enable">Enable</button>
<button id="bm-button-create">Create</button>
<button id="bm-button-disable">Disable</button>
</div>
<textarea id="overlayMain.outputStatusId" placeholder="Status: Sleeping...\nVersion: ${version}" readonly></textarea>
<div id="bm-contain-buttons-action">
<div>
<button id="bm-button-convert" class="bm-help" title="Template Color Converter">🎨</button>
</div>
<p style="margin-top: auto">Made by SwingTheVine</p>
<!--small?-->
</div>
</div>
</header>
</div>`