[TeeUniverse] Devlog (Page 6 of 12)

Sorry for what ever reason when I look at that post I see the image so I thought he was saying that the contents of the image would not work with his system. I will try to get the image working.

I will create a branch on github once the asset editor is usable (but still not finished, of course )

Do you use Linux or Windows ? What are exactly these errors ? b.t.w., the editor is not yet commited.

I like it, but I'm not sure if this will be very useful in term of workspace. Like I said, you need to be able to switch between assets in the editor to make something. So what you proposed will be more or less a start screen that will be never use during the creation process. However, such interface could be made to explore a list of assets available online.
You will certainly understand what I mean when you will try the editor

I've pushed the last version on GitHub (in the assets-editor branch : https://github.com/teeworlds-modapi/tee … ets-editor). So you can try it and play with it. Off course, its still far from finished, but it's usable.

Important missing feature :
* Choose the filename for load/save operation
* Create a list of sprites (which are used for muzzles)

How to create a portal gun with the Assets Editor

• Add this image in your teeworlds folder : http://file1.npage.de/006389/76/bilder/portal_v2.png

• Click on "Assets Editor" in the main menu of Teeworlds ModAPI. The Assets Editor (AE) is made of 4 parts : the Assets List (left), the View (center), the Editor (right) and the Timeline (bottom).

• In the Assets List, click on the "+" icon of the "Images" section. A list of images available in your teeworlds folder is listed. Click on portal_v2.png

• Now, the new image is displayed in the view. Since this image will be used to make sprites, a grid must be defined. In the Editor, set "Grid Width" to 32 and "Grid Height" to 16 (yes, you must click 32 times on the + button for now ). The grid should be displayed over the image
  

• In the Assets List, click on the "+" icon of the "Sprites" section. A new sprite is created. You can rename it in the editor. We must also change the "Image" associated to the sprite, which is set to nothing for now. Click on the empty button just after "Image" and select "portal_v2.png" in the external section.

• The last step to create the sprite is to define the coordinates of the sprite in the image (X, Y, Width and Height). To make it easier, click on the "eye" button of the asset "portal_v2.png", in the Asset List. Now, the View show the image, but the editor is still related to the sprite. You sprite is shown in red in the View. Edit your sprite with the Editor in order to get X = 2, Y = 12, Width = 8 and Height = 3. To make sure that your sprite is correctly created, click on the "eye" icon of your sprite in the Assets List. The portal gun should be visible in the view.
  

• Exercice : try the create a sprite for the "cursor" of the portal gun

• To create the weapon, click on the "+" icon of the "Attaches" section in the Assets List. An attach is more or less a gun with all its graphics effects. You can see in the View a Tee that hold nothing. The big "Eye" circle in the view can be drag and drop to change the aim of the Tee. The same can be done with the big "Arrow" to change the motion direction of the Tee (this is used for the orientation of the ninja blue things)

• In the Editor, click on the empty button just after "Cursor" and select the sprite that you have created as exercice. You should obtain this:
  

• Still in the editor, click on "add element". A new part of your weapon is now ready to be edited. Click on the empty button just after "Sprite" and select the sprite for your weapon. Set the "Size" field to 96 in order to make your portalgun visible.

• Set the "Alignment" field to "Aim". You should obtain this result:
  

I will explain later how to add animations in order to correct the position of the gun (I've found a small bug in the interface for that).

It worked for me when I clicked on the image not available image.

I can't try it because I don't have windows. Can you send me the output ?

For sure. I can add a new part called accessories, and add animation for accessories and decorations. What kind of animation do need for that ? I've only implemented position, rotation, scaling (x and y) and color. Is it enough for hair ?

Edit: b.t.w., don't spend too much time on the editor, because your saved assets will be no more compatible after few updates.

Each animation can now specify a width and height (not committed yet). In addition, it's possible to create a list of sprites and tell in the animation which element of the list must be used. It's used for muzzles, but it could works for hair as well.

All animations use the same system, so they can do the same things. The only exception is for tee animations, because the sprite that they use are defined somewhere else (the skin). In the current system, a weapon is made of elements, a sort of layer. The weapon itself is an element, and muzzles also. There is no more something called "muzzle" in the code, but rather just one element of a list with a sprite and an animation that correspond to a muzzle. In your example, the gun will be made of 4 elements : two elements for the gun with different animations, and two elements for fire effects.

Did you tried the editor ?

No, the effect of the attack trigger is done by the server, so it's a separated concept called "projectile" or "laser" depending of the weapon. I've implemented a LineStyle asset to create any kind of effect for line based weapon. For projectiles, nothing is done yet.

All teeworlds weapons are now using the same system in ModAPI. You can create rifles, swords, kungfu attacks or remotes for example. The only limitation is that only one animation per weapon can be done. If you want to create an reload animation, you must create a "reload" version of your weapon and change the weapon depending of the situation (it's completely transparent from the point of view of the player).

Let me interrupt you.

I think you are going to make modapi less teeish. I know I hate that adjective too, but teeworlds was built with simplicity in mind, please don't change that I like it that you can build, for instance, a portal gun, but there is a reason why there is only one melee weapon (the hammer)

I guess I don't understand. From the standpoint of skemone who would make a gun I would think that I would make the graphics, the animations, place it were it needs to be when the tee holds it, all the attributes that the gun has, maybe some actual programming to make completely new functionality, rap it all up in a fike/many files that I could post here that people could then use for their mods which are somehow put on a server which sends packets that the client then interprets and presents it on the players screen.......  As a person who is making a new gun for Teeworlds I don't really care how everything up to presenting an image to the player works. I just want to know how I can save myself some work and make one bullet animation for three guns that could fire the same bullet at three different rates. I really just want to make the shooting animation, the bullet animTion, the reload animation, and maybe the empty animation. And I think it would be best if it were presented as "the same gun".  Whether that's true or not does not really matter the the one making the gun. That's what I am saying. Now for modders who want to make a gun that can not do what ModAPI gives them out of the box all of this stuff may be nessisary to know when coding.

I'm thinking of the portle gun, siile's weird guns: https://youtu.be/drTpEd99ZI4 or this thing: https://m.youtube.com/watch?v=i3882wFkAAo

I am sorry but I absolutely hate the fact that Teeworlds HAS to be simplistic. Keep it simple stupid is a montra that is used way too much.  I love Teeworlds simple design and game play but keeping something simple for the sake of keeping something simple (stupid) is just that stupid.  I envision a Teeworlds that is way more complex than what we have today, but the devs/community is too scared to change their perfect game. Change is scary but sometimes it is a good thing, and to not even try something or discuss it because we need to keep it simple or I don't want to implement something is just silly and is in my opinion killing this game.