-
Notifications
You must be signed in to change notification settings - Fork 122
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
Tangent 0.1 #900
Merged
Merged
Tangent 0.1 #900
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The all-new and improved Tangent, brought to you by my weekend.
Features:
Oh, and almost all of these are implemented as mods, so you can change them out at runtime.
Also features the following Ambient changes:
assets
module at package level, not at scope levelfixed_rate_tick
method to make it easy to do an action every so often (used for input)Entity
a valid component value type; I tried going further, but WIT does not allow for recursive type definitions, so I had to give up. My plan was to use a serialized representation instead, but we have a lot of macro-driven code that makes special-casing things difficult, and fixing that would take too much time.remove_at_game_time
to the guestcamera::get_active
as a helper methodlerp
function--window-{x,y,width,height}
launch parameters to make it easy to launch two clients side-by-sideambient new
:--name
no longer appends to the path, making it usable as a configuration parameter--in-workspace
can be passed in to avoid generating unnecessary files if you're already in a workspace (no Cargo config, no VSCode settings, etc)--rust {none, empty, quad}
(defaults to quad) can now be used to choose the template used. None generates no Rust code (ideal for schemas), Empty generates empty main functions, while Quad generates the standard quad example we have so far. I foresee this being revamped in the short-to-mid-term future with different examples for different types of games.ambient new guest/rust/packages/games/tangent/mods/my_cool_mod --name "Tangent Mod: My Cool Mod!" --in-workspace --rust empty
and then replacing a few lines in the manifest to make it fully compatible. You don't have to delete files or lines of code any more.