Really stupid things that people have said about Modded MC(Off topicness makes moderators tired)
- Thread starter Qazplm601
- Start date
- Status
That is...very unlikely. Unless they use some very precise compression methods that, again, make massive use of bitwise operators, then ints are stored on disk exactly as they are in memory.
Admittedly, that comes from my C++ days, where the quote (I forget from whom) that stuck with me the most was: "If you have char* anywhere in your code, you have a bug. std::vector exists for a reason."
(For the those who do not know of the glory that is C++, char* is also known as a C-string. Due to how C/C++ works, pointers, any data type followed by an asterisk, can work and be addressed exactly like arrays. However, due to the potential for mismanagement, the fact that C/C++ requires that you manage your own memory, and the fact that pointers are allocated on the heap instead of on the stack and thus must be deleted manually in code, pointers can lead to many, many problems such as memory leaks, which can also be potential security risks.)
I think you mean orespawn and divinerpg but both of these mods where based in 1.6
I don't even know what a mutable field means, but the very name just sounds wrong on many levels.
Mutable as opposed to immutable - i.e. final. In other words, having an object that has properties that can be manipulated by other objects is bad programming.
It is one of the core concepts of OO programming.
I do not understand people who feel that using design features of a language is bad design, that a good programmer deliberately handicaps themselves by limiting their toolset, like when people say using automatic imports is bad form.
Last edited:
Any object can be changed, even if its final. According to him, everything is bad programming.
The only way to change a final field is with ASM or reflection, and these people have a really strong hatred of that; I nearly got kicked out of the Forge IRC for saying that I preferred reflection to a custom handler class that can "fail cleanly" for mod interaction.
I have no idea why people hate reflection. It's simple to use, and doesn't cause any big trouble.
Is "failing cleanly" one of the reasons why when modded MC boots up it usually displays a whole bunch of exceptions in the log, and yet never crashes? That annoys me so much. If there's a problem, I want to fix it, not overlook it.
"OMG ITS SLOW AND ITS SOO BAD! CODE FORM! DONALD KNUTH! STANDARDIZATION! POLISH NOTATION!".
Actually, reflection tends to generate more of that. However, it is preferable to crashing outright for mod interaction code.
Set up a macro command to give op and then immediately take it away.
After all, he was given op, you just never said for how long.
This still happens? The player is asking for lots of lovely torture in many different ways. Oh the fun we used to have when this happened on my vanilla server
http://minecraft.gamepedia.com/Chunk_format
Look at the ExtendedBlockStorage class. They're actually using half-bytes (aka nibbles) for that in the memory.
Accessing an element in such a nibble array basically goes like this:
Code:
byte value = array[index >> 1];
if(index & 1 == 0)
return value & 0xF;
else
return value >> 4;anyone still remember the time when you still had to edit the jars to install mods onto minecraft?
You still have to do that with the few remaining plugins. Though with the loss of... what was that called? 1.6 will be the last version of minecraft that happens in.
Celestialphoenix
Too Much Free Time
We still do.
Now you also have to rename stuff in the .JSON and several other steps that make it significantly more complex- as well as drag and drop the files with WINRAR.
(Why do you think we all use 3rd party installers now?)
As far as I can tell, the only things that are really TFC-like are the getting sticks from trees and the fact that you can knap. But even then the sticks thing is much more complex as it not only makes saplings useful, but also adds a choice in how one uses saplings: burn them, grow them or convert them, and with saplings taking immense amounts of time to grow, it's often much more viable to just convert of burn them. Knapping, on the other hand is just a single shapeless recipe with a single item as output, it's really nothing like TFC knapping other than how you use 2 stones.
- Status