QZPRODUCTIONS'S PROFILE

author=fifacv
last help i hope- I am at the top of the church tower. I know the sequence for the bell, but nothing happens at the gates

author=SilviuTM

author=QZProductions
Holy shit you were fast!!

That's what she said.

Anyway, considering what you said in that spoiler tag, I can't help but try it.
At least now I have a lot of information on the enemies and maps, so it shouldn't take as long as the first playthrough.

But first, I'll try deciphering the alphabet, then, in the meantime, maybe, just maybe, a "skip dialogue" button would be added...hopefully...if it wasn't already there.
It would be really cool to have that kind of button in case someone decides to do a speedrun.

Edit:

Show

Ka(1)(2)iscios
La(2)eronka(1)la
(2)ero(2)in
Liberigos

Lae(2)angeliolau
(1)ohano

(1) and (2) should be two of the following letters:
j,q,v,x,z

My bet would be on v and z tbh

Seeing as how I just can't find this alphabet anywhere, I am inclined to think you created it. Thing which, is fucking awesome.

Perhaps on the next playthrough, I'll pay attention and screenshot the other rune texts I can find.

author=Dyhalto
Congratulations, bro :D
Seeing one of these dumb things we make to Completion is no easy task.

author=SilviuTM
It seems like fate that I rarely visit this site, yet I checked it the same day this game's full version got released. Time to play it non-stop.
You're awesome, and congratulations.

author=Craze
:0 Awesome. Can't promise I'll get to it immediately with the pride month event but *downloads*

author=pianotm
I have discovered that for having the players triggering stationary events by walking into them, it's almost always better to not use actual event box collision triggers at all. Instead, create the effect in a common event and have the event wait for your player to enter a specified set of coordinates. The way this is done:

@>Control Variables: [0001: coordinate X] Player's Map X

@>Control Variables: [0002: coordinate Y] Player's Map Y

@>Conditional Branch: Variable [0001: coordinate X] == (number at X)

   @>Conditional Branch: Variable [0002: coordinate Y] == (number at Y)

   @>Trigger the effect you want triggered.

 : Branch End

: Branch End

I find when doing finicky work like what you're describing, this is significantly better than using the event box triggers. The system doesn't get nearly as confused about what it's supposed to do using coordinates as it does when using the built-in event triggers. I'm actually doing that now for a racing game I'm making. Since it's an obstacle course and since it's a runner, similar to snowboarding games, I don't want the character to just get stuck at an obstacle: I want the obstacle to interact (basically, penalize the player by backing up a space and forcing you to wait for a second.), and the basic event triggers won't react when you've got the game set to force him to run to the bottom of the screen. Using coordinates instead entirely solved every problem I was having and the game is reacting almost exactly the way I want it to.