[1.4.7]Packet Handler

[Moritz]

Hello. I got the problem with the facing and it is not fixed.

 

and i think that i will need for all this a packet handler.

 

First the facing does not work with this code:

 

https://github.com/Speiger/DynamicTools/blob/master/spmod_common/speiger/src/tinychest/common/tileentity/TileEntityBasicTinyChest.java

 

 

Also i need here 3 booleans and 2 integer here, 1 for facing and the other one for the stacksize

 

Source:

 

https://github.com/Speiger/DynamicTools/blob/master/spmod_common/speiger/src/tinychest/common/tileentity/TileEntityAdvancedTinyChest.java

 

so how can i make a packet handler can someone explain me that?

[Moritz]

ok then tell me what i have to do how i can store these informations:

 

integer: facing.

integer: stacksize.

boolean: isFull.

boolean: isEmpty.

boolean: stacksize going up

boolean: stacksize going down.

 

So how can i store these informations. without that any chest tell her informations to annother chest?

[Moritz]

without that any chest tell her informations to annother chest?

You will have to do that. There are 2 chests. One client, one server.

The server one tells the client one what the data is.

 

I meant when i place two tiny chest i the near of each other that these have the same facing (when i place the first one at the north and the other one into the south) thats my problem.

 

Also every time i place the any kind of block the facing go automaticly to 0 which means down.

 

that sucks. maybe it would be better that use more block ids but do not have these f.....g bugs.

 

[Moritz]

I only want to make 19 differend chest.

 

I want that all have facing.

Also 10 of them giving a redstonesignal when their full or empty.

And i want (and this is the most important thing) that they work seperate.

 

And nothing does really work!

The act as 1 Block. with facing, with redstone signal. that sucks!

So again how can i make that that they do not share their informations with each other type of chest.

 

if they share their information with client / server that would not my problem but they share it with every tileentity which is inside of the block!

[Torojima]

you should really (no, really ... REALLY, DO IT!!!) look up what the keyword static is doing ...

 

and you should get your indention right ...

[Moritz]

you should really (no, really ... REALLY, DO IT!!!) look up what the keyword static is doing ...

 

and you should get your indention right ...

 

Sorry for being stupid. but what are you mean with static?

[Moritz]

you should really (no, really ... REALLY, DO IT!!!) look up what the keyword static is doing ...

 

and you should get your indention right ...

 

Sorry for being stupid. but what are you mean with static?

[Torojima]

you've got two fields

private static boolean isFull = false;
private static boolean isEmpty = true;

 

set to static. So either you want to have *all* of your instances of the class set to the same value (which doesn't make to much sense in my opinion and in yours too if I do interpret your comments correctly, or you do not use the static keyword correctly. If you want *every* instance (aka your individual chests) have an individual setting you have to remove the static keywords. With static the field is not a object, but a class field, can only accessed via the class and can only have one value at a given time. If changed, it will change for every object ...

 

Google, searchwords "java static" first hit

http://www.javatutorialhub.com/java-static-variable-methods.html

 

there might be better explanations ...

[Moritz]

Solved