But if you ask me, I would invest more in more in categorization and views.
For example,
- I would like to limit everything to 2D and group by section (Audio, Animation, Texture - these should be different sections, not just tags)
- Or just filter out assets, because I search for tools (currently you can add only one filter. I guess you can just duplicate this to my account, but then again... I'm not sure I would lose any updates then...)
Consider them helpful suggestions :-) Databases like that are very helpful, and there should be more of them!
You're right, adding more filters and separating some sections would be far useful. Those are great suggestions, I'll see what I can do. Will definitely add more functionality. Thank you for the feedback, much appreciated!
I have to admit, I'm tempted regularly on whether I should stick to Godot (an engine) or choose MonoGame (a framework) :D I'm sticking with Godot, because in MonoGame I'd have to code all the tools myself. Still the amount of stuff to learn in an engine makes me tempted to try MonoGame :D
The idea for Game Dev Resource Database is great!
But if you ask me, I would invest more in more in categorization and views.
For example,
- I would like to limit everything to 2D and group by section (Audio, Animation, Texture - these should be different sections, not just tags)
- Or just filter out assets, because I search for tools (currently you can add only one filter. I guess you can just duplicate this to my account, but then again... I'm not sure I would lose any updates then...)
Consider them helpful suggestions :-) Databases like that are very helpful, and there should be more of them!
You're right, adding more filters and separating some sections would be far useful. Those are great suggestions, I'll see what I can do. Will definitely add more functionality. Thank you for the feedback, much appreciated!
Thanks for mentioning Godot Weekly, too :-)
I have to admit, I'm tempted regularly on whether I should stick to Godot (an engine) or choose MonoGame (a framework) :D I'm sticking with Godot, because in MonoGame I'd have to code all the tools myself. Still the amount of stuff to learn in an engine makes me tempted to try MonoGame :D
Huh, never heard of MonoGame before, and it looks very charming... :) Another thing to consider when I'm done with Unity.