Posts by Kademlia

Alles relativ offene Fragen bis auf Inventare im Screen bleiben relativ sicher erhalten.

/back würde ich vermeiden wollen wenn möglich. Aber kann sein, dass es nötig ist in irgendeinem Umfang

"Warum startest du etm nicht sofort"

und gleichzeitig

"Warum baust du das extra Feature nicht ein und startest 2 Monate später"

gleichzeitig verlangen ist schon geil. Rip

Das ist mir schon bewusst. Der Aufwand hat auch nichts mit der Idee oder Vorstellung zu tun, sondern nur mit der Umsetzung.

Prinzipiell geht das, aber die Verwaltung von einem "echten Slot im Inventar" der aber nur unechte Items enthält ist eklig. Jeder kleinste Bug produziert direkt "invalide Items" oder lässt items verschwinden etc.

Ausgelagert auf den Screen sind all diese Probleme nicht vorhanden.

Für die Anzeige des Rezepts an sich sicherlich - aber der spannende Teil wäre eher, dass du eben dann die einzelnen Zutaten anklicken könntest um das Sub-Rezept zu erhalten oder Rechtsklick für eine Beschreibung etc.

In "gut" also entsprechend aufwändig

Zusatzinvenstar:

hier ist die Frage WO dieses Inventar ist. Du kannst es halt nicht im normalen vanilla 'E' Inventar einfügen.

Mein Plan bisher wäre halt eins im Screen, welches man vielleicht als 'Raumschiff Lagerraum' deklariert. Du hast also nur Zugriff, solange dein Raumschiff auch in der Nähe ist (selber Planet).

(Raumschiff ist noch nicht implementiert / Brainstormed)

Spannend fände ich hier vor allem wenn der Screen eine Hilfe ist für die Werkbank usw.

Speziell für die Tools hättest du dann immer direkt die Crafting-Rezepte als Erklärung mit drin.

Leider aufwändig

Hey - I think this is way to detailed already. We currently just brainstorm about the possible ideas of how to implement something.

Generally "Skills" should be implemented (if possible) with:
1. Research (Character Upgrades; Items needed to get to the next level)

2. Tools (Crafting of Item needed; possibly research of Tool needed)

3. Additional Armor-Pieces you can put into the 'player' (see image), you can swap the virtual armor-pieces to get different kinds of benefits depending on what you want to do. But this system is still just an idea and not implemented

- Tools will often times be personalized - trading not possible

- Armor-Pieces might be character bound - trading not possible YOU need to get it

- Research is player-bound anyway (maybe guild-based somewhere in the future)

If you have a different Idea that does NOT fit into this system please specifically describe what is different and how it might be better or just different (and you prefere it because X).

Kade

Da will man einmal Britta los werden

Quote from crazyelectronics

1) Shulker box limit is not enforced when using a dispenser

Shulker Boxes are a special case generally on ETM (in terms of management in code as well as being OP for farmworld farming). They will be disabled at least in the beginning. I disabled them in dispensers

Quote from crazyelectronics

2) Creative copy with nbt data doesn't work +NBT is correctly shown when in inventory

Should be disabled now. Only known itemstacks can be copied. This means all player-heads cannot be copied unless they are saved into the official h_NAME system

Quote from Smiley!

Sheeps eating gras aren't growing any new fur.

Vanilla for now again

Quote from EinKuenstler

The snowballs are not despawning, guess that's not good for the performance?

Fixed for all types of projectiles. They will die after 500 ticks of flying upwards (getting pushed up).

TigA  crazyelectronics

Fixed the chestbug. It was caused by a small oversight in copy paste

        if (flag) {
            iblockdata1 = (IBlockData) this.blockIds.setBlock(i, j, k, iblockdata);
            this.obfuBlockIds.setBlock(i, j, k, iblockdata);
        } else {
            iblockdata1 = (IBlockData) this.blockIds.b(i, j, k, iblockdata);
            this.obfuBlockIds.b(i, j, k, iblockdata);
        }

While updating from 1.12 to 1.16 in terms of anti xray i accitentaly duplicated the lines and overwrote " iblockdata1 = " two times in each if case

EinKuenstler

probably this, but yeah needs fixing: https://bugs.mojang.com/browse/MC-125757

- Dying keeps fly status alive on client side

Terraformer is currently in the works.

Twitter

"Pond creator" might be something

Quote from crazyelectronics

Again me

1) fixed

2) thats right-clicking test code

3) Screen interaction from behind is now fixed

3) 'This removes/hides items in chest' no easy reproduction known - unsolved until then

4) Shops are on hold until tools work for shop-sign-creation

Added Useroption KsonTransactionPageSize. Dfault pagesize is now 50

public static final Option<UserOptionType, Integer> KsonTransactionPageSize = register(new IntegerOption<>( UserOptionType.KsonTransactionPageSize, 50, 10, 500, true));

• Deleted all Transaction; changed json layout of transactions on database side to allow ordered querying

Something like this should now work:

https://s200.etm.dev/transaction/Kademlia/after/0Y1QW1N2

path = "/{username:.+}/after/{transactionId:.+}"

Quote from crazyelectronics

1)

Missing Permission check at sponge Tool (Screen of Farmworld think protected with worldGurad). I cannot use the tool on street / other plots

2)

Screen Cursor is only updated by changeing looking direction (rotatating the head)

1. Was kinda shitty on stream already - change implementation now three times to get it to work with worldguard + landli + CB events. Should work now. Current drawback: Kills water AND sponges

2. Was disabled by design - enabled it again. Lets see how much cpu gets wasted by this

Quote from 125m125

server sent events could potentially also be interesting

You are just talking about getting websocket messages if something happens on the server right - that would be the way to inform you similar to long-pulling.

It will look something like this:

{
  "subject": "xxxxxxxxx",
  "data": {}
}

Where data is any kind of json object and the subject would be a unique identifier for the data object

Interpretation than just would be something like (typescript/angular)

  private handleWsMessage(msg: WsMessageDto) {
    switch (msg.subject) {
      case WsSubject.Chat:
        this.chatSubject.next(msg.data);
        break;
      case WsSubject.Transaction:
        this.transactionSubject.next(msg.data);
        break;
      case WsSubject.Mail:
        this.mailSubject.next(msg.data);
        break;
    }
  }