Skip to content
This repository has been archived by the owner on Aug 22, 2022. It is now read-only.

SlimeProperties behaving incorrectly #1

Closed
shivasuc opened this issue Jul 16, 2020 · 6 comments
Closed

SlimeProperties behaving incorrectly #1

shivasuc opened this issue Jul 16, 2020 · 6 comments

Comments

@shivasuc
Copy link

shivasuc commented Jul 16, 2020

Issue: When creating a new slime world, the console gets errors saying that a property was expeting a centain type, and then shows a value that isn't the type it expects, however in code, the types are the same.

image

Code used:

        set {_props} to new slime world property map
	set difficulty of {_props} to "normal"
	set spawn x of {_props} to 0.5
	set spawn y of {_props} to 63
	set spawn z of {_props} to 0.5
	set {_world} to slime world named "sb_%{_id}%" from file using properties {_props}
	load slime world {_world}```
@RealGatt
Copy link
Owner

Will look into it.

@RealGatt
Copy link
Owner

What version of SlimeWorldManager are you using?

@RealGatt
Copy link
Owner

Issue found and located. Somehow deleted some breaks in a switch case before shipping. Posting update soon

RealGatt added a commit that referenced this issue Jul 17, 2020
Add Cloned Slime World Property
@Padlick
Copy link

Padlick commented Jul 17, 2020

It still behaves incorrect.
When you do

set {_SWMsettings} to new slime world property map
set spawn x of {_SWMsettings} to 0
set spawn y of {_SWMsettings} to 64
set spawn z of {_SWMsettings} to 0

Your Addon returns
[Skript] spawnX expected a Integer, but got 0
[Skript] spawnY expected a Integer, but got 64
[Skript] spawnZ expected a Integer, but got 0

(0.0 and 64.0 also doesn't work)

@RealGatt RealGatt reopened this Jul 18, 2020
@RealGatt
Copy link
Owner

Seems like Skript gives Integers as Numbers regardless. Fixed in newest release

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants