Thanks, glad you enjoyed it! :) Feel free to ask questions :D

Thanks, I searched for so long to find a royalty free track like this. :D And I could even use it in the commercial version if I wanted to, but most likely I'll make something very similar so I can I call it my own :D

@@Tudvari Awesome. It's tempting to use royalty free stuff, but the reward from having your own is 😋

Thanks! I started with 1 item = 1 slot as well, but it can be improved in a few hours or so. So if you like that way better, don't be lazy :D Cheers!

Well, I've got some ideas in my pocket, and people told me they are good and got the right amount of change, so I'm hopeful. So you mean that you'd like the game to be isometric? :) Or you like to current top-down? As I see Stoneshard is a different kind of topdown.

@@Tudvari both of them are great I mean any point of view could be exciting but looking forward for your second game ;)

Thanks! :) I just simply use ScriptableObjects. I create them, set the values, and after that I can instantly do with them whatever I want. They handle inheritance, so I can have a common base for random and fixed (i.e. Unique) items, and I put an ItemType enum on them to differentiate Gloves from Boots for example. :) Yep, I was surprised as well how well the grid inventory works. I think I got the base from a quick google search, luckily it's a pretty common feature so there are tons of tutorials, saving you a lot of brain power :D Cheers!

@@Tudvari Thanks for the reply. It still bugs me I don't quite know how you go about creating and saving those unique objects created from SOs :D. Technically if you store SOs as an asset file, you will have to save each variation as a separate asset file. And speaking of saving those items, you can serialize its instance id or whatever its called to json, but runtime instantiated SO (if one were to create variations runtime) instance ids are gibberish, so no point saving those. Of course there are ways to circumvent this, but I haven't so far found any good way.

@@322ss Oh, now I know what you mean. I use ScriptableObjects only for the timpleate on which items are created (generated if random template, and just copied if fixed template). And you are talking about saving and loading the item instances themselves from a save file, right? If that's the case: The Items are just simple C# objects which are created based on these Templates. They are all easily serializable in a JSON, then loaded as well, because they are pure C# objects and they only contain primitive values. Or have I misunderstood you?

​@@Tudvari Well that is pretty much what I was talking about. It works, but I haven't yet found a way to represent many item types easily, unlike Scriptable Objects, Unity doesn't like serializable class subclasses in lists and such as there is pretty weak support for polymorphic serialization in Unity. So I haven't yet found a nice way to streamline loading/saving/inspector editing of items that are simple serializable class based, when I have multiple item types... that is.

@@322ss I see. Yeah, it's hard to find a good design :\

Hi! I would, if it wouldn't be just silly dice rolling with lots of if-elses. :D Basically I just generate a random number from 0 to 1. - If the number is less than 0.1 (10% chance) it will have a minimum of 4 affixes and I will style and name it as a rare item. - Else if the number is less than 0.5 (40% chance) it will have a minimum of 2 affixes --> magic item. - Else (50% chance) it will be a normal item with a minimum of 0 affixes. After this I also generate a number from 0 to 1 and with 50% chance I add 1 extra affix on the top of the minimum. I do this 3 times, sooo: minimum + (50% chance for 1 extra, 25% chance for 2 extra, 12.5% chance for 3 extra). Or something like that, maybe I messed up the propabilities :D On the top of this you can do edge cases like only boots can have movement speed affixes, only weapon can have damage affixes, etc. You just have to write a method which returns the pool of possible affix types based on the item's type. I already have some other extra details in it, can't really remember them but can't wait to add some more! :D Hope I could help! :)

@@Tudvari wow hey! Thanks for the fast reply. Do you have an item factory stating instance thay you just call when a monster dies like ItemFactory.CreateRandomItem()? Or how do you handle thay aspect? That's what I struggle with too is figuring out the framework in how and where to call this generate function. Also my item affixed are enums that I query from an equipment script on the player using an interface that loops through all the equipped items and asks them for a particular enum Stat like "health" and qdd these to a basestat script on the player that keeps the total sum so UI can ask the basestat script like. What is my health? Etc..

@@truth8483 Basically I have ScriptableObjects which describe the item generation's parameters and those are the assets I put into loot tables. Once a monster dies, I roll a schema then call its Generate() method to create the actual item. Then I'll assign this item to a "Loot" InteractableObject which has got just spawned on the floor. I handle the player's/equipment's affixes the same way, I think :)

@@Tudvari Thank you sir. I'll be thinking about what you said and seeing if I can find a way to make this work!

Thanks! :)

Glad to hear that! :)

Sajnálom, hogy elrontottam a napodat. :\