Clipboard.

  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

ljfa

New Member
Jul 29, 2019
2,761
-46
0
--This program is free software: you can redistribute it and/or modify
--it under the terms of the GNU General Public License as published by
--the Free Software Foundation, either version 3 of the License, or
--(at your option) any later version.

--This program is distributed in the hope that it will be useful,
--but WITHOUT ANY WARRANTY; without even the implied warranty of
--MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
--GNU General Public License for more details.

--You should have received a copy of the GNU General Public License
--along with this program. If not, see <http://www.gnu.org/licenses/>.
 

Someone Else 37

Forum Addict
Feb 10, 2013
1,876
1,440
168
Bore Warp Composite Lens doesn't teleport drops when attached to a Mana Blaster

When I combine a Bore Lens with a Warp Lens in a crafting table (with a slimeball, in that order, so the Bore lens is visible), then attach the composite lens to a Mana Blaster, the mana bursts fired don't teleport the dropped items anywhere- they just drop where the blocks were broken. I had assumed that this combination would teleport the drops to the player, similar to how it works on a mana spreader.

I also tested the composite lens on a redstone spreader (works fine), as well as with a Force Relay block (also works fine, with both the spreader and the blaster). I tested a few other combinations of lenses as well, which all seemed to work fine.

I'm running the latest versions of Forge, Botania, and Baubles for 1.7.10 from Azanor's forum page (not tested with your fork), with no other mods installed. (Note that this bug also exists in my modified FTB Infinity instance, with the April Fool's update of Botania as well as the latest one.)

fml-client-1.log: https://gist.github.com/anonymous/441b4f892d4d9910df2f

--
That's an entire bug report that I was about to submit to Vazkii, before I searched her closed GitHub issues to find that it was actually the fix for another bug. Which made me sad.
 

Strikingwolf

New Member
Jul 29, 2019
3,709
-26
1
Code:
module Trees.BinaryTree where

-- Tree Imports
import Trees.Tree

data BinaryTree a = EmptyTree | Node a (BinaryTree a) (BinaryTree a) deriving (Show, Read, Eq)
type OrderedBiTree = (Ord a) => BinaryTree a

instance Functor BinaryTree where
  fmap f EmptyTree = EmptyTree
  fmap f (Node x leftsub rightsub) = Node (f x) (fmap f leftsub) (fmap f rightsub)

instance (Ord a) => Tree BinaryTree a where
  singleton x = Node x EmptyTree EmptyTree
  empty = EmptyTree
  treeInsert x EmptyTree = singleton x
  treeInsert x (Node a left right)
    | x == a = Node x left right
    | x < a = Node a (treeInsert x left) right
    | x > a = Node a left (treeInsert x right)
  treeFromList = fromListRooted EmptyTree
  -- Is not the inverse of treeFromList as the ordering in the List was lost
  treeToList EmptyTree = []
  treeToList (Node x left right) = (treeToList left) ++ (treeToList right) ++ [x]
  treeElem _ EmptyTree = False
  treeElem x (Node a left right)
    | x == a = True
    | x < a = treeElem x left
    | x > a = treeElem x right

Haskelling...what can I say