Mythruna
April 17, 2024, 09:54:29 PM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Welcome to the new forums. See "Announcements" for a note for new users.
 
   Home   Help Search Login Register  
Pages: 1 ... 3 4 [5]
  Print  
Author Topic: Paul, API: Info/Allow Suggestions?  (Read 49582 times)
Michael
Donators
Hero Member
***
Posts: 2166



View Profile
« Reply #60 on: September 18, 2013, 06:24:07 PM »

Scripted actions are for scripts.  If you are not using scripting then you would not use a scripted action.

Fail Tongue
Logged
Michael
Donators
Hero Member
***
Posts: 2166



View Profile
« Reply #61 on: September 18, 2013, 06:31:54 PM »

Okay so anything within the "scripts" package will deal with external scripts, correct? (I just have to make sure)
Logged
pspeed
Administrator
Hero Member
*****
Posts: 5612



View Profile
« Reply #62 on: September 18, 2013, 09:00:02 PM »

Okay so anything within the "scripts" package will deal with external scripts, correct? (I just have to make sure)

Yes.  I tried to pick a name that made sense.
Logged
Michael
Donators
Hero Member
***
Posts: 2166



View Profile
« Reply #63 on: September 29, 2013, 08:29:41 AM »

This has been bothering me for quite some time with getting the location; how is it that with the groovy scripts you can grab the location without the position being null, but yet in java it is null?

Is it just how you set it up within the script package?
Logged
pspeed
Administrator
Hero Member
*****
Posts: 5612



View Profile
« Reply #64 on: September 29, 2013, 12:02:22 PM »

This has been bothering me for quite some time with getting the location; how is it that with the groovy scripts you can grab the location without the position being null, but yet in java it is null?

Is it just how you set it up within the script package?

Since I feel like I kind of said this once already...

The player does not have a Position component.  There is no Position component on the player.  Other entities have Position components but not the player.

That's why the player doesn't have any position.  Players are dealt with differently than other objects in the version you use.

The more complicated solution that breaks for sure with the next version is already embedded in the groovy scripts included with the game... and it is different on single player and multiplayer.  But if you hunt down the getLocation() definitions you can find it.

I have a little trouble dumping support into the Java API because it's not a defined API, will break for certain with the next version, and I spent a lot of time making an easier API already that is less likely to break.
Logged
Pages: 1 ... 3 4 [5]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.20 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!