v6b5/v7 Overworked/Modworked 1.13c Txt Files: Bug Fixes, Descriptions and Modding Support

This forum is for members of the public to post any announcements relating to Diablo 2 Mod Making including mod and patch releases amongst other similar subjects.
User avatar
Cypress
Junior Member
Champion of the Light
Posts: 263
Joined: Fri Dec 01, 2017 2:08 am

Re: v6b5/v7 Overworked/Modworked 1.13c Txt Files: Bug Fixes, Descriptions and Modding Support

Post by Cypress » Thu Aug 26, 2021 10:06 pm

For Overworked v8, I'm running into some rather serious issues. The idea of giving every weapon, boot and shield an ID is a huge mess.
(1) It has to be applied manually to automagic.txt, setitems.txt and uniqueitems.txt.
(2) Properties cannot help, since properties can only force param values, they cannot force min/max values. This is fine for pseudostats (i.e. skills), but it does not work at all for normal stats.
(3) Manually changing the values of ID stats every time weapons/boots/shields are changed would be a massive headache and error-prone.
(4) For boots/shields in particular, I'm relying on a tedious ID system that requires skills.txt spaghetti.

I don't think anyone would be willing to work with such a system. The solution I came up with is adding new txt files that are read by some program which then edits weapons/armor/misc.txt, uniqueitems.txt, setitems.txt and automagic.txt. This would make it very easy to modify and append IDs, but it will likely take me months to finish this program (I realize this is a laughably simple program to make, it just reads and modifies txt files, but I'm a very slow learner).

Also, if I am able to figure out how to make the above program, then I'll also be able to create a modding program, which I'm surprised hasn't been made yet, that would accept instructions to apply specific changes to txt files, which would make modding far less error-prone in general. It would allow Overworked to become modular, which means players/modders can install the parts of Overworked that they like and exclude everything else. With some effort, it would even allow for txt files from different mods to be compiled into a singular txt file, which will make it so mods do not have to be so mutually exclusive (i.e. modders can create simple plugins, like add two new uniques and three new skills, without having to messily copy+paste things over). And given that D2R txt files are at least slightly different from D2's, it will make conversion between D2 and D2R txt files easy.

---
eleriaqueen wrote:
Sat Aug 21, 2021 7:03 pm
Hi Cypress, is it intended that in Overworked, 'Dopplezon' skilldesc uses both a custom string 'stringlife' and 'StrSkill42' that resolve to the same string -> 'Life:'
That was messy work on my part, it would be better to use StrSkill42 instead. I'll fix that in the next update, thanks!

Question
Posts: 87
Joined: Sat Nov 28, 2009 1:53 pm

Re: v6b5/v7 Overworked/Modworked 1.13c Txt Files: Bug Fixes, Descriptions and Modding Support

Post by Question » Sun Sep 05, 2021 4:49 pm

@Cypress : kain_abel_666 suggested I post in this thread. So from what I can gather, overworked is the version that is compatible with vanilla saves while Modworked is not? Do you have a list of bugs still present in the Overworked version?

User avatar
Cypress
Junior Member
Champion of the Light
Posts: 263
Joined: Fri Dec 01, 2017 2:08 am

Re: v6b5/v7 Overworked/Modworked 1.13c Txt Files: Bug Fixes, Descriptions and Modding Support

Post by Cypress » Mon Sep 06, 2021 7:46 pm

Question wrote:
Sun Sep 05, 2021 4:49 pm
@Cypress : kain_abel_666 suggested I post in this thread. So from what I can gather, overworked is the version that is compatible with vanilla saves while Modworked is not? Do you have a list of bugs still present in the Overworked version?
That is correct, Overworked will be compatible with any vanilla saves from version 1.10f to 1.14. The "bug fixes that are not included" file in Overworked\Documentation describes some bugs/inaccurate descriptions that were not fixed in Overworked.

User avatar
erevos
Hosted Forum Moderator
Paladin
Posts: 137
Joined: Sat Mar 05, 2005 7:41 am
Location: Crete
Greece

Re: v6b5/v7 Overworked/Modworked 1.13c Txt Files: Bug Fixes, Descriptions and Modding Support

Post by erevos » Tue Sep 07, 2021 6:52 pm

@Cypress hello again :) Overwork's belts have an issue, the pop up slots are not working. Adding in armors.txt/type2: belt solves this. It was tested on vanilla 1.13c

User avatar
Cypress
Junior Member
Champion of the Light
Posts: 263
Joined: Fri Dec 01, 2017 2:08 am

Re: v6b5/v7 Overworked/Modworked 1.13c Txt Files: Bug Fixes, Descriptions and Modding Support

Post by Cypress » Tue Sep 07, 2021 7:36 pm

Thanks Erevos! However, I'm noticing that it only fixes the issue if type=belt, type2=belt does not seem to do anything. How were you able to get type2=belt to provide additional belt slots?

User avatar
erevos
Hosted Forum Moderator
Paladin
Posts: 137
Joined: Sat Mar 05, 2005 7:41 am
Location: Crete
Greece

Re: v6b5/v7 Overworked/Modworked 1.13c Txt Files: Bug Fixes, Descriptions and Modding Support

Post by erevos » Wed Sep 08, 2021 9:15 am

I added vanilla 1.13's itemtype belt row to overworked. Forgot it yesterday.

User avatar
Cypress
Junior Member
Champion of the Light
Posts: 263
Joined: Fri Dec 01, 2017 2:08 am

Re: v6b5/v7 Overworked/Modworked 1.13c Txt Files: Bug Fixes, Descriptions and Modding Support

Post by Cypress » Wed Sep 08, 2021 3:39 pm

Isn't the vanilla belt row still present in v7? I didn't remove any itemtype rows (aside from Expansion which does nothing), so the itemtype belt should still be present. What I did in v7 was move the types one step deeper. So instead of type1=belt, it's set up that type1=(itself)=belt. Normally, this would carry the itemtype's hardcoded behavior to type1, but from what I can tell belt is an exception to this rule. For example, a hand axe can be made to block attacks if it's type is equivalent to shie at some point, but having type equivalent to belt does not seem to do anything (that is, only type1=belt gives belt slots).

Could you provide your armor.txt and itemtypes.txt?

User avatar
erevos
Hosted Forum Moderator
Paladin
Posts: 137
Joined: Sat Mar 05, 2005 7:41 am
Location: Crete
Greece

Re: v6b5/v7 Overworked/Modworked 1.13c Txt Files: Bug Fixes, Descriptions and Modding Support

Post by erevos » Wed Sep 08, 2021 4:23 pm

i meant i replaced your belt row on itemtypes. Sure i can but its just your armor with type2: belt and your itemtypes with belt row replace by 1.13's belt row.

User avatar
Cypress
Junior Member
Champion of the Light
Posts: 263
Joined: Fri Dec 01, 2017 2:08 am

Re: v6b5/v7 Overworked/Modworked 1.13c Txt Files: Bug Fixes, Descriptions and Modding Support

Post by Cypress » Wed Sep 08, 2021 7:33 pm

It's strange, I cannot get it to work with type2=belt, only type=belt. I must be doing something wrong, but I can't figure it out.

User avatar
erevos
Hosted Forum Moderator
Paladin
Posts: 137
Joined: Sat Mar 05, 2005 7:41 am
Location: Crete
Greece

Re: v6b5/v7 Overworked/Modworked 1.13c Txt Files: Bug Fixes, Descriptions and Modding Support

Post by erevos » Wed Sep 08, 2021 10:42 pm

Check the files
Excel-txt.rar
armor/itemtypes
(19.48 KiB) Downloaded 12 times

User avatar
Cypress
Junior Member
Champion of the Light
Posts: 263
Joined: Fri Dec 01, 2017 2:08 am

Re: v6b5/v7 Overworked/Modworked 1.13c Txt Files: Bug Fixes, Descriptions and Modding Support

Post by Cypress » Thu Sep 09, 2021 12:08 am

Weird, it still doesn't work. I tried a few different txt file sets, different patches, with and without PlugY, with and without window mode and even different graphical renderers (I figured maybe it's some kind of messed up display issue since it involves the UI). No matter what, the belt inventory only shows when type=belt.

Could you try running this belt test? It's a stripped down v7 with only the txt files, your txt files copied over, the binned txt files, saves and a d2se_setup.

EDIT: Whoops sorry, attachment doesn't want to work. https://mega.nz/file/UaRxmKRR#v84JfwS0H ... NemdmOqSIE

User avatar
erevos
Hosted Forum Moderator
Paladin
Posts: 137
Joined: Sat Mar 05, 2005 7:41 am
Location: Crete
Greece

Re: v6b5/v7 Overworked/Modworked 1.13c Txt Files: Bug Fixes, Descriptions and Modding Support

Post by erevos » Thu Sep 09, 2021 1:36 am

I really cannot explain it but i cannot make it work anymore. Only ofcourse if type1: belt type2: tbl. Is there a special reason you want belt on type2?

On a side note, adding shie to a weapon makes the Chance to Block 20% appear but it does not actually nlock as far as i can tell.

User avatar
Cypress
Junior Member
Champion of the Light
Posts: 263
Joined: Fri Dec 01, 2017 2:08 am

Re: v6b5/v7 Overworked/Modworked 1.13c Txt Files: Bug Fixes, Descriptions and Modding Support

Post by Cypress » Fri Sep 10, 2021 3:38 pm

Type determines the itemtypes.txt settings used. So for example, if type=belt, then only the itemtypes settings of belt can be used. If each item has its own itemtype, then they can each have their own custom itemtypes settings. This allows:

(1) Auto treasureclass control. You can individually control the drop rate of each item by modifying its type's rarity.
(2) Varying gfx. You can give up to 6 different graphics for a single item.
(3) Varying socket limits. Normally, all items of a type have the same socket limits based on ilvl, but with separate typings you can give a different limit to each item.
(4) Can change equipping for each individual item. Could make gloves that can be equipped as a weapon or as gloves for example.
(5) Can make an item always spawn as magic, or prevent it from being rare.
(6) Staffmods and class-only.

So for example, with this system in place I can easily make it so Crystal Swords are 1/3x as common, have sorceress staffmods, always spawn as at least magic and can have 6 sockets regardless of ilvl.

It's not a huge deal that belts have to have type=belt, it just means belts cannot be as controlled as other itemtypes.

Also, the "shie" type needs to be linked to type, it cannot be linked to type2. So for example, if you give the axe itemtype equiv1 or equiv2 = shie, then axes will be able to block. See: https://d2mods.info/forum/viewtopic.php?f=4&t=67252.

User avatar
MilesTeg
Posts: 35
Joined: Sun Jul 18, 2021 6:42 am
Germany

Re: v6b5/v7 Overworked/Modworked 1.13c Txt Files: Bug Fixes, Descriptions and Modding Support

Post by MilesTeg » Sat Sep 11, 2021 11:34 am

Cypress wrote:
Thu Aug 26, 2021 10:06 pm
For Overworked v8, I'm running into some rather serious issues. The idea of giving every weapon, boot and shield an ID is a huge mess.
(1) It has to be applied manually to automagic.txt, setitems.txt and uniqueitems.txt.
(2) Properties cannot help, since properties can only force param values, they cannot force min/max values. This is fine for pseudostats (i.e. skills), but it does not work at all for normal stats.
(3) Manually changing the values of ID stats every time weapons/boots/shields are changed would be a massive headache and error-prone.
(4) For boots/shields in particular, I'm relying on a tedious ID system that requires skills.txt spaghetti.

I don't think anyone would be willing to work with such a system. The solution I came up with is adding new txt files that are read by some program which then edits weapons/armor/misc.txt, uniqueitems.txt, setitems.txt and automagic.txt. This would make it very easy to modify and append IDs, but it will likely take me months to finish this program (I realize this is a laughably simple program to make, it just reads and modifies txt files, but I'm a very slow learner).

Also, if I am able to figure out how to make the above program, then I'll also be able to create a modding program, which I'm surprised hasn't been made yet, that would accept instructions to apply specific changes to txt files, which would make modding far less error-prone in general. It would allow Overworked to become modular, which means players/modders can install the parts of Overworked that they like and exclude everything else. With some effort, it would even allow for txt files from different mods to be compiled into a singular txt file, which will make it so mods do not have to be so mutually exclusive (i.e. modders can create simple plugins, like add two new uniques and three new skills, without having to messily copy+paste things over). And given that D2R txt files are at least slightly different from D2's, it will make conversion between D2 and D2R txt files easy.
Hi there. I'm just chiming in to give you a nod in the (probably?) right direction. Not sure I fully understand why you need IDs for weapon, boot and shield in the first place, but there's a programming library that makes working with csv (=txt files) a breeze:

The python library panda. Some example code:

Code: Select all

import pandas as pd  # imports the panda library into your python program

df = pd.read_csv('SetItems.txt',sep='\t', index_col = 0)   # loads SetItems.txt as a panda dataframe (=table) object

anotherdf = pd.read_csv('SetItemsIDs.txt',sep='\t', index_col = 0)   # loads another .txt file as a panda dataframe object

newcombineddf = pd.concat([df, anotherdf], axis=1)   # Concatenates/combines both tables (x-axis=ads new columns) into a new one
I haven't looked much further into it but panda should have all the tools you might want for this job.

You can try it out yourself online: https://www.learnpython.org/en/Pandas_Basics

User avatar
eleriaqueen
Posts: 49
Joined: Mon Dec 16, 2019 8:49 am
France

Re: v6b5/v7 Overworked/Modworked 1.13c Txt Files: Bug Fixes, Descriptions and Modding Support

Post by eleriaqueen » Thu Oct 21, 2021 11:05 am

Hi again Cypress, I just noticed that in Overworked a few skills like "Immolation Arrow" skilldesc contain

Code: Select all

*22
for one of its "descline" values, did you mean to delete this value but never got around to it ?

User avatar
Cypress
Junior Member
Champion of the Light
Posts: 263
Joined: Fri Dec 01, 2017 2:08 am

Re: v6b5/v7 Overworked/Modworked 1.13c Txt Files: Bug Fixes, Descriptions and Modding Support

Post by Cypress » Fri Oct 22, 2021 1:03 am

eleriaqueen wrote:
Thu Oct 21, 2021 11:05 am
Hi again Cypress, I just noticed that in Overworked a few skills like "Immolation Arrow" skilldesc contain

Code: Select all

*22
for one of its "descline" values, did you mean to delete this value but never got around to it ?
That was left in so I could compare the difference between the original formula and Amazon Basin's formula. It serves no purpose now. I'll go ahead and remove it, thanks!
MilesTeg wrote:
Sat Sep 11, 2021 11:34 am

Hi there. I'm just chiming in to give you a nod in the (probably?) right direction. Not sure I fully understand why you need IDs for weapon, boot and shield in the first place, but there's a programming library that makes working with csv (=txt files) a breeze:

The python library panda.
Thanks for the idea, but I've been very lazy (as you can probably tell by the very late response, sorry!) and given up on programming. I've started working on a new version again which will have the unwieldy systems in place, so your advice should be helpful for anyone that wants to automate the process for themselves. Also worth noting that this entire issue is non-existent for anyone running 1.13+, since there is a property function 36 which lets you imprint exact min/max/param values for a given property, which I really wish existed for 1.10f too.

ascar
Posts: 23
Joined: Mon Aug 02, 2021 6:40 pm
France

Re: v6b5/v7 Overworked/Modworked 1.13c Txt Files: Bug Fixes, Descriptions and Modding Support

Post by ascar » Fri Nov 12, 2021 4:33 am

hello, just checked everything, its perfect :cool:
I have some questions ! :

- for sandraider AI you just removed the "health% flee" AI ? It was not supposed to be here?
- for bat you added the numbers in "aidist" ?

- in missiles part, for nihilatak not sure about what did you modify
- for poison cloud same

- for uniqitems txt is it "allowed" to have "comment" lines? like expansion, "armor" , "belt" , "new uniqs" etc? I got sometimes a weird uniq shift of one line when i add or delete some new uniqs i created, not sure if its because of blank lines just used for txt structure to be more readable.

For all txt your added columns require code editing or is it only "forgotten" columns?


Thanks a lot :)

jerk-o
Posts: 49
Joined: Tue Mar 02, 2004 6:40 am
United States of America

Re: v6b5/v7 Overworked/Modworked 1.13c Txt Files: Bug Fixes, Descriptions and Modding Support

Post by jerk-o » Tue Nov 16, 2021 7:13 am

Have you given any thoughts on expanding or improving the automap?
(\ /) This is Bunny.
(o.o) Copy Bunny into your signature to help
(><) him on his way to world domination

User avatar
Cypress
Junior Member
Champion of the Light
Posts: 263
Joined: Fri Dec 01, 2017 2:08 am

Re: v6b5/v7 Overworked/Modworked 1.13c Txt Files: Bug Fixes, Descriptions and Modding Support

Post by Cypress » Sat Nov 20, 2021 1:17 am

Hi ascar. The Sand Raider/Bat changes were from the fixed 1.11/1.13c txt files (which Overworked is based on), so I'm not exactly sure what happened there, but I think the Sand Raider changes were to prevent them from wandering around pointlessly all the time, and the bat AIdist changes were to make sure their AI activates before you see them so that they can properly roost.

I'm not sure what you are referring to for Nihlathak and the poison clouds. Could you list the specific missiles? I believe the poison clouds you are talking about might be a fix to make it so the plague javelin clouds deal damage, which was another fix borrowed from the fixed 1.13c txt files.

For comment lines in uniqueitems.txt, I think the only way is to name the row Expansion.

As for the added columns, are you referring to weapons.txt/armor.txt/misc.txt? If so, then yes, you can use the new columns. A valid column in any of those three txt files is valid in the others. You could, for example, add the various damage and strbonus/dexbonus and speed columns to misc.txt so that weapons can be defined within misc.txt. And regardless of that, everything in Overworked/Modworked is softcoded and txt-based, so you should not need code editing to use any of the additions.

Hi jerk-o, I have not. I've never even modified automap.txt for any of my mods, I know nothing about it. Is there anything in specific that needs to be added/fixed for it?

jerk-o
Posts: 49
Joined: Tue Mar 02, 2004 6:40 am
United States of America

Re: v6b5/v7 Overworked/Modworked 1.13c Txt Files: Bug Fixes, Descriptions and Modding Support

Post by jerk-o » Mon Nov 22, 2021 6:19 am

I can't think of anything specific besides maybe a few small pools in act 1, but possibly doing a few play throughs and seeing what does/doesn't show up couldn't hurt.

Edit: After looking at the automap.txt fileguide, it doesn't seem too hard to change the automap, just a little bit time consuming. One thing to look into that I just thought of is the possibility of changing the colors of each tile on the automap. I think it'd be neat if the automap was drawn in blue, green, yellow, or whatever instead of always in red.
(\ /) This is Bunny.
(o.o) Copy Bunny into your signature to help
(><) him on his way to world domination

Post Reply

Return to “Member Аnnouncements”