1 line
5.2 KiB
JavaScript
1 line
5.2 KiB
JavaScript
import{_ as e,c as t,o as a,N as o}from"./chunks/framework.0799945b.js";const m=JSON.parse('{"title":"Introduction","description":"","frontmatter":{"title":"Introduction"},"headers":[],"relativePath":"guide/index.md","lastUpdated":1681388423000}'),n={name:"guide/index.md"},r=o('<h1 id="introduction" tabindex="-1">Introduction <a class="header-anchor" href="#introduction" aria-label="Permalink to "Introduction""></a></h1><p>Profectus is a web-based game engine. You can write your content using many built in features, write your own features, and build up complex gameplay quickly and easily.</p><p>The purpose of creating profectus was to create an easy to use engine that does not create a ceiling for a programmer's personal growth. This engine will grow in complexity with you, empowering you to create increasingly complex designs and mechanics.</p><h2 id="should-you-use-profectus" tabindex="-1">Should you use Profectus? <a class="header-anchor" href="#should-you-use-profectus" aria-label="Permalink to "Should you use Profectus?""></a></h2><p>While this engine is intended to make game development (and web app development) easier, it still requires you to be comfortable with programming in general and javascript in particular. Fortunately, that is a solvable problem.</p><p>If you've never used Javascript before, <a href="https://www.learn-js.org/" target="_blank" rel="noreferrer">learn-js.org</a> is a good resource for learning the important concepts. If you'd like a more thorough lesson on all the ins and outs of web development, <a href="https://javascript.info" target="_blank" rel="noreferrer">javascript.info</a> and <a href="https://developer.mozilla.org/en-US/docs/Learn/JavaScript" target="_blank" rel="noreferrer">MDN's tutorials</a> should have you covered. MDN is also a great resource to use as a reference - for example, if you want to know more about something and you google it, there'll typically be a MDN link that'll explain it thoroughly.</p><p>Beyond the basics, Profectus uses a modern web development pipeline, using tools like node, typescript, and JSX. While most of it should be relatively easy to pick up through context, if this becomes too complicated you may be interested in <a href="https://github.com/Acamaeda/The-Modding-Tree/" target="_blank" rel="noreferrer">The Modding Tree</a>, a predecessor of Profectus that uses plain old javascript.</p><h3 id="alternative-engines" tabindex="-1">Alternative Engines <a class="header-anchor" href="#alternative-engines" aria-label="Permalink to "Alternative Engines""></a></h3><p>There are many popular game engines out there, such as <a href="https://www.yoyogames.com/" target="_blank" rel="noreferrer">GameMaker Studio 2</a>, <a href="https://unity.com" target="_blank" rel="noreferrer">Unity3D</a>, <a href="https://www.unrealengine.com/" target="_blank" rel="noreferrer">Unreal Engine 4</a>, and <a href="https://godotengine.org" target="_blank" rel="noreferrer">Godot</a>, that are all general purpose and also more useful if you're planning on going into a career in game development. These are all more mature and robust game engines compared to Profectus, and are used by actual game development studios.</p><p>Profectus, on the other hand, is a very opinionated engine that is better at specific types of projects. Where the above engines will require you to design and create your own interfaces, menus, save management systems, etc. Profectus will include those out of the box. Profectus will also output games that run natively in the browser, and will typically be easier for players to play than traditional engines.</p><p>If you are not interested in programming but still want to get into game development, the above engines also all support "visual programming", which may be more amenable to you. Each engine will have varying levels of support, and of course with varying complexities, but ultimately any of these will help you learn the concepts of programming and game development, and all of them also offer traditional programming for when you think you're ready.</p><h2 id="design-philosophies" tabindex="-1">Design Philosophies <a class="header-anchor" href="#design-philosophies" aria-label="Permalink to "Design Philosophies""></a></h2><p>While absolute purity is impossible, design decisions have been and will continue to be made using these principles in mind.</p><ul><li>An engine should be intuitive, and code readable without context</li><li>An engine should not constrain a creator</li><li>An engine should be consistent</li><li>An engine should be extensible, and those extensions sharable</li><li>An engine should be efficient</li><li>An engine should report issues early and thoroughly</li><li>Passing by reference is one honking great idea -- <a href="https://www.python.org/dev/peps/pep-0020/" target="_blank" rel="noreferrer">let's do more of that</a>! <ul><li>See <a href="https://dev.to/ycmjason/thought-on-vue-3-composition-api-reactive-considered-harmful-j8c" target="_blank" rel="noreferrer">Refs are better than reactive objects</a></li></ul></li></ul>',14),i=[r];function s(l,u,h,d,p,c){return a(),t("div",null,i)}const f=e(n,[["render",s]]);export{m as __pageData,f as default};
|