Search results

I created a wiki page about this topic: Please have a look and feel free to extend and comment it: https://github.com/MovingBlocks/Terasology/wiki/Versioning-Guideline

Well for me that result of yours is not surprising: When you ask the graphic driver to give you the bytes of something which hasn't finished rendering (asynchronous on the graphic card) then the call of glMapBuffers/readBackPixels() will block till the rendering is done. If you ask the graphic...

I started woring on it. You can view a work in progress version at: https://github.com/MovingBlocks/Terasology/compare/develop...flo:no-static-access-part1 It introduces a new Context intreface, with a get, put and delete method and makes the CoreRegistry be based on that Context object. Thus...

I guess it is to early to decide if we want to remove the old single player mode or not. I suggest we add a client+server option without removing the old singleplayer for now. Then we can see how it goes if that is the only mode we use for testing.

Name: Making singleplayer a special case of multiplayer Summary: Make singleplayer be in the background a headless server + client. Scope: Engine Current Goal: Making singleplayer a special case of multiplayer Phase: Design Curator: Florian Related: - The idea is to make singleplayer a special...

hi, I am also for the removal of the author tag. Espeically without email address it has as good as no use.

Even if we folloe SemVer, once the "api broke" version number gets incremented, all modules that used it should be seen as incompatible. e.g. if a module depends on engine 3.4.0, and we release engine 4.0.0 then all modules that depended on 3.x.x ( maxVersion = 4.0.0) can't be used with the...

@Cervator: I started reading and could not belief when I could scoll agan and again ^^. About module dependencies: You can define a minVersion and a maxVersion. If a module works for 1.0.0 and 2.0.0 you would set minVerison to 1.0.0 and the exclusive maxVersion to 3.0.0. Or when we are at 0.x.x...

hmm, yeah, maybe we should sperate engine and terasology releases (with modules). Then we can do a engine release with a increment of the 2nd version number to indicate a broken API and a increment of the third number whenever we add a feature to the engine that is needed by a module.

hmm, and how would you want to get away from "developing modules against the developemnt version"? When we change an used API the modules won't work with the engine till they get updated. We could delay the updating ofthe modules till the next engine release but typically it is easiest to change...

Currently we increment the version number which each stable release. Currently our version number is "0.50.1" (see engine/src/main/resources/engine-module.txt). While this ensures that dependency management works well for stable releases it often does not work during the development. e.g. going...

Entity ids are now longs. This is "finished".

The zip file system we use failed to write the changes to disk by renaming a temporary written file to the new name. I can only assume that there was something else that was still accessing the file and thus prevented the replacement. Please double check that there is no other terasology...

For stable build 50 you can use the attached module to give all players per default the permission to cheat.

@Cervator: No stacktrace?

I agree with @Immortius about being careful about not over splitting the engine without need. In general I think we should wait with adding complexity until there is need for it. Specifically I think we should simply merge the pull request from @Josharias which moves the starting inventory...

It could be that this is or at least was possible already with RelevanceRegionComponents. e.g. you create a entity with that component at a region which you wanted to have loaded in addition to the current position of the player. Although there were some opimizations recently to primarly...

Please create a github issue with a exact graphic card & driver version name. We may be able to create a workaround for your graphic driver by removing the "f"s from the constants. We explicitly state that glsl 1.20 should be used, so it's a bug in the graphic driver that it complains about...

I guess you are right, "Maintenance" is better fitting now.

I created a github issue about torches in hands. Is that the same issue you had? https://github.com/MovingBlocks/Terasology/issues/1527