Add universe (telescope / observatory / emergence) #469
Labels
No labels
breaking change
duplicate
good first issue
help wanted
invalid
question
scope: card
scope: docs
scope: game
scope: registry
scope: script
scope: tool
scope: universe
tracker
type: bug
type: card request
type: documentation
type: enhancement
type: improvement
type: parity
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
LunarTides/Hearthstone.js#469
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I want to make an "universe" tool which handles different resources. You should be able to run it and its different modules from the HUB.
Modules
Every module should be split into multiple files. A
liband amainfile atleast.Big Bang (emergance)
Handle importing, updating, reloading, creating, editing, and deleting resources. This shouldn't include a frontend per resource type, but it should include things to make the whole process smoother and more dynamic.
Observatory
This should show resources and packs as different objects in space. (Oooo, theming!)
This is my idea how it should be:
I don't really know what star clusters and galaxies should represent yet, but we can just have 1 of each for now.
The observatory module should generate the Universe at runtime, and should show a simulation of the universe with physics and stuff using a proper game engine (like #451)
There should also be a fully console-based version, incase someone doesn't want to use the proper one.
Telescope
Detect malicious cards and packs. It should block obvious stuff, and also add
suspicousnesswhen detecting suspicious code that isn't necessarily malicious. If the suspiciousness is too high (configurable), it will ask the user, or just block the target outright.It should block attempts to use networking without checking the config option. It should massively increase the suspicion when using stock
fs.The game should run it on startup, before importing the resources, and it should scan all the resources / packs contents. If this is too expensive, it could just scan the resources / packs that have changed since last run. Use hashes (checksum) for this?
It should also have functionality to run it on specific resources / packs. You can select a resource / pack to scan, or scan all. Where it will give a status.