play.wynncraft.com

Menu

Home

News

Store

Stats

Items

Classes

Map

Log in or Sign up

This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Wynncraft, the Minecraft MMORPG. Play it now on your Minecraft client at (IP): play.wynncraft.com. No mods required! Click here for more info...

Have some great ideas for Wynncraft? Join the official CT (content team) and help us make quests, builds, cinematics and much more!

World [70+ Supporters, 98.6%] The Actor System [ Includes Video & Gif Demonstrations ]

Discussion in 'General Suggestions' started by Novalescent, Oct 18, 2019.

Tags:

Thread Status:: Not open for further replies.

Page 2 of 3

Novalescent Retired Wynncraft Systematic Recreation Developer HERO

Messages:

569

Likes Received:

2,630

Trophy Points:

111

Minecraft:

Novalescent

It's that time of day again.

Bump

Novalescent, Oct 23, 2019

#21
__Excel i like cats VIP+

Messages:

596

Likes Received:

672

Trophy Points:

125

Minecraft:

Excel__
Novalescent said: ↑

Huzzah! Yet another suggestion with more videos!

So before I delve into this, I will say here and now that this suggestion is intended to have the Wynncraft Content Team as its primary audience. Of course, anyone else who is interested in what this is, feel free to read on!

This is also a pretty long read, so pull out your reading glasses.

A very important note: This is NOT meant to be a replacement for the current method of how Wynncraft creates their cutscenes. This is simply another alternative tool they can use to create it. (Brought up by Aarontti)

Now I don’t know how hard it is to make Wynncraft Cutscenes, but I’m assuming it takes a lot of effort, especially for things like the Secret Discoveries (The Wynn Monument discovery cutscene must’ve taken a long time!) I wanted to think of a way to not only improve the “liveliness” of the cutscenes, as it’s kind of obvious when something has a predefined path when they’re moving in a straight line, but to also make the effort of creating epic cutscenes easier.

I would also like to give a little something back to the Wynncraft Content Team (This is basically an “internal” suggestion) as I'm sure that there are a few things that could be changed to make their lives easier.

So, I present to you the fruits of my labor over the course of 4 weekends (I can't work on weekdays really), The Actor System.

Let’s start with a demonstration of what the Actor System can produce, as I know a good portion of people who actually open my threads only come for the demonstration(s) :)

Counting only the total time worked on it and not including a couple of bugs I had to fix along the way, this took ~30 hours to record & edit the scene.
Btw, there’s this super cool mod which will increase how many sounds can be playing at a time that I used in the video: https://www.curseforge.com/minecraft/mc-mods/extendpolyphonylimit

Ok, onto the actual info!

The Actor System was designed to make the job of creating cutscenes much easier. This idea was developed for cinematography in Minecraft and in fact doesn’t have to be just limited to the Wynncraft world.

So the basic goals and premises of this system are as followed:

Defining “actors” that are controlled by players and recording them walking around and performing actions. These actions include Arm Swings and Hand Item Switches.

These movements are “recorded” and transcribed into Player NPC movements, which will create near-perfect player recreated movements.

Using the Editor tool to add and change the looks of the scene. This includes adding Dialogue, Effects (Particles and Sounds), changing properties of Actors, and so on.

There’s so many features of this system that unfortunately I won’t be able to go over them all in this suggestion. So if you have any questions about how this works or what it can do, feel free to comment down below and I will answer them ASAP.

The Recorder

When making a Cutscene, the first part that most people should jump to is the recording.

To record, the editor of the scene needs to define “Actors.” These actors can then be used to record with by assigning players to them. For example, I can create an actor with an ID of “act_mage”, then assign someone like Corpe_ to it via a command.

After assigning players, you can then record the scene. This my friends is where the magic happens. When recording a scene, all movements and actions (Currently arm swings and hand item switches) are recorded into Actor Frames. Then, once you are finished recording and you test/play the scene, all movements done will be shown back to you via Player/Mob NPCs. This means if a player runs around in a circle flailing his arm, the scene will play back to you exactly what he was doing and exactly where he was in a smooth 20 TPS/FPS, the maximum Minecraft can provide. (Any higher via multithreading can cause data corruption to the Minecraft world unfortunately)

Click here to see an HD(er) version

Of course, you can assign multiple actors and recording simultaneously with multiple people performing actions of their own. I find it preferable however to record with just myself as it makes organization and scripting it a bit easier. Collaboration is hard sometimes!

You can also assign “Velocity Tools” to your hotbar keys. These tools allow you to change your velocity mid-recording so you can simulate knockback, launch forwards, and so on. For example, if I define a Velocity Tool to my 2nd Hotbar slot, when I scroll or switch to that hotbar slot, I will be launched based on the parameters I set.

Click here to see an HD(er) version

And finally, you can re-record portions of an actor in case you messed a pathing up. However, keep in mind that if you do this, all actor frames that are ahead of the frame you start at will be deleted, so be careful when re-recording to make sure you don’t mess up. For example: If an Actor has 500 frames, and I begin re-recording at frame 250, Actor Frames 250-500 will be deleted.
I should actually make it so re-recording just overwrites the frames as you record to prevent such things... Maybe another time.

The Editor

The second key feature and primary step in creating the cutscene is the Editor! There are a lot of cool tools for you to play with in order to get your scene looking flashy!

First of all, there’s Preview Mode, a powerful editing tool that allows you to preview the entire scene. How it works is you can play/pause the scene, move to the next scene frame, and move to the previous scene frame. This allows you to see the movements of all the NPCs and where they are, so you can make predictions when creating props and adding effects. You can even add effects and change properties while in editor mode, so you can see the results when you play them after the scene is finished!

Click here to see an HD(er) version

Next are the actual editors themselves. There are two primary editors: The Scene Editor and the Actor Editor, with the Actor Editor being the most powerful with the most tools.

Let’s cover the Scene Editor first. This editor is the easiest one to understand. When you’ve recorded a scene, scene frames are added, and you can open a UI to view all of these frames. When you open a Scene Frame, you can add Dialogue at that specific frame. This allows for easy dialogue creation, and all standard Wynncraft format is handled for you.

Another feature is that you can add is the ability for the scene to perform a command when that scene runs. This allows you to place a redstone block to trigger a door opening, or some sort of block explosion happening.

Click here to see an HD(er) version

Finally, is the Camera feature, which I think is the best part about this editor. How the camera works is you define points in the frame scenes, and set properties such as if the camera will instantly teleport to that location or not, and what direction the player will be looking when they teleport.

But what does the camera look like and how does it work? It’s actually an item drop that the player rides while they’re watching the scene. The “camera” item is moved at a constant velocity between points that is determined by the distance and the frame offset between the two points. This allows for extremely smooth camera movement while also allowing the player to have a full 360 view of the entire scene.

Click here to see an HD(er) version

Of course, a limitation is that the item can still collide with blocks, so it’s important that the camera path does not intersect with a block or it can lead to mishaps.

Oh yeah, and you can have Noteblock music play on certain frames. That’s cool I guess for people like @Corpe _ .

While implementing the Noteblock Music feature, there was a bug where due to internal server lag, the Noteblock Music can get off-beat the longer the scene goes on (ex. A scene that is 2+ minutes). This is because the Noteblock Music is running on a separate thread from the main server thread, and since server lag does not affect this separate thread, the music keeps going regardless of lag.

I spent a whole day trying to figure out how to fix this, but to no avail. I did manage to slightly fix it but not a whole bunch, so I had to develop a small BukkitRunnable workaround that allowed the music to be played on beat consistently. However, the tradeoff here is that the music can ominously pause on a beat due to how the tick calculation works.

I went ahead and used the BukkitRunnable workaround because I needed the consistency and was willing to deal with the tradeoff.

Now let’s move onto the best editor: The Actor Editor.

The Actor Editor allows you to add effects and change the properties of the actors themselves. These effects and properties are all contained to the actor that you are editing. I will show why this is the case in a moment.

I don’t want to go over the entire list of features available to the editor in-depth, so here is a rundown of it:

(Properties) EntityType: Can change the type of entity being shown. This entity must be a Creature-type Entity.

Name: Change the Actor’s displayed name. (This does not change their Name ID)

Skin: If the EntityType is a player, can change their skin to a specified one.

Armor: If the EntityType can wear armor, they will show the armor that you give them. Armor is static throughout the entire scene and cannot be changed frame-by-frame. (I may change this once I decide to not be lazy about it)

Visible-While-Inactive: A true/false flag that determines whether or not the actor is visible or not when they haven’t reached their starting frame.

(Frame-By-Frame Effects/Properties) Visibility: A true/neutral/false flag that toggles whether the actor is visible or not. This persists throughout the remainder of the frames until toggled otherwise.

Held Item(s): Can change the items held in the main and off hand. Items changed at a frame persist until changed again.

Particle Effects: Can add effects at chosen frames

Sound: Can add sound at certain frames

Frame Actions/Animations: Includes Particle Lines & Particle Circles. More stuff can be added via code with ease.

Animations/Effects: Plays/Removes certain mob/player animations at selected frames. These include:

Arm Swings

Hurt Animations

Death Animations (If this is toggled on, the Actor will not appear for the rest of the scene)

All of these properties and effects are limited to the Actor that you are editing. Why? Well this allows for the player editor to copy and paste the Actors at will! With a couple of commands, the editor can select/copy an actor, and paste them wherever the editor like, with all of their properties and effect still in tact.

You can also have the Actor’s path rotate according to the horizontal direction your looking at. This makes creating parts like clashing NPCs much easier!

Click here to see an HD(er) version

Whew! That’s the basics for the Actor System. Like I said, there’s a lot of things that I wanted to go into more detail about, but if I talked about everything and how everything works, this suggestion would be a 30 page essay.

That said, if you have any questions, feel free to comment and I will answer them ASAP! I will also put them in the “Q&A” post so that way people can check if their question has already been answered. There’s also a couple of technical questions to start off with so feel free to read those if you’re interested in the technical side of things.

Thanks for reading! And as always, feedback is appreciated!

Jesus Christ now I can finally sleep for more than an hour...
Btw did anyone else see the new logo? :monkaS:

________________________________

Q: How do the actors path work internally?

A: When recording an actor, the player’s location and direction is saved to a frame every tick (1 tick is 1/20 of a second, or 0.05s) with the according actions they performed on that tick (ex. Hand Swings). When playing the scene back, the Actors are actually being rapidly teleported to where the player originally was. This is accompanied with a small visual glitch in Minecraft where rapidly teleporting/moving an entity in a direction will cause their avatar to look like they are walking/running.
At first glance, this seems very unnecessary and inefficient. I actually thought the same too when I first made this system. So, I ran a test with the following parameters:

A running server with 1 GB allocated

100 Copied Actors performing the same action(s), which include particle effects and dialogue

This was the result:
https://media.giphy.com/media/fUefWXMUywEtwgZGGc/giphy.gif

Q: How do you save/load a scene?

A: All scenes can be saved by the Scene Editor with “/scene save.” In doing so, they are stored in their own .json file. They have been programmed to save only necessary information, such as non-default variables.
All scenes load automatically on server startup, but you can also manually reload the scene (/scene reload) in case you somehow messed up the scene catastrophically and need to restart from your previous save point.
The size of the .json file is proportionate to the duration and complexity of your scene; The more actors, effects, and the longer the scene is, the more information it saves and the larger the files becomes.
For example, the scene file for the GIF above this question takes up 6 MB, while the actual demonstration scene shown at the very beginning is about 18 MB. All in all, that isn’t a lot of disk space used.

Q: Are any command blocks involved in making a scene?

A: No, everything about the Actor System is handled purely by plugin magic. However, the Frame Editor allows you to run a command in case you need to perform some command block magic during the scene. This is to mainly allow CMDs to place a redstone block somewhere if they need to.

Q: Responding to a major technical concern from @Aarontti

A: I'll start with reliability first. I'm going to assume that this is the question of "How do I know this isn't going to bug out midway into playing a scene?" The answer to that, unfortunately, is I can never know perfectly. Things will break whether we expect them to or not. I've done my best to wring out most of the errors in the code, however the amount of logic that has to go behind everything, specifically the recording portion as I know there are about 10 different cases on how a user can record, may conflict in places where I may not expect it to. However, I've done my best to be sure that nothing breaks mid-scene or mid-creation and everything turns out smoothly. The main thing I worry about right now is the Camera. Since it is basically a moving item drop, it can be destroyed by things like Lava or collide into blocks, offsetting the path. I plan to add more checks to both the camera and more fragile places in the code to make sure errors like these don't happen again.

Performance impact I've addressed somewhat in the post. Yes, performance was something I kept in mind while creating this. The primary thing that could cause some lag is the actor movement.
I'll restate how actor movement works: When recording an actor, your location is saved every 1/20th of a second and when the scene plays back, the actor is teleported to those positions. So approximately every 0.05 seconds, all actors in the scene are teleported. I was and still am slightly concerned about this, but I've come to terms with it more and more that it isn't neccessarily a bad thing.
I even ran a test to make sure of this. In this gif link, there are exactly 104 Actors. The server that it's running on has a total of 1 GB allocated to it. The demo scene was also recorded on 1 GB, although if you wish to test it more I'd be happy to lower the allocation down to even 512MB or smaller.
https://media.giphy.com/media/fUefWXMUywEtwgZGGc/giphy.gif
If you have other performance tests in mind as well, let me know and I'll gladly test and fix stuff in the code if needed.

Next is multiplayer compatibility. Most of the code written does not touch the primary Bukkit API, and if it does, it does so very lightly. All of this code is ran on 1.12. Of course, things like Particle effects and Sound effects may not be saved correctly depending on what Wynncraft's version is running (I don't know for sure if Sound effect names in code change from 1.8 to 1.12 dramatically). Of course, methods to fix this such as reflection exists in case it needs to be compatible between versions.

So different types of lag... I'm going to assume you mean client lag and server lag. For server lag, the scene is still played and when the lag ends, it fasts forward like mobs do in Wynncraft where they're supposed to be when there is a lag spike. For client lag, the scene will still play. If they're is a camera in motion, they will still be riding it while the item camera moves.
Click to expand...

Woah........

This is amazing!!! I so wish wynncraft had a system like this. The music is also great, perfect for accompanying this scene, I love it how every transition in the scene had a transition in the music, and how the music and scene ended together. This is sooooooo much more effort than what most people put into the average suggestion, and it makes me super sad that they rarely every implement suggestions (the last one i think was the corkus suggestion, and that was like 2-3 years ago).
__Excel, Oct 23, 2019

#22

Novalescent likes this.
Novalescent Retired Wynncraft Systematic Recreation Developer HERO

Messages:

569

Likes Received:

2,630

Trophy Points:

111

Minecraft:

Novalescent

__Excel said: ↑

Woah........

This is amazing!!! I so wish wynncraft had a system like this. The music is also great, perfect for accompanying this scene, I love it how every transition in the scene had a transition in the music, and how the music and scene ended together. This is sooooooo much more effort than what most people put into the average suggestion, and it makes me super sad that they rarely every implement suggestions (the last one i think was the corkus suggestion, and that was like 2-3 years ago).
Click to expand...

Finally someone noticed the music...

And maybe it's a bit too much effort lol

Novalescent, Oct 23, 2019

#23

BqwaOLD likes this.
Novalescent Retired Wynncraft Systematic Recreation Developer HERO

Messages:

569

Likes Received:

2,630

Trophy Points:

111

Minecraft:

Novalescent

Bumpity bump bump bump

Novalescent, Oct 25, 2019

#24

BqwaOLD likes this.
Iboju absolute swag male CHAMPION

Messages:

650

Likes Received:

2,006

Trophy Points:

148

Guild:

Atlas Inc

Minecraft:

Iboju

ik this was just bumped yesterday but damn this needs a bump

Iboju, Oct 26, 2019

#25

Novalescent likes this.
Novalescent Retired Wynncraft Systematic Recreation Developer HERO

Messages:

569

Likes Received:

2,630

Trophy Points:

111

Minecraft:

Novalescent

Hi yes bump

Novalescent, Oct 28, 2019

#26
HalfCat_ Supporter of Catania HERO GM Builder

Messages:

252

Likes Received:

813

Trophy Points:

78

Creator Karma:

Minecraft:

HalfCat_

Can you download it somewhere?

HalfCat_, Oct 28, 2019

#27

Novalescent likes this.
Novalescent Retired Wynncraft Systematic Recreation Developer HERO

Messages:

569

Likes Received:

2,630

Trophy Points:

111

Minecraft:

Novalescent

HalfCat_ said: ↑

Can you download it somewhere?
Click to expand...

It's not available for download. I'm not sure whether I want to or not.

Novalescent, Oct 28, 2019

#28
HalfCat_ Supporter of Catania HERO GM Builder

Messages:

252

Likes Received:

813

Trophy Points:

78

Creator Karma:

Minecraft:

HalfCat_

Novalescent said: ↑

It's not available for download. I'm not sure whether I want to or not.
Click to expand...

Why wouldn't you? I would really love to make something with it, crediting you of course.

HalfCat_, Oct 28, 2019

#29

Novalescent likes this.
Novalescent Retired Wynncraft Systematic Recreation Developer HERO

Messages:

569

Likes Received:

2,630

Trophy Points:

111

Minecraft:

Novalescent

HalfCat_ said: ↑

Why wouldn't you? I would really love to make something with it, crediting you of course.
Click to expand...

There's actually a couple of reasons:
1. It's incomplete. True, it's about 85% complete but there are a couple of QoL bugs that I need to fix before it becomes actually convenient to use. Creating that demo scene was hard due to a couple of QoL commands not functioning the way they were supposed to about halfway into making it. I haven't gotten around to fixing them because I'm working on Recreation (You can find a video on that on the same channel where the demonstration video is).

2. Unfortunately I didn't make the plugin with the intention of releasing it to the public. At least not yet.

Novalescent, Oct 28, 2019

#30
Mmm Well-Known Adventurer VIP+

Messages:

155

Likes Received:

133

Trophy Points:

69

Minecraft:

StewieCman

Now this,

This is an extremely high quality suggestion.

Mmm, Oct 28, 2019

#31

Novalescent likes this.
SKZR Well-Known Adventurer

Messages:

240

Likes Received:

225

Trophy Points:

67

It's a good suggestion but not for Wynncraft and for a simple reason: LAGS
Wynncraft is already using a lot of command blocks and armorstands (for some mobs to create a different model or for other things like refineries for example) + the upcoming update with new armorstand-based monsters it will decrease servers performance.
Since the economy update the slots and the render distance already decreased and i think it isn't a good idea to make it decrease more. However, it still a good suggestion due to the fact that you out a lot of effort in it.

SKZR, Oct 28, 2019

#32
Novalescent Retired Wynncraft Systematic Recreation Developer HERO

Messages:

569

Likes Received:

2,630

Trophy Points:

111

Minecraft:

Novalescent

Diorlis said: ↑

It's a good suggestion but not for Wynncraft and for a simple reason: LAGS
Wynncraft is already using a lot of command blocks and armorstands (for some mobs to create a different model or for other things like refineries for example) + the upcoming update with new armorstand-based monsters it will decrease servers performance.
Since the economy update the slots and the render distance already decreased and i think it isn't a good idea to make it decrease more. However, it still a good suggestion due to the fact that you out a lot of effort in it.
Click to expand...

I've addressed this a few times already, so I'll do so again, quoting from the main thread

"Performance impact I've addressed somewhat in the post. Yes, performance was something I kept in mind while creating this. The primary thing that could cause some lag is the actor movement.
I'll restate how actor movement works: When recording an actor, your location is saved every 1/20th of a second and when the scene plays back, the actor is teleported to those positions. So approximately every 0.05 seconds, all actors in the scene are teleported. I was and still am slightly concerned about this, but I've come to terms with it more and more that it isn't neccessarily a bad thing.
I even ran a test to make sure of this. In this gif link, there are exactly 104 Actors. The server that it's running on has a total of 1 GB allocated to it. The demo scene was also recorded on 1 GB, although if you wish to test it more I'd be happy to lower the allocation down to even 512MB or smaller.
https://media.giphy.com/media/fUefWXMUywEtwgZGGc/giphy.gif
If you have other performance tests in mind as well, let me know and I'll gladly test and fix stuff in the code if needed."

Novalescent, Oct 28, 2019

#33
SKZR Well-Known Adventurer

Messages:

240

Likes Received:

225

Trophy Points:

67

Novalescent said: ↑

I've addressed this a few times already, so I'll do so again, quoting from the main thread

"Performance impact I've addressed somewhat in the post. Yes, performance was something I kept in mind while creating this. The primary thing that could cause some lag is the actor movement.
I'll restate how actor movement works: When recording an actor, your location is saved every 1/20th of a second and when the scene plays back, the actor is teleported to those positions. So approximately every 0.05 seconds, all actors in the scene are teleported. I was and still am slightly concerned about this, but I've come to terms with it more and more that it isn't neccessarily a bad thing.
I even ran a test to make sure of this. In this gif link, there are exactly 104 Actors. The server that it's running on has a total of 1 GB allocated to it. The demo scene was also recorded on 1 GB, although if you wish to test it more I'd be happy to lower the allocation down to even 512MB or smaller.
https://media.giphy.com/media/fUefWXMUywEtwgZGGc/giphy.gif
If you have other performance tests in mind as well, let me know and I'll gladly test and fix stuff in the code if needed."
Click to expand...

No matter how you tested it, iy wasn't in the same conditions that it would be on wynncraft servers.

SKZR, Oct 28, 2019

#34
Novalescent Retired Wynncraft Systematic Recreation Developer HERO

Messages:

569

Likes Received:

2,630

Trophy Points:

111

Minecraft:

Novalescent

Diorlis said: ↑

No matter how you tested it, iy wasn't in the same conditions that it would be on wynncraft servers.
Click to expand...

If you have other ideas for performance testing, I'm completely opened to them.

Either way, the small gif demonstration does show that the TPS is barely affected, so most likely server TPS will not be affected at all. While it can't fix lag, it can definitely not cause lag by itself.

Of course, it will all depend on how it's actually implemented.

Novalescent, Oct 28, 2019

#35
SKZR Well-Known Adventurer

Messages:

240

Likes Received:

225

Trophy Points:

67

Novalescent said: ↑

Of course, it will all depend on how it's actually implemented
Click to expand...

True

SKZR, Oct 28, 2019

#36
Novalescent Retired Wynncraft Systematic Recreation Developer HERO

Messages:

569

Likes Received:

2,630

Trophy Points:

111

Minecraft:

Novalescent

Righteous bump!

Novalescent, Oct 29, 2019

#37
Dexmio Ling Ling 40 hours a day. CHAMPION

Messages:

34

Likes Received:

35

Trophy Points:

51

Minecraft:

Dexmio

absolutely loving this, what an amazing and talented suggestion.

Dexmio, Oct 29, 2019

#38

Novalescent likes this.
Lotem Ex-Moral supporter in the official Wynncraft CT™ HERO

Messages:

805

Likes Received:

3,829

Trophy Points:

159

Guild:

lolFuckGuilds

Minecraft:

Lotem

I experimented with the Wynnscript system a long time ago (2-3 years), way before it was added to the game. It might have changed since, but probably not by much.

Your mod looks so much faster to use than the Wynnscripts system I used to know.
I remember when I tried to learn the system, and it took me about 2 hours to create a simple 30 second cutscene.

Wynnscript it written as a txt file with commands to be performed (such as controlling entities, moving the camera, playing sounds or particle effects...). It's much more powerful, but it takes so long to use.

Using Wynnscript is really tedious.
Whenever you want to make the smallest adjustment to the script, you have to copy-paste all of the coords manually, then push the script file to GitHub, log in to the GM server, wait for the script to be loaded, then watch it all the way through from the very start until the part you changed is showing up - only to find out you made a small mistake and must go through this whole process again.

(Btw I hope you all appreciate the huge amount of work the GMs put into every single cutscene. It's much harder than you think...)

Anyways, I think the perfect system would be the combination of both. Imagine you could record yourself acting and convert it into a script file :O
Then, any small tweaks, camera adjustments and complex effects can be added later to the file.

Great great job!
You should absolutely join dev team.

Lotem, Nov 13, 2019

#39

NITEHAWKX, Druser and Novalescent like this.
Novalescent Retired Wynncraft Systematic Recreation Developer HERO

Messages:

569

Likes Received:

2,630

Trophy Points:

111

Minecraft:

Novalescent

Lotem said: ↑

I experimented with the Wynnscript system a long time ago (2-3 years), way before it was added to the game. It might have changed since, but probably not by much.

Your mod looks so much faster to use than the Wynnscripts system I used to know.
I remember when I tried to learn the system, and it took me about 2 hours to create a simple 30 second cutscene.

Wynnscript it written as a txt file with commands to be performed (such as controlling entities, moving the camera, playing sounds or particle effects...). It's much more powerful, but it takes so long to use.

Using Wynnscript is really tedious.
Whenever you want to make the smallest adjustment to the script, you have to copy-paste all of the coords manually, then push the script file to GitHub, log in to the GM server, wait for the script to be loaded, then watch it all the way through from the very start until the part you changed is showing up - only to find out you made a small mistake and must go through this whole process again.

(Btw I hope you all appreciate the huge amount of work the GMs put into every single cutscene. It's much harder than you think...)

Anyways, I think the perfect system would be the combination of both. Imagine you could record yourself acting and convert it into a script file :O
Then, any small tweaks, camera adjustments and complex effects can be added later to the file.

Great great job!
You should absolutely join dev team.
Click to expand...

Ha ha thanks!
Of course, that's not to say that learning how the system works is an easy task. It does take a bit of knowledge to work with all of the tools available to you.

I remember when I first fleshed out the very basics of the system, I too decided to see how long it would take to make a simple cutscene.

It took roughly 2 hours, probably a bit more. Of course, this was before I added a few handy-dandy QoL tools that definitely help with synchronization.

Novalescent, Nov 13, 2019

#40

Lotem likes this.

(You must log in or sign up to reply here.)

Page 2 of 3

Thread Status:: Not open for further replies.