Steam'i Yükleyin
giriş
|
dil
简体中文 (Basitleştirilmiş Çince)
繁體中文 (Geleneksel Çince)
日本語 (Japonca)
한국어 (Korece)
ไทย (Tayca)
Български (Bulgarca)
Čeština (Çekçe)
Dansk (Danca)
Deutsch (Almanca)
English (İngilizce)
Español - España (İspanyolca - İspanya)
Español - Latinoamérica (İspanyolca - Latin Amerika)
Ελληνικά (Yunanca)
Français (Fransızca)
Italiano (İtalyanca)
Bahasa Indonesia (Endonezce)
Magyar (Macarca)
Nederlands (Hollandaca)
Norsk (Norveççe)
Polski (Lehçe)
Português (Portekizce - Portekiz)
Português - Brasil (Portekizce - Brezilya)
Română (Rumence)
Русский (Rusça)
Suomi (Fince)
Svenska (İsveççe)
Tiếng Việt (Vietnamca)
Українська (Ukraynaca)
Bir çeviri sorunu bildirin
EDIT: I know how to store an actor's name in a variable, butu I know not of a way to change an actor's name to the value stored in said variable.
With that knowledge we can go into the script editor and search for the name of the command. In this case it is "Change Name"
I have the code below for you, but it's all in the Game_Interpreter script.
What we have here is the script is setting the variable "actor" to $game_actors[Parameter] and setting that variable's name function to Parameter 2 if they are an actor. Basically $game_actors is a variable list called an array that contains all of the data for every actor in the game. $game_actors[1] will access the first actor's information for example. This means that $game_actors[1].name would in a default project return "Eric" (or whatever it is in each language). So if want to simplifiy this we can just merge the two lines together.
Lets say we want to change Eric's name to Dan. It would look like this
Now since you said you can put the name in a variable so that the palyer can name the character whatever they choose you'd want to use something like:
As to where to put this you can place it within a script call command on Page 3 of the events.
1. Open Database -- Choose Tab "Actors" --- Choose a Actor
2 Insert the following as Char discription: \V[1]
3. We are finished.
Whatever text you safe in Game Variable 1 will be shown as Actor discription for that Actor.
This trick doesnt work with all Database states, but with some off them.
Edit: Pseudocode: Control Variables -- Variable 1 = "Your Text with "" around it" if i remember correct.
Honestly though I'm shook right now. In all the time that I have been using this software I never knew that the text codes ("\V[#]" for example) actually worked in the description boxes.
They Work for Item Descritpion and Actor Description. If i recall right also for some others, but some interesting ones dont work sadly.
Sadly it doesnt work in the Name Box. But working in the description is allready very usefull.
#--------------------------------------------------------------------------
# Actor Description Change Script
# Original Script by Ineffabelle
# Converted to Plug-and-Play Script by Cougarmint
# Original Topic:
# https://forums.rpgmakerweb.com/index.php?threads/change-player-description.28444/
#--------------------------------------------------------------------------
class Game_Actor
def set_description(text)
actor.description = text
end
end
The original script contained all the instructions in the header, but I pulled them out and posted them here to make them easier for you:
Installation: To install this script, insert it below materials, above main.
There is no need to modify the "Game_Actor" class like in the original version.
~~~Usage~~~
1. Create a Common Event for your actor, called "X's Description Change" or whatever makes it easier for you to remember. Set it as a "Parallel Process" event and tie it to a switch of your choosing, preferably one that will only be actor or post-event specific.
2. Use the "Script" command in the Event Editor and set the following command: $game_actors[X].set_description("Insert new description here.")
3. Click "Apply" or "OK" to save your Common Event.
4. In the map event that results in your character's description being changed, turn the corresponding switch on to activate the Common Event.
5. To revert the description, turn the switch off and repeat step 2 in your map event. Copy and paste the original description from the database into the script command. This will eliminate the need to exit and reload the game, and there is no need to make another common event.
~~~Notes~~~
X is the actor's id number. In example, if you want to change the description of Actor 2, you would replace X with 2.
When using this script, the Carriage Return (pressing enter) will set a new line due to the nature of the call function. \n (line break) is not needed.
The character limit for the description is the same. Keep that in mind when choosing a new description for your actor.
You can reuse the Common Event as needed, and change the description usingthe "Conditional Branch" function in the event (such as if there is another actor in the party, or if there is a certain weapon equipped.) You can even forgo the Common Event and change the description based on Map Events; just be sure to set the event to be triggered via "Paralell Process." Don't be afraid to use your imagination to create dynamic descriptions for different situations!
~~~TO DO~~~
Figure out a way to make this permanent without having to use a common event or switch.
Hope this helps!
If he keeps his paralell common event activated, the descritpion will be changed up to 30 to 60 times per seccond. that can suck down some of his game performance, depending on how demanding that scriptcommand is.
In my opinion it would be best to deactivate that event after it changed the descritption.
Or give it no trigger at all, and use the call common event eventcommand to call it only when needed.
Edit: Why not delete the whole common event and only use the scriptline in the event that changes this description? ,
I mean this line alone: $game_actors[X].set_description("Insert new description here.") used as eventcommand + insert the above linked big scritp for this in script Database like explained.
Edit2: OP now get 2 Solutions, 2 are always better than one, sometimes it allows to create a 3rd Solution. I would use the first one because its allready in the rpgmaker Editor.