Mirrors/godot-platformer-2d
1
0
Fork 0
mirror of https://github.com/GDQuest/godot-platformer-2d.git synced 2026-01-23 02:14:19 +00:00
Code Issues Projects Releases Wiki Activity

Remove to-do.md

Browse source
This commit is contained in:
Nathan Lovato 2020-03-29 19:14:05 -06:00
parent 7066394376
commit aa6ec08750
1 changed files with 0 additions and 43 deletions
Download patch file Download diff file Expand all files Collapse all files

43
to-do.md
View file

@ -1,43 +0,0 @@
#29 META task: Missing base systems, components, or mechanics to complete the demos
#24 Level design: design connected frames to teach basic movement
#20 Camera: soft snapping to anchors
#4 Write a contribution guide discussion
# META task: Missing base systems, components, or mechanics to complete the demos
* created by @NathanLovato on 2019-06-09 03:50:17 +0000 UTC * assignees: NathanLovato This issue is to help me keep track of what main parts of the project are still missing
- [x] Health component
- [ ] Combat: taking damage, damaging enemies, death
- [ ] Respawn and checkpoints
- [ ] AI system and Enemies
- [ ] Level design
- [ ] Visuals
- [ ] Sound
- [ ] Transition between frames
# Level design: design connected frames to teach basic movement
* created by @NathanLovato on 2019-05-31 02:51:40 +0000 UTC * assignees: NathanLovato Notes:
- Need to set up a tilemap to quickly draw the layout of levels and get collision shapes
- There's currently no code to move between frames or scenes
# Camera: soft snapping to anchors
* created by @NathanLovato on 2019-05-31 02:43:44 +0000 UTC * assignees: NathanLovato Add support for anchors towards which the camera can softly lerp, to help guide the player to points of interest. E.g. a new ability to unlock.
# Write a contribution guide
* created by @NathanLovato on 2019-05-02 01:45:52 +0000 UTC * assignees: NathanLovato We need a guide so people know when and what they can contribute. During the prototyping phase, feedback and testing would be useful and welcome. Any serious work would be welcome at any stage, anything that helps the project move forward: implementing different mechanics, level design, etc.
I'd just like all the work to be ticketed and the scope to be well-defined so we don't go overboard with features. Right now it's just a little too early. We need to have a clearer direction and target for the demo.
From @henriiquecampos:
> I think a brief explanation on this take to clarify when this will happen would be nice. The major questions I have in mind are:
>
> Will the course and the demo be done in parallel or the demo first and then the course?
> In which case, when/where will contributors/learners take place?
> What kind of assignment/content can they expect to be accepted?