Nice work, I'll have to check it out. I hope there's some documentation, as I'm not great at figuring out python stuff without it.

Hi.
I haven't dug in to the docs yet, but it may be worth mentioning to people that want to create shareware/payed games that bass requires a license for each platform.

Hi @amerikranian
To answer your questions.
1: Can we use parts of Lucia in our own projects, meaning that if I only want to use, say, rotation, am I allowed to take it out of the engine as long as I say exactly what I've used?
- By default no, but you can do something like the below (with any util class)
from lucia.utils import rotation
# use rotation functions here.

2: What attribution do you all expect? A mention in the credits? Open sourcing the project with any part of Lucia in it?
- not necessarily. If you modify lucia, you are required to give those modifications back.
To quote choosealicense.com:
However, a larger work using the licensed work through interfaces provided by the licensed work may be distributed under different terms and without source code for the larger work.
Which essentially mean, that you are allowed to create closed source software / games / whatever with lucia but if you change / modify lucia itself, you are required to give those modifications back.
Hope that answered your questions.

hey @Liam
Yes, that could be a good idea hehe I'll put it in.

I see. Thank you. I will hopefully have more of a chance to sit down and mess with this some time soon.
A note: When running make.bat the generated documentation was pretty sparse. Is it because some things are missing and you guys are working on them?
An example with open al would be nice as well.

Could you all provide open al example? I got a traceback saying that a class was unable to be instantiated, but I think I'm just doing it wrong

I'm just curious, how are you supposed to pronounce Lucia? Eloquence says it like Loosha. Is it supposed to be Looseea? I know why there's confusion. If you play A Hero's Call, there's a character named Lucian, and different people in the game pronounce his name different ways. The guy at the mine entrance calls him Looseean, whereas at least one of the other guards calls him Looshan. Note: Eloquence pronounces the phonetic spellings in this post as intended.

I don't think the 3dpackfile example works correctly...
If I start out facing east, 0 degrees, the sound should be on my left. Yet, when I run the example, the sound is to my right.
My implementation of the sound pool was designed with north, east, south, and west equaling 0, 90, 180, and 270 degrees respectively, so maybe that's the issue here?

@Ethin and others
That's because OpenAL uses a left handed coordinate system while bass uses a right handed one (well, or the other way around).

So this means that bass and open al aren't compatible. How do we get around that issue?
Also if somebody could provide an open al example with lucia that'd be nice...

Yeh so, after messing with this some more, here are my thoughts.
I like the engine overall. You do have a rather interesting way of gathering input, I found something different online, but your way works, too.
I would perhaps add an option to the virtual input class to change the "hidden" message to the user's liking, though that is just me.
I would also expand the input class to support the ability to add typing sounds.
A minor convenience would be to alert the user of entering a capital char, either via a sound or by saying cap (I don't know if you can control the pitch of NVDA, though that can certainly be an option).
Add the ability to hold down keys in the input box, such as aaaaaaaaaaaa, right now it accepts only one letter at a time, which is also fine.
Add the ability to hit escape and close the input box (should be available at user discretion).
Overall, I am digging this. Except the open al/bass conflicts, I am all for using the engine in my future projects.
I do think that open al and bass issue needs to be resolved first, though. Right now I can't use lucia and my working sound pool as sound_lib throws errors about it being initialized already.

The rotation system being that way isn't the fault of any handed coordinates, it's because the trig functions work on that assumption of the unit circle. If I knew a reliable method to convert bearing to trig I would have used that, but one goes clockwise while the other doesn't, and they have different starting points. Either the sound pool or the backend's position function takes care of handed coordinate systems so you can use positive x is right, positive y is forward, positive z is up. Not sure what handed you'd call that. The cardinal directions are very set, but unfortunately sine and cosine don't operate on the cardinal directions, nor do they operate on degrees, and arc tangent is a mess either way. An update can be made if we have an implementation to convert at will between the two rotation systems to imply bearing and convert under the hood.

My current version of the sound pool, I do still need to update the official topic, has worked successfully with the BGT port of the rotation script.  That script has East equaling 90, so I don’t understand why if mine works, yours does not. That being said, my sound pool also requires you to calculate theta with degrees, convert them to radians.