[TeeUniverse] Devlog (Page 7 of 12)

How do you install this? I am running Ubuntu Linux 14.04 for a minute and I already have your source code.

@necropotame no please bot. There is a better way to compile on Ubuntu.

sudo apt install bam build-essential python
cd to/the/source
bam -j <number of cores>

(the last time I checked the dependencies.... Bam is the build system (specifically made by magnus auvinen for teeworlds I think, but in the repos), build-essential is the compiler and python is needed for the scripts I think). The -j option speeds up the build enormously (on my server, it compiles the server from scratch in less than 3 seconds)

Sorry, I forgot to mebtion

For 0.7: libsdl2-dev
For 0.6: libsdl1.2-dev

Install them with

sudo apt install lib....

Teeworlds0.7 without included SDL/Freetype = many questions like this

Please avoid insults, particularly to devs. // Dune
Removed insult to Oy // heinrich5991

(I had enough time to read what you wrote)

It's because he also thinks it. And I also think it, it is VERY stupid (to act like Oy did).
I was gonna ask the question too but I found some help fortunatly, after an hour of two. (Maybe more lol)

I deleted what I said because I figured a moderator wrote the red, I have seen it before and it looked odd.  Also Neox you have a PM in your mail box.

ubuntu@ubuntu:~/Downloads/teeworlds-master$ bam -j 4
[1/2] #1 c++ src/engine/client/text.cpp
src/engine/client/text.cpp:13:22: fatal error: ft2build.h: No such file or directory
 #include <ft2build.h>
                      ^
compilation terminated.
bam: 'build/x86_64/debug/objs/engine/client/text.o' error 256
bam: error: a build step failed
ubuntu@ubuntu:~/Downloads/teeworlds-master$ 

I am still getting this error even after installing bam, build-essential, python, and libsdl2-dev. even tried bam -c config before I did bam -j 4 again.

Sounds great and all, but what you need teeworlds for? Dropping vanilla compatibility would make the development much easier and faster.

After looking a bit into github api docs, my suggestion is possible, but maybe a bunch of work.

Introduction
Basically we have a central repository hosted on github for sprites/mapres/other mapping stuff. One who makes a map can browse the repository, search it etc, then select it and use it. Thanks to the mapinfo file (or it'd replacement), these resources stay at github and a modapi server fetches them to serve them as embedded to non modapi clients, or a modapi client fetches them directly from github. We can even manage licenses if we say, like, "everything there is licensed cc-by-sa" and let the server generate a license info text (on modapi client a discrete text box, on non-modapi motd appendix). New data is done by pull requests via the api

So how to use uploaded files:
- map-making client downloades them to generate a mapinfo file and display them
- map-running server downloades them to serve them as "embedded" to non-modapi clients
- connecting vanilla client gets them via embedded pictures
- connecting modapi client gets them as link or such, where to find it on github and fetches it

How we add new resources:
1. resource creator presses the share button, client loggs into github api with a token, otherwise request a token for this usage (public_repo scope)
2. Forks the central repo if its needed
3. Create a branch for the forked repo
4. Use the "upload file" / "create file" method to push one file to the branch
5. Create a pull request to the central repo

6. A member of the approval team sees the pull request displayed in the client
7. Presses either allow or deny, while the only rule is the name and/or the category (don't put quads under sprites and such), if deny a short message why)

Additional notes:
- we need a pull request limitation to only allow adding new files
- everything is possible with the github api, even displaying the pull requests' pictures as a selector for the pull requests, even select the type while uploading, maybe as second repo or as Metadata
- this may require a bit of work

"FAQ":
1. Why choose a central repo?
This is, because it makes creation of maps much easier if we have every compatible work in one place.

2. Why choose github?
Just because github is the fastest and most reliable host, and provides a good api

3. Why cc-by-sa?
I think shared mapres should be licensed under creative Commons. This also applies to just normally forum-shared stuff. And it makes managing copyright easy because the server can just generate a copyright note for you

4. That repo is git. Can't everyone access it, and via the Web page?
Although you could possibly clone repos and merge and such, it is not recommended too do it with a standard git client. Using github client as well as "hub" may he content of a discussion, the same applies to the github web interface. 

I wanna say that this is a bit too large for me, but I would be very thankful if you at least think about it.

So what exactly are the dangers of a faker?

That's just a bad admin, not looking carefully enough and just banning by name.
I used to run a few servers myself with a lot of cheaters and such things, but I never ban people by their name but only by their actions.

The players on the other hand, well, if they know you, they would (should) know that a person with the same name, but acting completely different is very likely not you.
For the players that you don't know, why would you care?

If someone wants to make this a reality then someone should make a vanilla Teeworlds/modAPI compatible mod that server admins could add to their servers. this really is not a modAPI thing but a mod you would place on top of modAPI. That's kinda the point of modAPI is to be a framework for other mod makers to build on top of.