I hate to sound ignorant on this one but what is an SoT?
public override List<StoreEntry> EntryStructure
{
get
{
List<StoreEntry> entry = base.EntryStructure;
string[] skillnames = Enum.GetNames(typeof(SkillName));
entry.Add(new ListEntry(typeof(PowerScroll),typeof(PowerScrollListEntry),"Power Scrolls"));
entry.Add(new ListEntry(typeof(StatCapScroll),typeof(StatCapScrollListEntry),"Stat Scrolls"));
return entry;
}
} public override List<StoreEntry> EntryStructure
{
get
{
List<StoreEntry> entry = base.EntryStructure;
entry.Add
(
new StashEntry
(
typeof(PowerScroll),"Power Scroll",500,new StashSortData
(
new StashSortEntry[]
{
new StashSortEntry( "Value", "Value" ),
new StashSortEntry( "Skill", "Skill" )
}
)
)
);
entry.Add
(
new StashEntry
(
typeof(StatCapScroll),"Stat Cap Scroll",500,new StashSortData
(
new StashSortEntry[]
{
new StashSortEntry( "Value", "Value" )
}
)
)
);
return entry;
}
}
//master constructor
public TreasureMapListEntry(Item item) : base(item)
{
TreasureMap map = (TreasureMap)item;
//fill in the name based on the level
//TODO: find a better way to do this
switch (map.Level)
{
case 0:
{
_Name = "Youthful";
break;
}
case 1:
{
_Name = "Plainly";
break;
}
case 2:
{
_Name = "Expertly";
break;
}
case 3:
{
_Name = "Adeptly";
break;
}
case 4:
{
_Name = "Cleverly";
break;
}
case 5:
{
_Name = "Deviously";
break;
}
case 6:
{
_Name = "Ingeniously";
break;
}
}
_ChestLocation = map.ChestLocation;
_ChestMap = map.ChestMap;
_Decoder = map.Decoder;
_Level = map.Level;
_Bounds = map.Bounds;
}
Yeah, they changed the T-Maps to the random spawn locations (like the official servers) and it messed with the storage keys. My fix went a different route.... I don't like the random locations so I just switched back to the old treasuremap.cs. Have not seen any problems yet - but not sure what the long term effects will be
So by a previous version do you mean an older verison of treasuremap.cs from...? pub 54 or? Any chance Tukram you could post that treasuremap.cs? I tried these workarounds without being able to eliminate the chestmap problem.Yeah, they changed the T-Maps to the random spawn locations (like the official servers) and it messed with the storage keys. My fix went a different route.... I don't like the random locations so I just switched back to the old treasuremap.cs. Have not seen any problems yet - but not sure what the long term effects will be
As a "programming" fix... I don't know if this is recommended, probably not. Not sure what it might interfere with later - but I will deal with that later. I can't stand the random spawning chests anyway, so I was glad to get the storage keys working, Davies Locker working, and go back to the regular spawning chests so the rune libraries work. For me it was a win/win/win. We shall see if it backfires later.
Universal Storage Keys/Main Data Management/BODListEntries.cs:
CS0234: Line 8: The type or namespace name 'CliLocHandler' does not exist in
the namespace 'Solaris' (are you missing an assembly reference?)
+ Universal Storage Keys/Main Data Management/ItemListEntries.cs:
CS0234: Line 7: The type or namespace name 'CliLocHandler' does not exist in
the namespace 'Solaris' (are you missing an assembly reference?)
+ Universal Storage Keys/Main Data Management/StashListEntry.cs:
CS0234: Line 5: The type or namespace name 'CliLocHandler' does not exist in
the namespace 'Solaris' (are you missing an assembly reference?)
+ Universal Storage Keys/Main Data Management/StoreEntries.cs:
CS0234: Line 13: The type or namespace name 'CliLocHandler' does not exist i
n the namespace 'Solaris' (are you missing an assembly reference?)lol, sorry, was looking at an older version of the keys that didn't include it.
I ended up removing Bod keys and the list entry because a Bod book that's part of the repo is way better IMO
I have something I modified. The pet key when you put in the master key and used it would sometimes crash a shard. This one you have to lock down in your house. I'll send the script
