?

it does not store it no..
it goes through a process that is in an initial state, this is a number, the number is from x - max_32bit, from this number it can only generate finite number of possibilities but is limited after all to the max 32bit number
for every affix that is created, is generated from this initial number in a sequence
it's not that it is not possible to go higher then 32bit.. it's that they used 32 bits to do the calculations (this is not entirely true but for the initialization of the sequence, it is)

edit:



If you have start of a sequence, it's a 32 bit number, anything that is generated from that number will have the same sequence, hence it is limited by its initialization.
So it certainly does determine it.

not sure what difference it makes now.., it's been 7 years since it got "fixed"

This post was edited by tunglidid on Dec 9 2024 07:00pm

The size of a 32 bit integer doesn't determine the states of the program though?

I haven't looked at the details behind how the game generates items, the data representation, or the source code. Have you?

The only thing I'm saying is: I would find it surprising if the developers wrote the code to represent items by 32 bit integers. I have a strong suspicion that that's not true. That's something you would know by understanding their design or code.

This post was edited by zero_sharp on Dec 9 2024 07:08pm

https://forums.d2jsp.org/topic.php?t=80627599&f=21
see post #6 and #9
i'd trust what this guy says

thanks

Also:
It's possible to make replica of rare items. I. e. it won't be duped but it'll have same same name and stats (it comes from the fact that rares stats are being generated from 32-bit seeds and 2

32

is not that big number these days). Shadow Loom is also already existed, i. e. it was generated from the same seed but my version should have different id to survive any head-to-head tests within one game. It was generated as any other legit item generated when you're completing imbue quest.

........


My guess is that id is an another 32-bit number, so there can be only 2 such axes (== any other items). Once you've got same 32-bit seed for name+mods AND same 32-bit id -- that's when dupe scanner will start wipe absolutely legit items Anyway 2 is a big enough even for today's standard to really face this problem.



https://forums.d2jsp.org/topic.php?t=73613914&f=53

This post was edited by vasya on Dec 10 2024 12:15pm

Love that 1700 damage Thunder Maul.

GG

I believe others said it was hero editor item. Still fun to look at.

I wouldn't complain if someone made a 100% eth tomb and posted here

I tried to look into it yesterday. I'm not sure where the dude talking about 2^32 initial states gets that information from. Also the seed is likely only one part of the data representing the item.

Here's a page where somebody partially breaks down the .d2s/item encoding:

https://user.xmission.com/~trevin/DiabloIIv1.09_Item_Format.shtml

spoiler: it's longer than 32 bits. It's apparently designed to be variable length. Let me know if you can source the 2^32 thing.

Also, the other point is this: even if there were 2^32 possible options for the tomb reaver, how do you know the perfect one is not represented (or: can't be generated)? lol

This post was edited by zero_sharp on Dec 10 2024 03:04pm

Did you just compare:

Item save format
to
The process of generating an item

?

spoiler: they are not the same thing..

please read what is being said

Where do you think information comes from? I'll answer that for you, it comes from other people who have done the research or know it in other ways

Cool. Show me.

I'm over here guessing at wtf you're saying because it's so vague.

This post was edited by zero_sharp on Dec 10 2024 05:09pm