-
Notifications
You must be signed in to change notification settings - Fork 56
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Made Schematics load into RAM as byte arrays at the start of game instead of as NBT (saves +- 1GB of RAM) (SH) - Added checks for non-default schematics to make sure they contain valid NBT at game start (SH) - Made sure that invalid templates/schematics aren't even added to the array (SH) - Made sure that PocketTemplate loads Schematic from byte array before it tries to place it (PT) - Made sure that PocketTemplate unloads Schematic after placinf it (PT) - Made sure that TileEntityRift doesn't check its Location while PocketTemplate is replacing placeholders in Schematics (otherwise it will try to use null worlds and shizzle) (TER and PT) - Added functionality when saving a Schematic, this should put the Schematic in memory as a byte array (SH) - Fixed little bug, where Schematics that would be too big, would only be loaded when configured not to (SH) - Added functionality to keep the Schematics that are placed most loaded in RAM as NBT (combination of usageList and usageMap) (SH and PT) - Added config option to set the maximum number of Schematics that will be cached as NBT (MC and SH) - Made sure that Dimdoors.log is consistently used (SH) - Added check for .json file extension for files in the json config folder (SH) - Schematic files in the jar have had the .schem extension for a while now. Generalised a bit. (SH)
- Loading branch information
1 parent
d905340
commit 5b84baf
Showing
6 changed files
with
230 additions
and
34 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.