[TeeUniverse] Devlog (Page 10 of 12)

yah I just can't use Synfig. I thought it would be a good animation tool but I just don't like the way it works.

Sounds like a great time to switch to Ninslash!

A custom teeworlds compatible client and server.

Right?

Shall I create a little website for it? Well, I will do a short sketch but not more for now.

We don't need it yet

Devlog: I trying to finish the first version of the editor so you can test it There is also some important new features.

GUI improvement
I'm still improving the style and the features of the GUI. In particular, it's now possible to resize each "panel" of the editor.

Package system
The package system is a core feature of TeeUniverses. It replace maps in TeeWorlds, and the "Universe, World, Land, Skin" system of previous versions of TeeUniverses. A package is a list of assets AND a list of required packages. When a package is loaded, all needed packages are loaded as well. In the future, when a TeeUniverses client will connect a server, the server will send the list of needed package, and the client will download only ones that are missing or outdated. There is two major advantages with that:

• The client don't have to download the same image multiple times. This will save a lot of time during map download. The idea is to put the map tiles in one package, and the image in another. That way, if the map layout change, but not the image, the client will download only the map layout

• It will become more easier to share stuff on Internet. You can create a package "Beach Environment" with all needed images, animations and sprite and share it on Internet. Then, a map maker will just have to download it, open it in the editor and start to use it in his map. And you can update your environment without breaking the map (and without opening the map, in fact)

A funny point is also that this system allows you to open multiple maps simultaneously. Of course, all this dependency stuff is automatic. When you save your map, the editor looks which packages are needed.
I've converted the vanilla external images into packages to facilitate the conversion of vanilla maps.

Even if you don't want to use the TeeUniverses Client or Server, the editor will provide you a good way to create normal maps. Just think about this package system as a "project file" to create what you want, and finally export it into vanilla map.

Thanks

Small additional note: TeeUniverses will be under the AGPL license. This means that:

• You can't distribute a modification of TeeUniverses (or a mod made with it) without provide the sources in the same time.

• You can't create a modified server without provide the sources to players.

The second point may sounds a bit too much, but this prevents people to create private mods that will be lost later, as it happens a lot in the TeeWorlds community. I also like the idea that, like for maps, you can easily get a mod just by playing on it. In practice, this will take the form of a chat command like /sources, that will display a link to the sources. Since most of mod are on github, I don't think it's really harmful.

Oh wow lol. I was thinking about using it... not to be rude, but there's no way I'll use a project that has such a license. Unless I'm planning on making the mod opensource...

I fully agree with you

Just a reminder in case someone miss it: I've renamed the old teeuniverses git repository to "teeuniverses-old-draft", and created a new one with the name "teeuniverses". So make sure that you follow the correct one It means also that the code is available and you can test it if you want. However, it's not even a beta version, so I don't recommend to do it, except if you want to help me compilation on Windows or OSX (good luck...).

You can follow how things are going until the beta here

There is also a IRC channel on QuakeNet if you need some help: #teeuniverses

Screenshot of the day I'm working on entities edition (in TeeUniverses, "entities" are things like pickups and spawn, while "zones" are solid/nohook/death tiles). You can see also in the toolbar a slider that control the "opacity" of zones. When the opacity become high, the map turns progressively to black, so you can focus on the layout.

I understand your point of view (east, Neox and Henningstone). However, I will not change the license in a near future. My idea is to create a community of mod-makers, with a constant sharing. Everyone should be able to know what is the code behind the game, whatever if you are just a player and an another programmer. No more code will be lost, and the security will be improved.
I understand that sometimes, people want to create a coherent ecosystem without having 100 alternatives of the same mod, with half of them unbalanced or with abusive moderators. However, keep secret the code is not the appropriate answer to this problem. Moderating the master server is definitively more interesting and open. Once your mod start to be popular, the TeeUniverses team will create a new entry in the start menu for you, and will give you the key to moderate the server list inside (in particular, make sure that all mods inside are pure). The visibility will be completely different between a fork and the original version. Yes, I fully agree with TeeWorlds about the "purity criteria" in the server list. It's very important to create something coherent. Of course, an universe containing all non-regular servers will be still available.

If nobody want to use TeeUniverses because if the AGPL licence, I will consider GPL or Apache instead. But I strongly think that it's possible to create a community with the actual one. DDNet, OpenFNG, InfClass and all small mods are already open source. So it's not like TeeWorlds relies on private mods.

The thing is rather that not all people understand how this "giving and taking" works that opensource finally is all about aswell, and they pretty much abuse it by just 'taking'. That means, taking code of you (or pieces of it) and telling everyone that they made it (or even selling it for money; sadly I'm talking out of experience). And eventually they are such big assholes that they actually convince people that YOU stole it from THEM. That's one of the biggest downsides that I see about opensource in teeworlds. Don't get me wrong, I'm also in favor of it, but well... if there are too many scumbags the whole point of it will get ruined.
For example, another popular reason for opensource is that other people can find bugs in your code and help you fix it. In teeworlds, they'd rather use the bugs they find to crash your server (not to be taken as a generalization, there are also many good guys!). But honestly, one scumbag is already one more than you'd like, right?

If you post your sources on GitHub, or in a forum, the timestamp will solve this problem. Once again, someone that don't respect a license should be master banned (in TU master servers, IDK about TW).
Concerning security, both are true, but in long-term, I think everything will be more secure. Someone that exploits your bug is not changing the state of your project, while someone that solve it makes your project more secure.

Nobody is forcing you. This "restriction" will be clearly visible to everyone so they will not even start to work on TeeUniverses if they don't want to publish sources. Please note also that you can create solo mods or lan-only mods without sharing sources, and you can use the editor or the client without problem. Things created with the editor are not under any license, of course.