jadedctrl/ flora-search-aurora
1
0
Disbranĉigi 0
Fontkodo Issues Tirpetoj Eldonoj 1 Activity
flora-search-aurora/flora-search-aurora.lisp

84 lines
3.0 KiB
Common Lisp
Raw Normal View History

Split into packages; no functional change
2023-06-04 04:04:34 -05:00
;;;; Copyright © 2023, Jaidyn Ann <jadedctrl@posteo.at>
;;;;
;;;; This program is free software: you can redistribute it and/or
;;;; modify it under the terms of the GNU General Public License as
;;;; published by the Free Software Foundation, either version 3 of
;;;; the License, or (at your option) any later version.
;;;;
;;;; This program is distributed in the hope that it will be useful,
;;;; but WITHOUT ANY WARRANTY; without even the implied warranty of
;;;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
;;;; GNU General Public License for more details.
;;;;
;;;; You should have received a copy of the GNU General Public License
;;;; along with this program. If not, see <https://www.gnu.org/licenses/>.
Create general “state”-system … by which an individual state's loop can plug in another superceding loop function. Ex., a menu giving way to a sub-menu.
2023-06-08 21:57:51 -05:00
;;;; FLORA-SEARCH-AURORA
;;;; A simple TUI-game made for the text-flavoured LibreJam of 2023-06!
;;;; See: https://jamgaroo.xyz/jams/2
Init: Basic one-tile map-drawing
2023-05-31 23:04:36 -05:00
Translations of menu-items ^_^
2023-06-23 12:54:29 -05:00
(ql:quickload '(alexandria anaphora assoc-utils cl-charms cl-tiled str))
Implement menu input-loop; changing selection
2023-06-07 19:02:11 -05:00
Orienting dialogue to the left or right of entity
2023-06-20 20:04:13 -05:00
(load "util.lisp")
Split into packages; no functional change
2023-06-04 04:04:34 -05:00
(load "input.lisp")
(load "display.lisp")
Start UI: Line-wrapping string printing
2023-06-04 12:52:18 -05:00
(load "ui.lisp")
Reorder overworld.tiled functions; overworld.util No functional changes. Re-order functions in overworld.tiled so SBCL doesn't complain at me. Split some functions from overworld.tiled into a new overworld.util package. Also rename the files in a nice way!
2023-06-17 10:12:23 -05:00
(load "overworld.util.lisp")
(load "overworld.tiled.lisp")
Begin overworld-rendering loop It draws to the screen, now! Err, well, it has been able to do that, since my first day on this project. But until now, there wasn't a menu leading you there! c:<
2023-06-09 07:07:28 -05:00
(load "overworld.lisp")
Change entity faces while they’re talking What a cool effect ^w^ ^o^ ^w^
2023-06-19 08:47:45 -05:00
(load "dialogue.lisp")
Split off STATE-LOOP into an engine package (⚙) … while making generic state-function-creators for both dialogues and overworld maps. This should make game-specific code more pretty-like!
2023-06-23 13:29:09 -05:00
(load "engine.lisp")
Init: Basic one-tile map-drawing
2023-05-31 23:04:36 -05:00
Split into packages; no functional change
2023-06-04 04:04:34 -05:00
(defpackage :flora-search-aurora
When printing dialogue, show chars one-at-a-time Y’know, RPG-style! ‘Cause we’re cool kids! c:< … and this is a real RPG! This is legit! This is legit! … this is legit… =,w,= It _will_ be legit!
2023-06-19 14:43:46 -05:00
(:nicknames :fsa :✿)
Start UI: Line-wrapping string printing
2023-06-04 12:52:18 -05:00
(:export #:main)
(:use :cl
:flora-search-aurora.input :flora-search-aurora.display
Change entity faces while they’re talking What a cool effect ^w^ ^o^ ^w^
2023-06-19 08:47:45 -05:00
:flora-search-aurora.overworld :flora-search-aurora.dialogue
:flora-search-aurora.ui))
Init: Basic one-tile map-drawing
2023-05-31 23:04:36 -05:00
Split into packages; no functional change
2023-06-04 04:04:34 -05:00
(in-package :flora-search-aurora)
Semantic parsing of input; ncurses for raw input Yes, ncurses. Look, I caved, okay?! But in my defense, I couldn't find a simple way to get raw input in both a framebuffer and an xorg terminal, so… ncurses can handle the details. I'm just a dummy, you can't expect me to do everything! Well, input is parsed into a somewhat-semantic format, so at least I did *something* alright.
2023-06-04 02:33:53 -05:00
Baseline support for translations! :D It’s not using gettext or anything, just a simple system I cooked up for having the translations hard-coded in, side-by-side. … it’s easier for me this way when writing, and it’ll make things easier later on, during distribution :P
2023-06-23 11:28:34 -05:00
Split off STATE-LOOP into an engine package (⚙) … while making generic state-function-creators for both dialogues and overworld maps. This should make game-specific code more pretty-like!
2023-06-23 13:29:09 -05:00
(defparameter *literary-girl-dialogue*
(💬:start-dialogue
(💬:mumble "literary-girl" :en "...")
(💬:say "player" :eo "Kielas apud la mar'?"
:en "How's the view?")
(💬:face "player" "<.<")
(💬:say "literary-girl" :eo "Kielas apud la ruinoj de via viv'?"
:en "How's your trainwreck of a life?")
(💬:face "player" '💬:normal-face)))
Semantic parsing of input; ncurses for raw input Yes, ncurses. Look, I caved, okay?! But in my defense, I couldn't find a simple way to get raw input in both a framebuffer and an xorg terminal, so… ncurses can handle the details. I'm just a dummy, you can't expect me to do everything! Well, input is parsed into a somewhat-semantic format, so at least I did *something* alright.
2023-06-04 02:33:53 -05:00
Baseline support for translations! :D It’s not using gettext or anything, just a simple system I cooked up for having the translations hard-coded in, side-by-side. … it’s easier for me this way when writing, and it’ll make things easier later on, during distribution :P
2023-06-23 11:28:34 -05:00
Interact with nearby entities
2023-06-16 14:28:41 -05:00
(defun literary-girl-dialogue (map)
Split off STATE-LOOP into an engine package (⚙) … while making generic state-function-creators for both dialogues and overworld maps. This should make game-specific code more pretty-like!
2023-06-23 13:29:09 -05:00
(make-dialogue-state map *literary-girl-dialogue*))
Begin overworld-rendering loop It draws to the screen, now! Err, well, it has been able to do that, since my first day on this project. But until now, there wasn't a menu leading you there! c:<
2023-06-09 07:07:28 -05:00
Translations of menu-items ^_^
2023-06-23 12:54:29 -05:00
(defparameter *submenu* `(((LABEL :en "IDK") (selection . 100) (selected t))
((LABEL :en "GO BACK") (return . nil))))
Menu state-function creator: #'📋:make-menu-state
2023-06-22 11:31:49 -05:00
Translations of menu-items ^_^
2023-06-23 12:54:29 -05:00
(defparameter *main-menu* `(((LABEL :en "PLAY" :eo "EKLUDI")
(selection . 100) (selected . t)
Split off STATE-LOOP into an engine package (⚙) … while making generic state-function-creators for both dialogues and overworld maps. This should make game-specific code more pretty-like!
2023-06-23 13:29:09 -05:00
(return . ,(🌍:make-overworld-state
(format nil "~Ares/map.tmx" (uiop:getcwd)))))
Translations of menu-items ^_^
2023-06-23 12:54:29 -05:00
((LABEL :en "SUBMENU" :eo "SUBMENUO")
(return . ,(📋:make-menu-state *submenu*)))
((LABEL :en "QUIT" :eo "REZIGNI")
(return . nil))))
Baseline support for translations! :D It’s not using gettext or anything, just a simple system I cooked up for having the translations hard-coded in, side-by-side. … it’s easier for me this way when writing, and it’ll make things easier later on, during distribution :P
2023-06-23 11:28:34 -05:00
Semantic parsing of input; ncurses for raw input Yes, ncurses. Look, I caved, okay?! But in my defense, I couldn't find a simple way to get raw input in both a framebuffer and an xorg terminal, so… ncurses can handle the details. I'm just a dummy, you can't expect me to do everything! Well, input is parsed into a somewhat-semantic format, so at least I did *something* alright.
2023-06-04 02:33:53 -05:00
(defun main ()
Split off STATE-LOOP into an engine package (⚙) … while making generic state-function-creators for both dialogues and overworld maps. This should make game-specific code more pretty-like!
2023-06-23 13:29:09 -05:00
"A pathetic fascimile of a main loop. What does it do? WHAST DOES TI DODOO?
What a mysteryyy! You’ll have to check out the engine to uncover it.
engine.lisp, that is. Cheers! :D"
(⚙:main (list (📋:make-menu-state *main-menu*))))
Create general “state”-system … by which an individual state's loop can plug in another superceding loop function. Ex., a menu giving way to a sub-menu.
2023-06-08 21:57:51 -05:00
Semantic parsing of input; ncurses for raw input Yes, ncurses. Look, I caved, okay?! But in my defense, I couldn't find a simple way to get raw input in both a framebuffer and an xorg terminal, so… ncurses can handle the details. I'm just a dummy, you can't expect me to do everything! Well, input is parsed into a somewhat-semantic format, so at least I did *something* alright.
2023-06-04 02:33:53 -05:00
Rename state-loop’s loop functions to “state-functions” Also document all current state-functions.
2023-06-09 16:14:46 -05:00
(main) ;; — Knock-knock
;; — Who’s there?
;; — Yo momma!
;; — “Yo momma” who?
Start basic dialogue state, etc? This is so bad, I wanna dieee :w:
2023-06-17 22:47:30 -05:00
;; — Yo momma’s a sweet lady, and I’d like to take her out for some tea!