rictic
Follow
Create your own GitHub profile
Sign up for your own profile on GitHub, the best place to host code, manage projects, and build software alongside 50 million developers.
Sign up
Popular repositories
-
-
A proof of concept tower defense game written in Processing.js
-
A competition about learning, or otherwise developing, the best controller (agent) for a version of Super Mario Bros.
-
My bash profile, full of the little aliases and shortcuts that make life worth living
-
Forked from mxtaweb-xx/reconciliation_ui
An html user interface for reconciling data against freebase using a new reconciliation service
-
672 contributions in the last year
Activity overview
Contribution activity
October 2020
Created a pull request in rictic/airlock.chat that received 4 comments
Improve incremental builds by 710% by dropping webpack
I spent this morning messing with drawing a voting screen, which for someone who isn't good at geometry involves a lot of trial and error, and the …
- Properly handle display messages in replays
- End the game with a clearer message
- Display player names in color.
- A bunch of little improvements
- Some small improvements for running on nicer machines (high frame rate, big monitor)
- Add a super basic vision system.
- The map is responsible for placing players.
- Smoother collisions
- The map is in charge of generating tasks.
- Implement edge-snapping for camera.
- Add static geometry into the Map, add collision detection to it
- Improve messages a bit
- Add a concept of a "map", the space in which a game takes place
- Use a camera-window system for tracking the player
- Avoid `use` statements that rust-analyzer dislikes
- Format using rustfmt, enforce that in CI.
- Add a voting UI, display of messages from the server
- Basic replay system
- A handful of incremental cleanup changes
- A couple minor improvements to scripts
- Compile in the current git SHA
- The server generates uuids, not the client.
- Implement the game simulation and protocol bits of voting
- Make airlock.chat a PWA
- Use cargo workspaces, to reduce duplicated compiles hopefully.
- Some pull requests not shown.
Created an issue in rust-analyzer/rust-analyzer that received 1 comment
"unresolved import" for std and core types like Duration and BTreeMap
I'm trying out matklad.rust-analyzer for the first time in vscode, having previously used rust-lang.rust. It appears to be working well, save that …