Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

1

Technical forum / Re: Show inventory by pressing a keyboard button

« on: March 06, 2025, 02:07:17 AM »

As an example, I implemented your idea in (a copy of) the wme demo project (also known as wme_demo.wpr).

I'm not sure if you want to add the functionality of displaying the inventory when pressing SPACE (while keeping the former method of navigating to the top of the screen) or you want to replace one by the other. If you want to keep both, follow Walkthrough #1. If you want to replace one by the other, Walkthrough #2 (down below this post).

Walkthrough 1

1. I open wme_demo.wpr
2. In the project tree pannel, I locate the folder named scripts, and open the file base.inc
3. This file is loaded on SciTE Script Editor.
4. I add a global variable to keep track of whether the SPACE key has been pressed to show/hide the inventory. I'll name it spaceSwitch.

Code: WME Script

1. #include "scripts\const.inc"
2.  
3. global Scene;
4. global Keyboard;
5. global actor;
6.  
7. // this var keeps track whether the user has pressed space to show or hide the inventory
8.  global spaceSwitch;

5. In the project tree pannel, I locate the folder named scripts, and open the file game.script
6. I give an initial value to the var spaceSwitch at the start of the code - false since the space key has not been pressed yet.

Code: WME Script

1. #include "scripts\base.inc"
2. #include "scripts\keys.inc"
3.  
4. // store some of the game's attributes in global variables for convenience
5. Keyboard = Game.Keyboard;
6. Scene = Game.Scene;
7.  
8. // this var keeps track whether the user has pressed space to show or hide the inventory
9.  spaceSwitch = false;

7. I go to the bottom of the code and locate the portion that tells the engine what to do when the player presses a key on the keyboard. I add a new portion of code that is triggered when the user presses the SPACE key.

This portion makes sure that the main character is not currently having a dialogue with other characters, and that the Win menu is not visible, before showing the inventory, as there's no use for the inventory to show up when those are visible. In the same way, we tell the engine to hide the inventory if the main character starts a dialogue or when the game stops being interactive.

At the end, I add a "switch" that is changed from false to true, and from true to false, each time the user presses the SPACE key.

Code: WME Script

1. ////////////////////////////////////////////////////////////////////////////////
2. on "Keypress"
3. {
4.   // on Esc or F1 key
5.   if(Keyboard.KeyCode==VK_ESCAPE || Keyboard.KeyCode==VK_F1)
6.   {
7.     // load and display the main menu window
8.     WinCaption.Visible = false;
9.     var WinMainMenu = Game.LoadWindow("interface\system\mainmenu.window");
10.     WinMainMenu.Center();
11.     WinMainMenu.GoSystemExclusive();
12.     Game.UnloadObject(WinMainMenu);
13.   // on SPACE key
14.   } else if (Keyboard.KeyCode==VK_SPACE)
15.   {    
16.     if (!Game.ResponsesVisible && !WinMenu.Visible) {
17.       Game.InventoryVisible = true;
18.     } else if (Game.ResponsesVisible || !Game.Interactive) {
19.       Game.InventoryVisible = false;
20.     }
21.     // turn on and off the space switch when pressing space
22.     spaceSwitch = !spaceSwitch;
23.     }
24. }
25.  
26. ////////////////////////////////////////////////////////////////////////////////

8. In the project tree pannel, I locate the folder named scripts, and open the file game_loop.script

9. I go to the bottom of the code and locate the portion that tells the engine to show the inventory when the user navigates to the top of the screen.

I modify the code, so the inventory only dissapears from the screen if the user has not previously triggered it by means of the SPACE key. If I didn't make this modification, considering that the mouse cursor can be in positions outside the top, the inventory would never stick around when the user pressed SPACE: the engine would display it just for an instant before making it dissapear right away.

Finally I set spaceSwitch to false to avoid a conflict between the different methods of toggling on and off the inventory. If you're curious, you can delete spaceSwitch = false; and see what happens.

Code: WME Script

1. // display the inventory window
2. if(Game.Interactive && Game.MouseY < 45 && !Game.ResponsesVisible && !WinMenu.Visible)
3. {
4.   Game.InventoryVisible = true;
5. } else if((Game.MouseY > 100 && spaceSwitch == false)|| Game.ResponsesVisible|| !Game.Interactive)
6. {
7.   Game.InventoryVisible = false;
8.   spaceSwitch = false;
9. }

Walkthrough 2

If your intention is to replace the former method of displaying the inventory (ie. navigating to the top of the screen) by a new method that shows/hides the inventory when pressing the SPACE key.

1. In the file game_loop.script, I modify the portion of code that tells the engine to show the inventory when the user navigates to the top of the screen like this:

Code: WME Script

1. // display the inventory window
2. if(Game.ResponsesVisible|| !Game.Interactive)
3. {
4.   Game.InventoryVisible = false;
5. }

2. I modify the file game.script like this:

Code: WME Script

1. ////////////////////////////////////////////////////////////////////////////////
2. on "Keypress"
3. {
4.   // on Esc or F1 key
5.   if(Keyboard.KeyCode==VK_ESCAPE || Keyboard.KeyCode==VK_F1)
6.   {
7.     // load and display the main menu window
8.     WinCaption.Visible = false;
9.     var WinMainMenu = Game.LoadWindow("interface\system\mainmenu.window");
10.     WinMainMenu.Center();
11.     WinMainMenu.GoSystemExclusive();
12.     Game.UnloadObject(WinMainMenu);
13.   // on SPACE key
14.   } else if (Keyboard.KeyCode==VK_SPACE)
15.   {    
16.     if (!Game.ResponsesVisible && !WinMenu.Visible) {
17.       Game.InventoryVisible = true;
18.     } else if (Game.ResponsesVisible || !Game.Interactive) {
19.       Game.InventoryVisible = false;
20.     }
21.   }
22. }
23.  
24. ////////////////////////////////////////////////////////////////////////////////

2

Technical forum / Re: 3D Actor Blender export

« on: September 11, 2024, 12:03:24 PM »

Hi Martin 

A few months ago, I tried to accomplish what you're trying at this moment (on Blender 4.2.1). I didn't manage to get it to work. I met a few people in the Blender community who are trying to do just the same for their game projects. Hopefully, someone will figure this out.

In any case, if this would interest you, you can use the animations of your Blender character in a 2D project by exporting frames as .bmp, and then using those to create sprites in wme's SpriteEdit.

3

General Discussion / Re: Preservation of games

« on: February 23, 2024, 12:55:24 AM »

Hello retro_exo 

Is there a particular reason the game was delisted?

I don't have all the information ... one possibility could be that Shadow of Nebula may have not been added to the Game page. I know of several games developed with wme that are not in there. In occasion, I wondered whether I should add them myself or not, but it seems to me that ultimately is a decision of the game authors.

I figured I would reach out to the community and see if anyone is aware of any repositories of the free games that have been announced\released over the years? Or do any members here happen to have archives of the games that have been released?

Now and then, I check out the game page and update it with new links to the games on the internet. I haven't done so in a while ... Which game/s were you looking for? I may be able to point you to a download link if it's available. Some I haven't found myself though.

4

Game announcements / Re: James Peris 2: The fountain of Eternal Drunkenness

« on: December 04, 2022, 09:09:58 PM »

WOW These are awesome news !!!

Congratulations and thank you guys for creating another amusing adventure game

I'm looking forward to playing it 

5

General Discussion / Re: Actor position

« on: December 04, 2022, 08:35:12 PM »

Hello Kusurović 

For example:

Code: WME Script

1. // Molly will be placed at the coordinates 139, 428
2. actor.SkipTo(139, 428);
3.  
4. // And she will be facing downwards and to the right
5. actor.Direction = DI_DOWNRIGHT;
6.  

In case you want to see a working example, you will find a demo project within the folder where you installed WME Development Kit. Possibly C:\Program Files (x86)\WME DevKit\projects\wme_demo\wme_demo.wpr

The snippet of code you see above, I got it from said demo - more precisely, from the file scene_init.script, located in the project tree pane under scenes > room > scr.

6

Community bulletin board / Re: Finished competition games!

« on: April 27, 2022, 05:48:31 PM »

Hi wintermuties

By any chance, any of you has the source code of leucome's game The Closet (winner of the second round of the WME Competition)? The download link is no longer active.

7

Software and games / Re: Wintermute in other Operating Systems: Wine Edition

« on: April 19, 2022, 07:54:44 PM »

I run into an issue while using SpriteEdit under Wine 7.0 (Stable). When I try to add a frame, a message pops up explaining that it needs to close the program, and subsequently it closes it down. On the other hand, the rest seems to be working fine.

So if you're set in using Wine 7.0, you can still add frames to your sprite (eg. MyFile.sprite) via a text editor, and then open the hand-edited file in SpriteEdit to set (visually) variables, such as the hotspot coordinates, etc.

To give you an idea of what you would need to do, here's a a sprite without frames (named chair.sprite) that I created by clicking the option 'Add sprite'. Then I opened it in a text editor.

Code: [Select]

; $EDITOR_PROJECT_ROOT_DIR$ ..\..\..\
; generated by SpriteEdit

SPRITE {
  NAME="chair"
  LOOPING=TRUE
  CONTINUOUS=FALSE
  PRECISE=TRUE
}

And now I will add a frame by copy-pasting the text part corresponding to the frame, like in the example below. Important: I fill the IMAGE variable with the location (within the project) where the wouldbe frame image is located; in this case: IMAGE = "tutorial\gfx\chair.bmp"

Code: [Select]

; $EDITOR_PROJECT_ROOT_DIR$ ..\..\..\
; generated by SpriteEdit

SPRITE {
  NAME="chair"
  LOOPING=FALSE
  CONTINUOUS=FALSE
  PRECISE=TRUE
  FRAME {
    DELAY = 0
    KEYFRAME=FALSE
    IMAGE = "tutorial\gfx\chair.bmp"
    HOTSPOT {0, 0}
    EDITOR_SELECTED=TRUE
  }

}

That's it. chair.sprite is ready to be opened in SpriteEdit, where I can set the hotspot coordinates of such frame, and other settings.

The same method can be applied to multiple frame sprites. Here you can see the finished version of walk.sprite portraying the character Molly walking in the dd direction:

Code: [Select]

; generated by SpriteEdit

; $EDITOR_PROJECT_ROOT_DIR$ ..\..\..\..\

SPRITE {
  NAME=""
  LOOPING=TRUE
  CONTINUOUS=FALSE
  PRECISE=TRUE
  FRAME {
    DELAY = 90
    MOVE {0, 8}
    KEYFRAME=FALSE
    IMAGE = "actors\molly\dd\walk\00.bmp"
    HOTSPOT {50, 250}
  }

  FRAME {
    DELAY = 90
    MOVE {0, 8}
    KEYFRAME=FALSE
    IMAGE = "actors\molly\dd\walk\01.bmp"
    HOTSPOT {50, 250}
  }

  FRAME {
    DELAY = 90
    MOVE {0, 8}
    KEYFRAME=FALSE
    IMAGE = "actors\molly\dd\walk\02.bmp"
    HOTSPOT {50, 250}
  }

  FRAME {
    DELAY = 90
    MOVE {0, 8}
    KEYFRAME=FALSE
    IMAGE = "actors\molly\dd\walk\03.bmp"
    HOTSPOT {50, 250}
  }

  FRAME {
    DELAY = 90
    MOVE {0, 8}
    KEYFRAME=FALSE
    IMAGE = "actors\molly\dd\walk\04.bmp"
    HOTSPOT {50, 250}
  }

  FRAME {
    DELAY = 90
    MOVE {0, 8}
    KEYFRAME=FALSE
    IMAGE = "actors\molly\dd\walk\05.bmp"
    HOTSPOT {50, 250}
    EDITOR_SELECTED=TRUE
  }

  FRAME {
    DELAY = 90
    MOVE {0, 8}
    KEYFRAME=FALSE
    IMAGE = "actors\molly\dd\walk\06.bmp"
    HOTSPOT {50, 250}
  }

  FRAME {
    DELAY = 90
    MOVE {0, 8}
    KEYFRAME=FALSE
    IMAGE = "actors\molly\dd\walk\07.bmp"
    HOTSPOT {50, 250}
  }

  FRAME {
    DELAY = 90
    MOVE {0, 8}
    KEYFRAME=FALSE
    IMAGE = "actors\molly\dd\walk\08.bmp"
    HOTSPOT {50, 250}
  }

  FRAME {
    DELAY = 90
    MOVE {0, 8}
    KEYFRAME=FALSE
    IMAGE = "actors\molly\dd\walk\09.bmp"
    HOTSPOT {50, 250}
  }

}


8

General Discussion / Ron Gilbert announces Return to Monkey Island | Coming 2022

« on: April 18, 2022, 03:14:33 PM »

So to mix things up a little I'm taking this opportunity to announce I've decided to make another Monkey Island.

Announcing Return to Monkey Island, the long-awaited follow-up to the legendary Secret of Monkey Island and Monkey Island 2: LeChuck's Revenge by Ron Gilbert's Terrible Toybox in collaboration with Devolver Digital and Lucasfilm Games, coming 2022.

Official website
Trailer

9

Game design / Re: Basics

« on: April 10, 2022, 09:11:17 PM »

Hi gintonik 

1.: I need an Actor. Is there a good (easy)tool aviable, where i can build an Actor (it have to been compatible with WME) really quickly? I tried to use Poser8 but this is a science of himself.

It seems you're talking about a 3D animated character, if so, you need a program able to export such character in the Microsoft X file format. In addition, WME would require "hidden geometry" files (in which walkable areas of scenes, 3D light positions and cameras are defined) in 3DS format.

As for easy and quick ... I guess that's relative. You may have to spend some time learning how to design in 3D. In any case, WME Development Kit provides a 3D demo project (including a 3D character) to ease the process. If you used the default settings when you installed Wintermute, you will find it here:

C:/Program Files (x86)/WME DevKit/projects/wme_demo_3d/wme_demo_3d.wpr

You can find further information in:

1. This video tutorial series created by Jyujinkai with WME in mind:

How to Create a 3D Real-Time Character

Tutorial 01 - Creating Symmetrical Design Plates
Tutorial 02 - Modelling your Character off Design Plates
Tutorial 03 - Building Symmetrical UV Layouts
Tutorial 04 - Texturing
Tutorial 05 - Rigging: (A) Introduction, (B) Biped, (C) Skinning: Part 1 - Part 2 - Part 3

2. The Resource Center

3. The documentation:

3D characters support in WME
Principles and requirements
Actor definition file, X format
Scripting support
Additional 3D options in SceneEdit
Shadows

2.: I need Rooms. Is there a really easy tool aviable to build Rooms. Or have i use ex. Photoshop and paint a complete Room (room1.jpg)?

If you're referring to drawing the background of a scene (room), sure, a graphic design program. If you're referring to designing a scene (the background is just a part of it), I would direct you to the scene creation tutorial in the documentation.

3.: Have somebody a really easy tutorial(german) how i have use the WME?

I would start here.

10

Game design / The Secret of Creating Monkey Island

« on: April 07, 2022, 04:40:32 PM »

Interview with Ron Gilbert, published in The Adventurer, Issue No. 01, Fall 1990

Whatever possessed you to create a game about pirates, anyway?

I'd wanted to do a pirate game for a long time.

You see, one of my favorite rides in Disneyland is Pirates of the Caribbean. You get on a little boat and it takes you through a pirate adventure, climaxing in a cannon fight between two pirate ships. Your boat keeps you moving through the adventure, but I've always wished I could get off and wander around, learn more about the characters, and find a way onto those pirate ships.

So with The Secret of Monkey Island I wanted to create a game that had the same flavor, but where you could step off the boat and enter that whole storybook world. The pirates of Monkey Island aren't like real pirates, who were slimy and vicious. These are swashbuckling, fun-loving pirates, like the ones in the adventure stories everyone grows up with.

Once you had the idea, where did you go from there?

I started designing Monkey Island about two and a half years ago. But I was only about a fourth of the way through the design when Indiana Jones and the Last Crusade came up. That had to be done quickly, so we had to put Monkey Island on hold for a while. That's why it took so long to complete.

The first thing I do when I'm designing a game is sit down and write a short story. I wrote a lot of four- or five-page stories, lots of different plots.

Then I'd read each story and ask myself, is that interesting? Does that make sense? And I'd say, "well, no." So I'd throw it out and write another.

I kept writing these stories and showing them to people around the office, until I hit upon something that was really intriguing. I had put some ghosts into one of the stories, and that seemed to catch everyone's interest.

I'm not sure why there's such a close connection between pirates and ghosts, and so many stories about ghost ships and ghost pirates. In all the reading I did, I never found out where all that began. Still when I put in the ghost pirate LeChuck, that's when everything started to come together for me. Because now I had a good, strong antagonist.

You mention doing some reading. Why?

I read a lot of novels and reference books, more for the flavor of the period than for accuracy. This isn't a historically accurate game. In fact, you'll see when you play that there are a lot of anachronisms, like the vending machine at Stan's used ship yard. They're there to add humor to the game, of course, but they also have a secret, deeper relevance to the story - but I'm keeping that secret for the sequel.

A sequel? Really?

Yeah, but don't tell anyone yet.

Okay, I'll just edit that line out of the interview before it's printed. So you've got your story, and your ghost pirate. Then what?

The next step was to take the story and break it up into a step-by-step outline of what the player has to do.

You have to pick up some things, you have to get a ship, you have to find Monkey Island, and so on. I ended up with a four-page list of forty or fifty key points.

Then I started writing puzzles around each of those points. Each point might have as many as three or four puzzles that needed to be solved.

At the same time, I looked for ways to make the story nonlinear, to give players a choice of which puzzle to solve next. If you have a lot of bottlenecks, you're going to increase the chance that players will become frustrated with your game. Because they're sitting in one room trying to get through one door, and there's nothing else to do in the game until they get through that door. If you can give them other things they can do while they're trying to get through the door, they can put that puzzle aside for a while and do other stuff. Maybe they'll even see something along the way that'll help them figure out the puzzle.

Can you give us an example of this from the game?

One of the things I did to make the story less linear was to add the three trials at the start of the game. You have to prove yourself as a pirate by completing these three tests, and you can do them in any order that you want. That was done on purpose, so that you don't have to finish trial one before you can try trial two. I think it's a good design technique to, have things as nolinear as possible, but it does make the storytelling ten times as hard.

The game went through a lot of changes in the design process. The three trials are one example; I added them late in the design stage. Another change was that I decided to introduce a lot of characters in a way that wasn't directly related to the main plot. These are the people you'll eventually need for your ship's crew. But I wanted you to meet them as incidental characters while you're completing the trials. They aren't important at that point. Then when you're presented with the problem of finding a crew, you think, wow, I've already met these people, and now you can go back and really interact with them.

When you've finished the design, you're ready to start programming, right?

Wrong. After the design is finished, then comes the horrible task of budgeting and scheduling, which is no fun whatsoever. You plan out when each room is going to get drawn, when each character is going to get programmed, how much is it going to cost. This can last a couple of weeks.

A computer game used to be done by one person working for maybe a year, and it would cost thirty or forty thousand dollars. Now we're doing these huge games that teams of specialists work on together, and they're starting to cost huge amounts of money. Within a few years it'll cost a million dollars to put together a game. When you're dealing with that much money you have to plan out every detail.

Our team for Monkey Island included programmers Tim Schafer and Dave Grossman. They not only did the programming but they wrote about two-thirds of the dialog in the game, too. And Steve Purcell and Mark Ferrari did the great artwork.

Once the budgets and schedules are done, you can begin programming at last. But Monkey Island is an enourmous complex game. Where do you start?

Our first goal was to get a crude version of the game together as fast as we could. That means a lot of the animation was missing, the rooms were just sketched in, the puzzles were wired in as quickly as possible.

It took about three months to get a primitive version of Monkey Island that was playable from beginning to end. It was like having a rough cut of a movie. We could identify a lot of weak spots - we cut out a whole bunch of the game at that point because it just didn't flow well, and we added stuff where the game wasn't interesting enough.

For example?

Before you can recruit one character named Meathook, he demands you prove your bravery. You had to accomplish three things. But it slowed down the flow of the game too much, so we cut out two of them. For our story, one was enough.

We added some things, too. We realized that once you got to Monkey Island, the game became kind of slow. The reason was simply that there weren't a lot of people ... to be a deserted island. So we added a shipwrecked character on the island, and that gives you somebody to talk with. And as you piece together the story of what's been happening on Monkey Island, you discover that's he's a very important part of that story.

So that crude first version of the game actually saved us time. If instead we'd worked each part up to perfection as we went along, we'd have wasted a lot of time on things like that that would eventually be thrown out, and it would have taken twice as long to produce the game.

But Monkey Island is on the shelves at last.

I'm glad it's done. It's been two and a half years and a lot of hard work, but a lot of fun, too. We hope everyone has a great time playing it.

11

Technical forum / Re: What are packages or package, how do I download or create one?.

« on: December 14, 2021, 04:43:30 PM »

Packages are special files containing game resources in a compressed form (similar to zip archives). Once you compile your game, you can choose to store all the resources in one or more packages. Why to have multiple packages? There are many reasons ...

Click here to learn more about it
Click here to learn about everything Wintermute

12

Foro técnico / Re: Que son los packages o pack, como descargo o creo uno?.

« on: December 09, 2021, 06:05:47 PM »

Hola niccx

Un package (o paquete) es un archivo comprimido que contiene varios o todos los recursos del juego (imágenes, sonido, etc.). Cuando hayas terminado de crear tu juego y te propongas distribuirlo, al compilarlo, se crearán tantos archivos paquete como hayas elegido en un inicio.

Podría ser útil crear más de un paquete, por ejemplo, si creas un juego en varios idiomas y das la opción a los jugadores de descargarse específicamente el audio del idioma en el que estén interesados (y no todos). Al crear un paquete para cada idioma, puedes reducir el tamaño de lo que se vayan a descargar.

Al inicio de esta historia ...

Tras crear un nuevo proyecto en ProjectMan, hay un solo paquete llamado "data". Para crear un nuevo paquete (además de data), click derecho en algún espacio en blanco dentro del panel árbol del proyecto. Del menú que aparece selecciona "Create folder".



Esto creará una nueva carpeta al mismo nivel que "data". Click derecho sobre esta nueva carpeta y selecciona "Promote to package". A partir de este momento, esta carpeta funcionará como un nuevo paquete.



Este nuevo paquete puede contener subcarpetas, archivos, etc. Tras compilar el juego, verás dos archivos paquete, el paquete básico "data", y el nuevo.

Si seleccionas un paquete en el árbol del proyecto, puedes ajustar sus propiedades en el panel propiedades, incluyendo el orden de prioridad.



Por si ayuda ...

Jose tradujo al español gran parte de la documentación y el libro de WME. Y aquí encontrarás la versión traducida de la wiki.

13

Software and games / Wintermute in other Operating Systems: Wine Edition

« on: May 30, 2021, 12:02:43 AM »

Recently I installed Wintermute Engine Development Kit in my GNU/Linux machine (by means of Wine 5.0) and I was nicely surprised to see that everything worked: every tool and every demo (including those with 3D features).

I also tested several games made with WME (The White Chamber, Kulivočko, and James Peris) and they all worked nicely - no apparent lag, loss of graphic quality or bug.

As far as I read, these are the operating systems for which Wine provides binary packages: Android, Ubuntu, Debian, Fedora, macOS, Suse, Slackware and FreeBSD. It can also be built from source.

Notes (after installing Wine):

(1) Wine comes with its own variant of DirectX, so there's no need to install native DirectX (in fact, they recommend not to). I didn't.

(2) I installed .NET Framework 2.0 (as suggested by Wintermute installer). Apparently Wine also comes with its own version (of .NET), but since Wintermute is working this way ...

(3) Wine does not sandbox malware. If you use Wine, you should be careful about which Windows programs you pick (in order to avoid installing malware). Never run Wine as root (not even sudo). Never. There's no need for it under any circumstance.



Wine (originally an acronym for "Wine Is Not an Emulator") is a compatibility layer capable of running Windows applications on several POSIX-compliant operating systems, such as GNU/Linux, macOS, and BSD.

Instead of simulating internal Windows logic like a virtual machine or emulator, Wine translates Windows API calls into POSIX calls on-the-fly, eliminating the performance and memory penalties of other methods, and allowing to integrate Windows applications into the desktop.

14

Technical forum / Re: Objects picked up are not showing in Inventory Box.

« on: May 26, 2021, 03:16:33 PM »

Hey Cliff

It's great you found an answer to this puzzle !!

Half way down this page, you'll find more information relevant to this situation.

there are two ways, how to approach inventory – Global (one inventory for the whole game) and Actor based – each actor has their own inventory

15

Game announcements / Re: Chaos Realm

« on: October 08, 2020, 02:00:31 PM »

Heeey Chaos

Nice to see it